|
From: | Todd Gamblin |
Subject: | Re: Bugreport: Incorrect forwarding of a shared library's -R flags when this library is linked to an executable |
Date: | Thu, 7 Jan 2010 14:21:29 -0800 |
Ralf, On Jan 7, 2010, at 12:06 PM, Ralf Wildenhues wrote: The Another question regarding -R and compatibility with different linkers. Why does libtool draw a distinction between -R and -rpath? GNU ld treats -R plus directory name as a synonym for -rpath, so these are effectively the same once things get through libtool and down to the linker. Or am I mistaken about this? I ask because I seem to remember at one point when I was fighting with this that I could get -rpath flags to propagate, but not -R flags. The libraries that were built had the correct runpath (according to readelf), but libtool refused to install them because it claimed I was trying to install into the wrong directory. So, why does libtool attach special significance to -rpath? Is that how different runs of libtool know where particular libraries are to be installed? It seems like -rpath is understood by quite a few linkers, so why can't libtool just translate -R arguments to -rpath arguments on systems where -R isn't understood? -Todd |
[Prev in Thread] | Current Thread | [Next in Thread] |