os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Clarify unexpected consequences of setting LDCONFIG_DIRS.

Browse source 
PR:		docs/88454
Approved by:	simon
This commit is contained in:
Volker Stolz 2005-11-04 09:23:27 +00:00
parent 1aeb634f65
commit 67d272896f
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=26219
1 changed files with 11 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
en_US.ISO8859-1/books/porters-handbook/book.sgml
View file

@ -3869,6 +3869,17 @@ PORTVERSION= 1.0</programlisting>
<programlisting>INSTALLS_SHLIB= yes
LDCONFIG_DIRS= %%PREFIX%%/lib/foo %%PREFIX%%/lib/bar</programlisting>
<para>Remember that non-standard directories will not be passed to
&man.ldconfig.8; on (re-)boot! If any port really
needs this to work, install a startup-script as
<filename role="package">x11/kdelibs3</filename> does. Please
double-check, often this is not necessary at all or can be avoided
through <literal>-rpath</literal> or setting <envar>LD_RUN_PATH</envar>
during linking (see <filename role="package">lang/moscow_ml</filename>
for an example), or through a shell-wrapper which sets
<makevar>LD_LIBRARY_PATH</makevar> before invoking the binary, like
<filename role="package">www/mozilla</filename> does.</para>
<para>Note that content of <makevar>LDCONFIG_DIRS</makevar> is passed
through &man.sed.1; just like the rest of <filename>pkg-plist</filename>,
so <makevar>PLIST_SUB</makevar> substitutions also apply here. It is