On Sep 28, 2004, at 2:50 PM, <d.ayers@inode.at> wrote:
You need to have /opt/local/bin in your path. gcc also uses cpp, and
it's probably finding Apple's cpp in /;usr/bin instead of the one you
want in /opt/local/bin
Let me jump in here: I believe the issue ist that this is the
"mainline"
gcc (4.0) for which Andrew Pinski went through the motions to have
the GNU
runtime reenabled but with a few nifty tweaks so that the NeXT
runtime is
neither clobbered nor hidden. The flag that controls which headers
are
searched is -fgnu-runtime/-fnext-runtime. Yet this flag is only
available
for ObjC and the configure test is only compiling a regular C
programm. I
hope that adding a "-x Objective-C" in the confiugure compiler flags
can
temporarily deal with this. OTOH, it may be more feasable to patch
gcc to
Well, then it appears there are two problems, the one that I
mentioned, plus this one, which I'm
guessing would make cpp look in
/opt/local/lib/gcc/i686-apple-darwin7.2.1/4.0.0/include-next-runtime
for those files instead of
/opt/local/lib/gcc/i686-apple-darwin7.2.1/4.0.0/include-gnu-runtime