Date: Tue, 23 Feb 2010 12:56:29 +0100 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: Stephen Hurd <shurd@sasktel.net> Cc: Ronald <followait@163.com>, "Freebsd-Chat@Freebsd.Org" <freebsd-chat@freebsd.org> Subject: Re: Where to put private lib files? Message-ID: <864ol817yq.fsf@ds4.des.no> In-Reply-To: <4B83B4AA.3030405@sasktel.net> (Stephen Hurd's message of "Tue, 23 Feb 2010 02:57:46 -0800") References: <DD958BBC52D94F79855244E6890704DB@jqslaptop> <868wak2sv5.fsf@ds4.des.no> <4B83B4AA.3030405@sasktel.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Stephen Hurd <shurd@sasktel.net> writes:
> Dag-Erling Smørgrav <des@des.no> writes:
> > The canonical location for ports is ${LIBDIR}/${PORTNAME}, but
> > remember that unless these are run-time loadable modules, this
> > directory must be in the library search path when you run the app.
> > This means that you either have to ldconfig the directory using an
> > rc_subr script (which defeats the purpose of having a private
> > library directory) or install a wrapper that sets LD_LIBRARY_PATH
> > before execing the real binary.
> You can also compile in a search path.
Not PREFIX-safe, hence not allowed in ports unless there is no other
solution.
DES
--
Dag-Erling Smørgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?864ol817yq.fsf>