Re: [Yade-dev] ld: new problems on Mac OS X
Václav Šmilauer said: (by the date of Fri, 28 Aug 2009 20:01:45 +0200) You must find some way how to tell the linker to ignore that there symbols undefined at link time -- ClassFactory and other libs are maybe he could try compiling monolithic version? Or even the static one? -- Janek Kozicki | ___ Mailing list: https://launchpad.net/~yade-dev Post to : yade-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-dev More help : https://help.launchpad.net/ListHelp
Re: [Yade-dev] ld: new problems on Mac OS X
maybe he could try compiling monolithic version? Would be the same IMO. Or even the static one? $ scons-h ## :-( ___ Mailing list: https://launchpad.net/~yade-dev Post to : yade-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-dev More help : https://help.launchpad.net/ListHelp
Re: [Yade-dev] ld: new problems on Mac OS X
maybe he could try compiling monolithic version? Thank you Janek for your idea... Would be the same IMO. Unfortunately Vaclav is right Or even the static one? $ scons-h ## :-( ok thank you, I will try scons LIBPATH=... Does runtimePREFIX could replace the origin option? ___ Mailing list: https://launchpad.net/~yade-dev Post to : yade-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-dev More help : https://help.launchpad.net/ListHelp
Re: [Yade-dev] ld: new problems on Mac OS X
Le 29 août 09 à 14:21, Václav Šmilauer a écrit : Does runtimePREFIX could replace the origin option? No. Besides that, I think runtimePREFIX will not be needed soon as we use $ORIGIN now. Let's not confuse linking stage (at compilation) and running (when libraries are being found also). If $ORIGIN only affects running. For compilation, you have to: add the necessary libs to LIBS and also add their dirs to LIBPATH. For running, I remember vaguely that -z origin wasn't necessary, even if the libs had -rpath=\$ORIGIN/.. etc in their paths. You can verify after the build that running ldd on a plugin will find all libs automatically, without setting LD_LIBRARY_PATH. If it doesn't, set LD_LIBRARY_PATH to all lib directories (colon-separated) and run yade. ok, understood. Is the system you use for download somewhere, e.g. virtualbox images? It seems to be possible with vmware: http://wiki.osx86project.org/wiki/index.php/Vmware_how_to Thank you to be interested in this issue. VR ___ Mailing list: https://launchpad.net/~yade-dev Post to : yade-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-dev More help : https://help.launchpad.net/ListHelp
