I agree. If a user sucessfully builds and installs a package to it's default location, it is reasonable to expect that subsequent ./configures would find that package.
Richard > -----Original Message----- > From: Michael Basler [mailto:[EMAIL PROTECTED]] > Sent: 17 February 2003 10:48 am > To: [EMAIL PROTECTED] > Subject: RE: [Flightgear-devel] Compile problem with Metakit > > > 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. > > Regards, Michael > > -- > Michael Basler, Jena, Germany > [EMAIL PROTECTED] > http://www.geocities.com/pmb.geo/ > > > > > > _______________________________________________ > 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
