<div><span class="gmail_quote">On 6/12/07, <b class="gmail_sendername">Bryan O'Sullivan</b> <<a href="mailto:bos@serpentine.com">bos@serpentine.com</a>> wrote:</span><blockquote class="gmail_quote" style="margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex">
> Let's see how libtool handles this situation.<br><br>I would recommend against following libtool's lead in this area.<br>Libtool's fondness for cooking RPATH into binaries makes it very<br>difficult to deal with, because it's quite common for those binaries to
<br>get installed and distributed, RPATH and all. RPATH should only be used<br>by a user who knows they have a large-calibre weapon pointed at their foot.<br></blockquote></div><br>The NetBSD Project has a different opinion and strongly encourages the use of RPATHs. Letting the user alter the lookup path for installed binaries is seen as a security problem. Since every NetBSD system has its libraries in one directory and third-party libraries are in /usr/pkg/lib, there's no problem in hardcoding the paths.
<div><br class="webkit-block-placeholder"></div><div>Just another data point...<br clear="all"><br>-- <br>Rich<br><br>JID: <a href="mailto:rich@neswold.homeunix.net">rich@neswold.homeunix.net</a><br>AIM: rnezzy
</div>