This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
xgcc seems to ignore C_INCLUDE_PATH
- To: egcs-bugs at egcs dot cygnus dot com
- Subject: xgcc seems to ignore C_INCLUDE_PATH
- From: Eric Buddington <eric at 3com136 dot vgernet dot net>
- Date: Mon, 5 Jul 1999 19:30:34 -0400 (EDT)
- Reply-To: ebuddington at wesleyan dot edu
I'm trying to compile egcs on a non-standard system. The system headers
are not under /usr/include.
In all cases so far, setting C_INCLUDE_PATH and CPLUS_INCLUDE_PATH has
worked perfectly.
However, when compiling egcs-1.1.2 itself, I get the following error:
----------------------------------------------------------------------
./xgcc -B./ -DIN_GCC -O2 -g -mcpu=i586 -march=i586 -I./include -I.
-I/src/build-src/egcs-1.1.2/egcs-1.1.2/gcc
-I/src/build-src/egcs-1.1.2/egcs-1.1.2/gcc/config -fgnu-runtime -c
/src/build-src/egcs-1.1.2/egcs-1.1.2/gcc/objc/NXConstStr.m -o
objc/NXConstStr.o
In file included from include/objc/Object.h:31,
from include/objc/NXConstStr.h:31,
from
/src/build-src/egcs-1.1.2/egcs-1.1.2/gcc/objc/NXConstStr.m:28:
include/objc/typedstream.h:32: stdio.h: No such file or directory
----------------------------------------------------------------------
...even though C_INCLUDE_PATH and CPP_INCLUDE_PATH are set to point
to the directory that contains stdio.h et al. Adding the same directory to
the command as -I$C_INCLUDE_PATH allows the file to compile normally.
Unfortunately, strace -f mysteroiusly fails to show any attempted access
to program files/headers, or even the creation of a child process (though
there's a wait() in there. But that's not your problem.
So does xgcc ignore the C_INCLUDE_PATH environment variable, and is this
necessary? It is the only thing that prevents me from compiling stock egcs
in a completely non-privileged environment. As it stands, I have to either
symlink from /usr/include or tweak the egcs source.
-Eric
ebuddington@wesleyan.edu