>>>> "SJT" == Stephen J Turnbull
<stephen(a)xemacs.org> writes:
>>>> "plynchnlm" == plynchnlm
<plynchnlm(a)netscape.net> writes:
plynchnlm>
--site-runtime-libraries=/proj/3rdparty/lib
> From configure --help:
SJT> --site-runtime-libraries=PATH List of ALL directories to search for
SJT> dynamically linked libraries at run time
SJT> Note the "ALL".
SJT> What that switch does is allow you to create an executable by
SJT> resolving symbols against the libraries in the -L paths, and then sets
SJT> the runtime search path to exclude any -L paths not explicitly listed.
SJT> I have no idea why it is that way;
Suppose you build with libraries in /net/polgar/lib/
Your xemacs is built with a runpath containing /net/polgar/lib.
You install xemacs.
You leave the company.
One year later, the machine "polgar" is shut down.
Everytime someone starts xemacs, it now takes 5 minutes to start up
because of the hang accessing the NFS directory /net/polgar/lib.
Even though no library in /net/polgar/lib is being used.
No one can figure out why.