Hi, Andrew, 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? B.R. Harry -----Original Message----- From: Andrew Haley [mailto:aph@xxxxxxxxxx] Sent: Tuesday, December 01, 2009 5:34 PM To: He Yunlong-B20256 Cc: gcc-help@xxxxxxxxxxx Subject: Re: One question about gcc fix_includes He Yunlong-B20256 wrote: > We are using one cross-compiler to compile native gcc, in out test, > we found that gcc will created "fixed includes" from host glibc header > files, I think they should come from the header files inside of the > cross-compiler, can anyone confirm that? That doesn't sound right. gcc is supposed to fixinclude the headers from the C library for the target. It's possible you failed to provide them. Andrew.
