Le 04/02/2012 22:33, Bryan Kadzban a écrit : > > Bah, right. Well, there's a C++ compiler *somewhere*, that the pass2 > gcc is using to compile libstdc++ when it runs into this error. :-) > > Maybe it'd be a better idea to do it that way: Run a build until it > breaks, then repeat the command that fails (with all flags intact), > adding -E and -Wp,-dU, removing -o<file>, and replacing any C or C++ > source file with whatever stdio.h is being used. (Probably the one in > /tools/include, but it might be worth double-checking. You can do that > with another compiler run just adding the -E flag, and grepping through > the output file for stdio. It'll be on a #file line somewhere.) > > The full output of that -E -Wp,-dU run is one of the few things that'll > be useful for debugging this I think. (Along with whatever the command > was, I think.) Maybe try (supposing the build tree has not been removed):
echo '#include<cstdio>' |/mnt/lfs/sources/gcc-build/gcc/xgcc -shared-libgcc \ -B/mnt/lfs/sources/gcc-build/gcc -nostdinc++ \ -B/tools/x86_64-unknown-linux-gnu/bin/ \ -B/tools/x86_64-unknown-linux-gnu/lib/ \ -isystem /tools/x86_64-unknown-linux-gnu/include \ -isystem /tools/x86_64-unknown-linux-gnu/sys-include \ -I/mnt/lfs/sources/gcc-4.6.2/gcc \ -I/mnt/lfs/sources/gcc-build/x86_64-unknown-linux-gnu/libstdc++-v3/include/x86_64-unknown-linux-gnu \ -I/mnt/lfs/sources/gcc-build/x86_64-unknown-linux-gnu/libstdc++-v3/include \ -I/mnt/lfs/sources/gcc-4.6.2/libstdc++-v3/libsupc++ \ -D_GNU_SOURCE \ -E -Wp,-dU - Regards pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
