On Dec 10, 2013, at 11:48 PM, wei wang wrote:

I have viewed  config.log.   In
./mips64el-unknown-linux-gnu/libgcc/config.log

says:
configure:3795: /mnt/clfs/sources/gcc-build/./gcc/xgcc
-B/mnt/clfs/sources/gcc-build/./gcc/
-B/cross-tools/mips64el-unknown-linux-gnu/bin/
-B/cross-tools/mips64el-unknown-linux-gnu/lib/ -isystem
/cross-tools/mips64el-unknown-linux-gnu/include -isystem
/cross-tools/mips64el-unknown-linux-gnu/sys-include -c -g -O2
-minterlink-mips16 conftest.c >&5
conftest.c:10:19: fatal error: stdio.h: No such file or directory
#include ^ compilation terminated. c

/mnt/clfs/sources/gcc-build/./gcc/xgcc -B/mnt/clfs/sources/gcc-build/./ gcc/ -B/cross-tools/mips64el-unknown-linux-gnu/bin/ -B/cross-tools/ mips64el-unknown-linux-gnu/lib/ -isystem /cross-tools/mips64el-unknown- linux-gnu/include -isystem /cross-tools/mips64el-unknown-linux-gnu/sys- include -g -O2 -minterlink-mips16 -O2 -g -O2 -minterlink-mips16 - DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wno-narrowing -Wwrite- strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wold- style-definition -isystem ./include -fPIC -g -DIN_LIBGCC2 - fbuilding-libgcc -fno-stack-protector -fPIC -I. -I. -I../.././gcc - I../../../gcc-4.8.1/libgcc -I../../../gcc-4.8.1/libgcc/. -I../../../ gcc-4.8.1/libgcc/../gcc -I../../../gcc-4.8.1/libgcc/../include - DHAVE_CC_TLS -o _muldi3.o -MT _muldi3.o -MD -MP -MF _muldi3.dep - DL_muldi3 -c ../../../gcc-4.8.1/libgcc/libgcc2.c -fvisibility=hidden - DHIDE_EXPORTS
In file included from ../../../gcc-4.8.1/libgcc/libgcc2.c:27:0:
../../../gcc-4.8.1/libgcc/../gcc/tsystem.h:87:19: fatal error: stdio.h: No such file or directory
#include <stdio.h>
                  ^
compilation terminated.

I wonder if mips has a step that we are missing for headers. I am not sure if they should be in /cross-tools/mips64el-unknown-linux-gnu/sys- include or not.

I read other people having issues with powerpc, but I've never encountered this with powerpc.

SIncerely,

WIlliam Harrington
_______________________________________________
Clfs-support mailing list
[email protected]
http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org

Reply via email to