Building a cross-gcc from Debian SID
Thu Jan 15 16:06:00 GMT 2004

> hi all,
> I would like to build cross-compiler from my debian sid, for
> rs6000-ibm-aix4.3 target architecture.
> I built binutils (2.14) with these options:
> ./configure --prefix=/usr/local --target=rs6000-ibm-aix4.3
> --with-headers=/usr/include.aix --with-libc=/usr/lib.aix

I think it should be --with-libs, not --with-libc, right?

> ../gcc-3.3.2/configure --host=i686-pc-linux-gnu
> --target=rs6000-ibm-aix4.3 --with-headers=/usr/include.aix
> --enable-language=c  --with-gnu-as
> --with-as=/usr/local/rs6000-ibm-aix4.3/bin/as --with-gnu-ld
> --with-ld=/usr/local --without-threads --with-libc=/usr/lib.aix

Again, --with-libs rather than --with-libc, probably.
(And does the --with-ld option really take a directory?)

> In file included from /root/gcc-build/gcc/include/errno.h:1,
> /root/gcc-build/gcc/include/errno.h:1:10: #include nested too deeply
> make[2]: *** [libgcc/./_muldi3.o] Erreur 1

First off: please don't build gcc as root :-)  It's much better
practice to use e.g. /opt/foobar as your --prefix, and chown
/opt/foobar to a regular user!   OK, safety tips aside:

I don't know what's causing your problem, but you might consider
trying the latest gcc-3.3.3 snapshot and using --with-sysroot
instead of --with-libs and --with-headers when compiling gcc.
sysroot is a much nicer way of telling gcc about the target
system's headers and libraries.  binutils doesn't take --with-sysroot,
I think, but it does take --with-lib-path, which might be handy
if you need it to search both /lib and /usr/lib.  I'm still muddy
on this myself (even though I submitted the patch that added
- Dan

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

More information about the crossgcc mailing list