I've done a search for those four headers on my LFS-6.6/BLFS-6.3 system, and gone back and checked that my build script follows the GCC-4.4.3 install. It does, and all the tests are checked for, including the one about search paths, but there is that comment about limits.h being unconditionally placed in /usr/lib/gcc/i686-pc-linux-gnu/4.4.3/include- fixed/, but there's no explicit instruction to do, and it seems to have ended up there. It's not clear to me why Mesa can't find those headers, as they seem to be in the compiler's built-in search path. I hope this helps the diagnosis. Thanks.
/usr/include/c++/4.4.3/tr1/float.h /usr/include/c++/4.4.3/tr1/limits.h /usr/include/c++/4.4.3/tr1/stdarg.h /usr/include/limits.h /usr/include/linux/limits.h /usr/include/linux/stddef.h /usr/lib/gcc/i686-pc-linux-gnu/4.4.3/include-fixed/limits.h /usr/lib/gcc/i686-pc-linux-gnu/4.4.3/include/float.h /usr/lib/gcc/i686-pc-linux-gnu/4.4.3/include/stdarg.h /usr/lib/gcc/i686-pc-linux-gnu/4.4.3/include/stddef.h /usr/lib/gcc/i686-pc-linux-gnu/4.4.3/install-tools/include/limits.h /usr/src/linux-2.6.34.13/arch/arm/include/asm/limits.h /usr/src/linux-2.6.34.13/arch/parisc/math-emu/float.h /usr/src/linux-2.6.34.13/include/linux/limits.h /usr/src/linux-2.6.34.13/include/linux/stddef.h -- Paul Rogers [email protected] http://www.xprt.net/~pgrogers/ Rogers' Second Law: "Everything you do communicates." (I do not personally endorse any additions after this line. TANSTAAFL :-) -- http://www.fastmail.fm - mmm... Fastmail... -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
