RE: SH-ELF / MINGW32 cross problem

["Anita Kulkarni" <AnitaK at kpit dot com>]

Hi,
I have built SH toolchains for mingw host on linux. I am using gcc-3.0.3, binutils-2.11.2, newlib-1.9.0, mingw runtime-20000203 (as could not be built with latest runtime). But it is working fine on Windows-XP too.
Regards,
Anita Kulkarni
KPIT InfoSystems Ltd.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Free download of GNUSH tool chain for Hitachi's SH Series.
The following site also offers free support to European customers.
Read more at http://www.kpit.com/products/support.htm.
Latest version of GNUSH is released on Jan 1, 2002.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 

-----Original Message-----
From: Kai Ruottu [mailto:kai.ruottu@luukku.com]
Sent: Tuesday, April 02, 2002 4:46 PM
To: Matt Williams
Cc: crossgcc@sources.redhat.com
Subject: Re: SH-ELF / MINGW32 cross problem


Matt Williams wrote:
> 
> Hello all.
> 
> I'm having a problem with GCC with an SH-ELF target and a Mingw32 host
> (though the target doesn't seem to matter in this case), it compiles
> fine (under Linux), but when I try to compile something (or do 'gcc -v'),
> I get this:
> 
> sh-elf-gcc: Cannot allocate 1017617375 bytes

 One Gbyte is quite a lot memory...

> Anyone have any ideas as to why?

 Not seen here at least with gcc-3.0.3/3.0.4 and 'sh-elf' or any other target.
And with Win2k...
 
> If it makes any difference, I'm running Windows XP Pro.  And GCC's version
> is 3.0.4, but this also happens to 2.95.2 and 2.95.3.

 Does the same happen on any other Windoze ?  9x/NT4/2k ?  If it works OK
elsewhere, the problem lies in Mingw with XP...

 What are the Mingw-runtime and the GCC used in the host-compiler ?  Not that
I had ever seen or heard about your problem, but if it proves that the standard
Mingw-distribution packages will cause this...

 Where you did build the 'sh-elf' targeted cross-GCC?  What were the binutils
(for Win32-target) used to link the resulted 'sh-elf-gcc' ?  It is well known
that Windoze isn't the best place to build (the tools there could handle the
sources somehow wrong) and all GNU-binutils versions don't work for the Win32-
target. Under Linux you may have used some 'only for Linux'-binutils sources
for the Win32-target too...
 
Cheers, Kai



------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com