rbmj <rbmj@xxxxxxxxxxx> writes: > On 05/25/2012 09:59 AM, Ian Lance Taylor wrote: >> rbmj<rbmj@xxxxxxxxxxx> writes: >> >>> Refine my question: anyone know why fixincludes does not appear to be >>> doing *anything*? I can't seem to find any fixed headers anywhere in >>> GCC's build tree. And the compile keeps failing... >> In your specific case, I don't know. But it is possible for a target to >> disable fixincludes by setting STMP_FIXINC in a config/CPU/t-XXX file. >> Or, since this is a cross-compiler, GCC may simply be confused about >> where to find the header files that it is supposed to fix. Normally >> those header files will be found in the directory printed by gcc >> -print-sysroot-headers-suffix. What does that print for you? Did you >> configure GCC with the right --with-sysroot option? > > Maybe that's the error: > > ./gcc/xgcc -print-sysroot-headers-suffix > xgcc: fatal error: not configured with sysroot headers suffix > > xgcc is the compiler in question right? . is the build directory. I > believe xgcc is the compiler that compiles all of the cross targets > (lib*). Yes. > My configure call was: > > ../gcc-4.7.0/configure --prefix=/usr --target=powerpc-wrs-vxworks > --with-gnu-as --with-gnu-ld > --with-headers=../gccdist/WindRiver/vxworks-6.3/target/h > --disable-shared --disable-libssp --disable-multilib --with-float=hard > --enable-languages=c,c++ --enable-threads=vxworks --without-gconv > --disable-libgomp --disable-nls --disable-libmudflap --with-cpu-PPC603 > > I don't use --with-sysroot; I use --with-headers. So do I need to use > a different configuration? And how can I achieve the same effect > using --with-sysroot as I did with --with-headers if that *is* the > issue. As the installation doc says, the --with-sysroot option is the new replacement for the --with-headers option. So if you can, try using --with-sysroot. Otherwise, I'm not entirely sure. The Makefile rules for running fixincludes are pretty tangled. Ian
