cygwin arm-elf-linux gcc build failure

John Andrews
Fri Mar 23 00:49:00 GMT 2001

Thanks Richard!

That was the problem.

I got rid of the -linux in the arm-elf-linux configuration and I was able to
complete building arm-elf-gcc --with-newlib.

It feels really good to actually complete something!

Well at least for a couple of minutes 8-) 

Then reality starts settling in again (I hate that 8-) 

I still can't build a kernel, or newlib for that matter.

I do appreciate everyone's help. 

Can someone please tell me what libs I need in place to build
arm-elf-linux-gcc? What I'm really shooting for is building uClinux-2.4,
I've spent hours scouring archives, and the web sites of half the people on
this list, I just can't find anywhere that tells me what headers and libs
need to be in place to get the compiler compiled BEFORE having the kernel

When I try to build newlib with the arm-elf-gcc I get:

arm-elf-gcc -B/usr/src/build-2.4.x/newlib/arm-elf/newlib/ -isystem
d-2.4.x/newlib/arm-elf/newlib/targ-include -isystem
/libc/include -DPACKAGE=\"newlib\" -DVERSION=\"1.9.0\"  -I.
newlib-1.9.0/newlib/libc/stdlib  -O2 -DABORT_PROVIDED -DHAVE_GETTIMEOFDAY
RDI_MONITOR -I../../targ-include
/libc/include -fno-builtin      -g -O2 -c
Assembler messages:
: No such file or directory
arm-elf-gcc: file path prefix `/usr/src/build-2.4.x/newlib/arm-elf/newlib/'
r used
make[3]: *** [__adjust.o] Error 1
make[3]: Leaving directory
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/usr/src/build-2.4.x/newlib/arm-elf/newlib/libc'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/build-2.4.x/newlib/arm-elf/newlib'
make: *** [all-target-newlib] Error 2

I know this one is something dumb...


John E. A.

-----Original Message-----
From: Richard Earnshaw [ ]
Sent: Wednesday, March 21, 2001 5:52 AM
To: John Andrews
Cc: Crossgcc;
Subject: Re: cygwin arm-elf-linux gcc build failure 

> Hi All,
> I've made it past a number of cross gcc build errors based on the sage
> advice (both to myself and others) from the ubergeeks of this list. Many
> Thanks!
> But now I'm stumped again. After rereading all of the archives, FAQs and
> assorted web pages I can't get a clue regarding this one.
> Binutils built and installed without incident using the default
> The gcc build is now making it to libgcc2 and barfs on something in
> gthr-posix.h. I've tried running dos2unix CRLF -> CR converter on just
> file, and also on all of the headers. The converted file sizes are the
> as the preconverted and it doesn't change the error.

I suspect the problem is that you are trying to use newlib with a Linux 
target.  Linux builds demand more than the newlib headers provide and so 
you are running into problems.  If you want a linux target, then you will 
need to obtain glibc and build with that.  If you want newlib, then I 
suggest you use a more appropriate cross configuration, such as plain 


Want more information?  See the CrossGCC FAQ,
Want to unsubscribe? Send a note to

More information about the crossgcc mailing list