OK, these tests are using SimGear and FlightGear CVS snapshots from about 29th Jan,
Cygwin (similar date) on W2K, gcc 3.2.
When configuring SimGear:
"./configure --with-metakit=/usr/local" (or "./configure
--with-metakit=/usr/local/lib") both fail at the MetaKit version check. I should note
though that it appears to find mk4.h successfully, but it is the version check that
fails.
"LDFLAGS=-L/usr/local/lib ./configure" runs configure correctly to the end and creates
all the Makefiles.
Then, with a minor tweak to .../simgear/sky/Makefile to remove the clouds3d directory,
SimGear builds and installs correctly.
Same requirements apply to configuring FlightGear, which then builds and installs
happily.
No errors or warnings from gcc about /usr/local/* that I could see.
Does that help?
Whilst we are on the subject of gcc warnings, when building on recent Cygwin
installations, you get warnings like this:
In file included from hud.hxx:34,
from hud_card.cxx:2:
../../src/Include/config.h:245:1: warning: "WIN32" redefined
In file included from /usr/include/w32api/windows.h:48,
from /usr/include/plib/ul.h:102,
from /usr/include/plib/sg.h:28,
from hud_card.cxx:1:
/usr/include/w32api/windef.h:29:1: warning: this is the location of the
previous
definition
fairly often. The fix is to remove the definition of WIN32 from
.../src/Include/config.h, but I think this is an auto generated file, so I get lost
right about now when trying to fix it.
Richard
> -----Original Message-----
> From: Curtis L. Olson [mailto:[EMAIL PROTECTED]]
> Sent: 17 February 2003 1:38 pm
> To: [EMAIL PROTECTED]
> Subject: RE: [Flightgear-devel] Compile problem with Metakit
>
>
> Michael Basler writes:
> > Bernie,
> >
> > > There already is a --with-metakit=DIR option to
> configure. Conversely you
> > > specify CPPFLAGS and LDFLAGS on the command line to
> configure thus:
> >
> > Is there a similar option to tell FlightGear where to look
> for the Simgear
> > libs, as they hit the same problem? - I still would prefer
> having this
> > working by default without any options. The average user just types
> > ./configure and sits back.
>
> Ok, looking in configure.ac, the --with-metakit=/path/to/metakit
> option simply adds the specified path to EXTRA_DIRS. We used to add
> /usr/local to EXTRA_DIRS automatically, but this was removed because
> it was causing problems for gcc-3.x. Question for those with gcc-3.x:
> does the --with-metakit=/path option also cause problems/warnings
> compiling?
>
> It would be *very* simple to add /usr/local back in to the list of
> subdirectories that are checked and added automatically.
>
> Someone needs to tell me specifically why gcc-3.x was complaining
> about this and what can be done about it. I can't imagine that
> gcc-3.x prevents you from including or linking against anything in the
> /usr/local tree.
>
> Curt.
> --
> Curtis Olson IVLab / HumanFIRST Program FlightGear Project
> Twin Cities [EMAIL PROTECTED] [EMAIL PROTECTED]
> Minnesota http://www.menet.umn.edu/~curt
http://www.flightgear.org
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
________________________________________________________________________
This e-mail has been scanned for all viruses by Star Internet. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
