He Yunlong-B20256 wrote: > > Glad to hear that, however, in my environment, the header files > do exist, for example: > > > /opt/freescale/usr/local/gcc-4.3.74-eglibc-2.8.74-dp-3/powerpc-none-linu > x-gnuspe/powerpc-none-linux-gnuspe/libc/usr/include/features.h > it contains: > 40 _SVID_SOURCE ISO C, POSIX, and SVID things. > 41 _ATFILE_SOURCE Additional *at interfaces. > 42 _GNU_SOURCE All of the above, plus GNU > extensions. > > However, in /usr/include/features.h, it contains following > lines: > > 40 _SVID_SOURCE ISO C, POSIX, and SVID things. > 41 _GNU_SOURCE All of the above, plus GNU > extensions. > > In generated gcc-4.3.2/build-gcc/gcc/include-fixed/features.h, > following lines found: > 1 /* DO NOT EDIT THIS FILE. > 2 > 3 It has been auto-edited by fixincludes from: > 4 > 5 "/usr/include/features.h" > 6 > 7 This had to be done to correct non-standard usages > in the > 8 original, manufacturer supplied header file. */ > > 49 _SVID_SOURCE ISO C, POSIX, and SVID things. > 50 _GNU_SOURCE All of the above, plus GNU > extensions. > > I didn't change any fix-includes related files, so that's what > gcc compiling process does, is there anything wrong in my build process? You didn't tell me how you built gcc, so I cannot know. However, I suspect that gcc did not see find headers in your sysroot. What does the features.h in your target's C library look like? Andrew.
