Re: Shared libraries on Solaris (ITS#376)

[bbense@networking.stanford.edu]

On Sat, 4 Dec 1999, Kurt Zeilenga wrote:

> There is no portable way to ensure that a executable built in
> one environment will run in another environment.  We require
> the installer to tune their environment such that the built
> executable will run in most user environments.
> 
> That is, if the installer has specified to use and locate
> shared libraries not in the default search path, then the
> installer is responsible to provide options and flags (such
> as -R) to configure to ensure built executables can locate
> detected libraries at run time.
> 

- But, it is in the default search path. If the configure script
adds the -L options it should be smart enough to add the 
-R options. I didn't give it any special compile options, I
just typed configure. If the configure script is going to 
look in /usr/local without my telling it, it should be
prepared to deal with finding a shared library there. 

- I fully see your position if I had specified something 
like -L/usr/special/place, it's up to me to add the -R option. 

-If the configure script is not going to deal with it, I would
suggest that you add something to the build documentation to
warn people about the issue. 

- Booker C. Bense