Clemens Fruhwirth wrote:
Libtool's fondness for cooking RPATH into binaries makes it very
difficult to deal with, because it's quite common for those binaries to
get installed and distributed, RPATH and all. RPATH should only be used
by a user who knows they have a large-calibre weapon pointed at their foot.
Did I understand that correctly that you don't want to see binaries
with rpath's pointing to install directories such as /usr/lib/gcc-6.6?
That's right.
So, this forces us to use a wrapper in all cases.
Not necessarily. Many systems provide a global mechanism to manage the
paths that ld.so searches for shared objects. This is the standard on
Linux, for example (/etc/ld.so.conf). For systems that don't provide
this mechanism, one possibility would be to provide an option that cooks
the rpath in.
<b
_______________________________________________
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
