Ralf Wildenhues wrote:
In theory: no run paths for paths that the runtime linker searches by default. Otherwise, rpaths for all libraries we link directly against. (Omitting the minor detail that we care about the difference of uninstalled vs. installed locations, for simplicity.)
If I read the above threads correctly there are some problems determining the runtime paths automatically (mainly because gcc doesn't give the complete picture). In this case, user assistance is acceptable, so would adding a -R to the libtool invocation make it stop adding rpaths?
Is there perhaps also some environment variable that can be used to pass this information? That would allow "make RPATHENV=/usr/lib64" and I wouldn't have to mess with the build system.
Thanks -- Pierre Ossman Telephone: +46-13-21 46 00 Cendio AB Web: http://www.cendio.com _______________________________________________ http://lists.gnu.org/mailman/listinfo/libtool
