Crosstool-NG build produces all the tools except the compiler

Mitch Frazier mitch@comwestcr.com
Mon Apr 19 20:13:00 GMT 2010


p.s. I did successfully build the m68k-unknown-elf toolchain which runs
on Linux and include it in the PATH when I try to build the Windows
toolchain.

On 04/19/2010 12:46 PM, Mitch Frazier wrote:
> Yann
> 
> I'm trying to build an m68k-unknown-elf toolchain that will run on a
> Windows system.  I'm building it on openSUSE 11.2.
> 
> I've installed the mingw cross compiler on my openSUSE system and
> created a crosstool-NG configuration for a Canadian cross:
> 
>   Build on openSUSE
>   Host on  Windows
>   Target   m68k
> 
> When I run crosstool-NG it shows the following systems:
> 
>> [EXTRA]  Dumping internal crosstool-NG configuration                            
>> [EXTRA]    Building a toolchain for:                                            
>> [EXTRA]      build  = x86_64-suse-linux                                         
>> [EXTRA]      host   = i386-mingw32msvc                                          
>> [EXTRA]      target = m68k-unknown-elf                                          
> 
> The host value (i386-mingw32msvc) is openSUSE's name for the mingw
> compiler running on openSUSE.
> 
> The build "succeeds", but it doesn't build a C compiler.  Specifically
> it builds the following executable files:
> 
> .../m68k-unknown-elf/m68k-unknown-elf/bin/ld.exe
> .../m68k-unknown-elf/m68k-unknown-elf/bin/nm.exe
> .../m68k-unknown-elf/m68k-unknown-elf/bin/objcopy.exe
> .../m68k-unknown-elf/m68k-unknown-elf/bin/strip.exe
> .../m68k-unknown-elf/m68k-unknown-elf/bin/ranlib.exe
> .../m68k-unknown-elf/m68k-unknown-elf/bin/objdump.exe
> .../m68k-unknown-elf/m68k-unknown-elf/bin/as.exe
> .../m68k-unknown-elf/m68k-unknown-elf/bin/ar.exe
> .../m68k-unknown-elf/bin/m68k-unknown-elf-ar.exe
> .../m68k-unknown-elf/bin/m68k-unknown-elf-ranlib.exe
> .../m68k-unknown-elf/bin/m68k-unknown-elf-strip.exe
> .../m68k-unknown-elf/bin/m68k-unknown-elf-readelf.exe
> .../m68k-unknown-elf/bin/m68k-unknown-elf-as.exe
> .../m68k-unknown-elf/bin/m68k-unknown-elf-ld.exe
> .../m68k-unknown-elf/bin/m68k-unknown-elf-c++filt.exe
> .../m68k-unknown-elf/bin/m68k-unknown-elf-addr2line.exe
> .../m68k-unknown-elf/bin/m68k-unknown-elf-gprof.exe
> .../m68k-unknown-elf/bin/m68k-unknown-elf-strings.exe
> .../m68k-unknown-elf/bin/m68k-unknown-elf-nm.exe
> .../m68k-unknown-elf/bin/m68k-unknown-elf-size.exe
> .../m68k-unknown-elf/bin/m68k-unknown-elf-objdump.exe
> .../m68k-unknown-elf/bin/m68k-unknown-elf-objcopy.exe
> 
> 
> Note that it doesn't "fail" building the compiler: it never even tries.
>  I've tried changing the build scripts a bit to get them to try to build
> the compiler but so far that just causes the build to fail for other
> reasons.  I haven't actually tested the created .exe's yet.
> 
> Does this make sense that it doesn't try to build the compiler?
> 
> Also note that this happens with the current release of crosstool-NG as
> well as the code from the repository.
> 
> Mitch
> 
> 
> 
> --
> For unsubscribe information see http://sourceware.org/lists.html#faq
> 


--
For unsubscribe information see http://sourceware.org/lists.html#faq



More information about the crossgcc mailing list