On Tuesday 24 April 2007 19:10, Mathias Fröhlich wrote: > On Monday 23 April 2007, Andy Ross wrote: > > Indeed. Nonetheless, from a build just completed: > > > > $ ldd ./yasim > > libdl.so.2 => /lib/libdl.so.2 (0x00002ac79e774000) > > libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00002ac79e878000) > > libm.so.6 => /lib/libm.so.6 (0x00002ac79ea78000) > > libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002ac79ebf9000) > > libc.so.6 => /lib/libc.so.6 (0x00002ac79ed07000) > > /lib64/ld-linux-x86-64.so.2 (0x00002ac79e657000) > > > > Those extra SimGear libraries don't require anything from OSG, except > > perhaps the compile-time headers. Are you doing anything fancy like > > building SimGear as a shared library? > > Hmm, the same for me. > What symbols are missing for you link? > > Greetings > > Mathias
Hi All, After our extensive email communication, I began to realize that it should be something related to my particular setup that was causing the linker error. So last week I downloaded a SuSe upgrade, and did a system wide update this morning. After a relatively painless upgrade (it took about two hours to get the wireless card working again; but the upside is that the Samba server is running with a lot more stability), I'm now running SuSe Linux version 10.2, and I'm currently past the failing point in the FlightGear compilation process. :-) Thanks everybody who contributed to the discussion. Cheers, Durk ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
