Jon Berndt writes: > > > It *appears* that g++ isn't searching /usr/local/lib automatically for > > libraries. You might want to try configuring FlightGear with > > something like: > > > > LDFLAGS="-L/usr/local/lib" ./configure > > > > That's a can of worms where differnet people think different things > > about /usr/local and it cause some grief to the end users. > > Hmmm. I don't get this. I'm using the same build process I've been using > for years. SimGear builds and installs. FlightGear was built and installed a > few months ago.
Have you upgraded cygwin (your compiler) in the mean time? I believe that is where the critical change happened. > Is there a place in a Makefile where I can check to see which path is, in > fact, being used? Be aware that the user editable file is Makefile.am. When the autotools are run, a Makefile.in is created from every Makefile.am. Then when you run the configure script, the actual Makefile's are generated from all the Makefile.in's. So, just bear that in mind when you look through the final Makefile's. There will a be a ton of machine generated stuff in them. > I'll give that a try. There is no try, only do. :-) Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities curt 'at' me.umn.edu curt 'at' flightgear.org 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
