Greg Schafer wrote: > Further investigation reveals Debian Lenny does some (possibly weird) > stuff with the multilib Glibc include dirs. Essentially, it's a 32-bit > host so the Glibc 32-bit headers are naturally in /usr/include. But then > they've gone and stuck the 64-bit Glibc headers into > /usr/include/x86_64-linux-gnu. > > With that information in hand, it now becomes clear why the build is so > deeply screwed. Basically, the stage2 gcc was linked against a 64-bit libc > but compiled against 32-bit libc headers. Arghhh! ie: the stage1 gcc (used > to compile stage2 gcc) doesn't know to look in > /usr/include/x86_64-linux-gnu for it's headers. I made the the build > succeed by adding `-isystem /usr/include/x86_64-linux-gnu' to BOOT_CFLAGS. >
Thanks for solving this! -- Alexander E. Patrakov -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
