Donn Washburn alerted me to the fgpanel build issue and he used either --prefix=/usr or --prefix=/usr/local. With openSUSE, 32-bit libraries go in /usr/local/lib or /usr/lib and 64-bit go in /usr/local/lib64 or /usr/lib64. There is also /lib and /lib64 respectively for libraries like libz.so.1. Some configure scripts have a --libsuffix to take care of that, some will only need e.g --libdir=/usr/lib64.
In Flightgear they get partially ignored and during the build you see -L/usr/local/lib and the ancient -L/usr/XFree86/lib still cropping up. Regards Sid. On 24/09/11 08:34, Mathias Fröhlich wrote: > Sid, > > On Saturday, September 24, 2011 04:09:51 Sid Boyce wrote: >> # ./configure --prefix=/usr/local/lib64 > The prefix seems suspicious to me. Probably the lib64 is too much. > > The rest what you were reporting looked somehow like a 32/64 bit mixed > objects/libs problem. No clue where this might stem from. > > Also you might need to recreate the autotools build files. May be you just > need > to run the autogen.sh. > > My problem here is that it builds fine on fedora 14/15 64 bits with the > autotools build. I have just now done one build from scratch to find lurking > problems. > > Greetings > > Mathias > -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 _______________________________________________ Flightgear-users mailing list Flightgear-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-users
