Re: Shared library defines a RPATH
On Sun, 28 Jul 2002, Richard Atterer wrote:
> > Use a wrapper script that sets LD_LIBRARY_PATH?
> Why should one do that when rpath is the more elegant solution? If a
Because rpath is forbiden for a good reason. It has a lot of side-effects
that are far-reaching in the future, and this has bitten us in the arse once
> The argument "libs must be relocatable" isn't really valid in these
> cases IMHO, because the lib is usually tied closely to the binaries
The argument "it is easier to use rpath" is not valid in any case. And
rpath has more side-effects than most people realise.
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
To UNSUBSCRIBE, email to email@example.com
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org