cross compile gcc

Rudolf Floers r.floers at
Mon Jan 8 02:35:23 PST 2001

On Sun, Jan 07, 2001 at 04:56:32PM -0700, ken_i_m wrote:

> --target=i486-pc-linux-gnu --prefix=/usr 
> --with-gxx-include-dir=/usr/include/g++ \
> --enable-languages=c,c++ --disable-nls

i prefer --host=i486-blaa..  but i it's probably just the same, isn't 
it? also make sure there is no CFLAGS=-march=i686, but -march=i486, env

>make -e LDFLAGS=-static cross

what's that cross target? i don't think it's needed when compiling
for a 486 on a 686.

> ../../gcc-2.95.2/gcc/libgcc2.c:41: stdlib.h: No such file or directory
> ../../gcc-2.95.2/gcc/libgcc2.c:42: unistd.h: No such file or directory
> make[1]: *** {libgcc2.a] Error 1
> make[1]: Leaving directory `/lfs/usr/src/gcc-build/gcc'
> make: *** [cross] Error 2

why do you actually compile a statically linked gcc? i think you don't 
need gcc on your 486 router at all. the only thing of the gcc package
you may/might need is 
you should be able to compile everything you need on your 686, why a 
compiler for the 486?


Unsubscribe: send email to lfs-discuss-request at
and put unsubscribe in the subject header of the message

More information about the lfs-dev mailing list