Re: configure of base doesn't detect my ffcall

[Lars Sonchocky-Helldorf]

Am Dienstag, 28.09.04 um 22:50 Uhr schrieb <d.ayers@inode.at>:

> > On Sep 28, 2004, at 7:14 AM, Lars Sonchocky-Helldorf wrote:
> > > localhost:~/GNUstep-Darwin/test lars$ /opt/local/bin/gcc -E
> > > -I/opt/local/include  -fgnu-runtime
> > > -I/opt/local/GNUstep/System/Library/Headers conftest.c
> > > cc1: warning: command line option "-fgnu-runtime" is valid for
> > > ObjC/ObjC++
> > > but not for C
> > > # 1 "conftest.c"
> > > # 1 "<built-in>"
> > > # 1 "<command line>"
> > > # 1 "conftest.c"
> > > # 12653 "configure"
> > > # 12765 "configure"
> > > # 1 "/usr/include/objc/objc-api.h" 1 3 4
> > > # 12766 "configure" 2
> > > localhost:~/GNUstep-Darwin/test lars$
> > >
> > > as one can see here the wrong objc-api.h is found: the one of the 
> > > NeXT
> > > runtime.
> >
> > 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.

-x objective-c (this is the right spelling) helps but only if -E is not 
specified.

> OTOH, it may be more feasable to patch gcc to
> allow -fgnu-runtime/-fnext-runtime flags for regular C code also, since
> this controls the header search paths.

The C++ maintainers will jump on you full of hatred for that 
suggestion. Don't you know how hard they're already fighting ObjC++ ;-)

> Good luck!
> David

regards, Lars