Kanwal Preet Singh CHANANA kirjoitti:
Hi,
Following are the paths of the build directories:
Root: /cygdrive/c/build
Binutils: /cygdrive/c/build/build-binutils/binutils-2.16
Gcc: /cygdrive/c/build/build-gcc/gcc-4.0.3
Newlib: /cygdrive/c/build/build-newlib/newlib-1.14.0
$TARGET=arm-elf
$PREFIX="/cygdrive/c/build/Build"
I havent used -isystem option.Kindly suggest to solve this problem.
The new GCC (its 'xgcc') uses these '-isystem' options for
getting the target headers. So if the headers are now in
the '$PREFIX/$TARGET/sys-include', which installation the
'--with-headers=' config option should have done, then they
SHOULD be found. Otherwise your new GCC is badly broken!
The built-in search paths for headers cannot be seen directly
with the 'xgcc', one must use the 'cpp' for that. So the command:
cpp -v
given in your '$build/gcc' directory should tell where your new
GCC would search its headers WITHOUT the given '-isystem'
options... If you try it, you will see that the search happens via
relative paths and if something is missing from these paths, the
headers etc. target stuff will not be found... Then creating the
'$PREFIX/lib/gcc/$TARGET/$GCC_VERSION' helps, with your
values the '/cygdrive/c/build/Build/lib/gcc/arm-elf/4.0.3' can be
in every built-in search path and just creating it enable these
being working.... But as told, those '-isystem' options on the
'xgcc' command line should have worked ! Creating the given
directory is one workaround but your GCC remains broken if
those '-isystem' options don't work with it...
