newlib for i386-linux-newlib

[Jeff Johnston]

Shaun Jackman wrote:
> I'm attempting to configure newlib for --target=i386-linux-newlib.
> configure is failing here:
> 
> checking for gcc... (cached) i386-linux-newlib-gcc
> -B/home/sjackman/src/toolchain/i386-linux-newlib/newlib-cvs/_build/i386-linux-newlib/newlib/
> -isystem /home/sjackman/src/toolchain/i386-linux-newlib/newlib-cvs/_build/i386-linux-newlib/newlib/targ-include
> -isystem /home/sjackman/src/toolchain/i386-linux-newlib/newlib-cvs/newlib/libc/include
> checking whether the C compiler (i386-linux-newlib-gcc
> -B/home/sjackman/src/toolchain/i386-linux-newlib/newlib-cvs/_build/i386-linux-newlib/newlib/
> -isystem /home/sjackman/src/toolchain/i386-linux-newlib/newlib-cvs/_build/i386-linux-newlib/newlib/targ-include
> -isystem /home/sjackman/src/toolchain/i386-linux-newlib/newlib-cvs/newlib/libc/include
> -O2 -g -O2   ) works... no
> configure: error: installation or configuration problem: C compiler
> cannot create executables.
> make[1]: *** [configure-target-newlib] Error 1
> make[1]: Leaving directory
> `/home/sjackman/src/toolchain/i386-linux-newlib/newlib-cvs/_build'
> 
> I know I got farther than this before. The C compiler cannot create
> executables because crt0.o is missing, but I haven't built newlib yet,
> so this isn't surprising. Any suggestion what's gone wrong here?
> 

Any chance you switched over to using libtool?  Newlib overrides the 
regular gcc execution test with its own macro (see LIB_AC_PROG_CC in 
newlib/acinclude.m4).  If you opt to use libtool, it will end up doing 
the normal execution test in its configuration.  That is why we 
currently only support libtool natively.  Perhaps you could modify the 
libtool.m4 file to handle your particular situation.

> i386-linux-newlib isn't a supported target, yet, but I'm hoping to get it there!
> 
> Thanks!
> Shaun