Hi,
   Here's the text I came up with:

----------------------------------------------------------------------
OpenSSL Shared Libraries have been installed in:
   [directory name]

If this directory is not in a standard system path for dynamic/shared
libraries, then you will have problems linking and executing
applications that use OpenSSL libraries UNLESS:

* you link with static (archive) libraries.  If you are truly
  paranoid about security, you should use static libraries.
* you define the LD_LIBRARY_PATH or SHLIB_PATH (HP) environment
  variable and add [directory name] to it, and use the -L linker
  option.
* you use the GNU libtool code during linking
  (http://www.gnu.org/software/libtool/libtool.html)
* you specify the the system-wide link path via a command such as
  crle(1) on Solaris systems.

One common tool to check the dynamic dependencies of an executable
or dynamic library is ldd(1) on most UNIX systems.

See any operating system documentation and manpages about shared
libraries for your version of UNIX.  The following manpages may be
helpful: ld(1), ld.so(1), ld.so.1(1) [Solaris], dld.sl(1) [HP],
ldd(1), crle(1) [Solaris], pldd(1) [Solaris].
----------------------------------------------------------------------

I looked at the Makefile to see where it might go.  "make install"
invokes "make link-shared" near the end of the install process.  The
text could be printed at that point.  A really good way to do this
would be to have the text above broken into two pieces, one generic
for all UNIX, and one specific to the OS.  The specific piece could
be printed out perhaps when the Makefile do_$(SHLIB_TARGET) target
is invoked.  That way the quirks of dynamic loading on Solaris, HP,
Linux, could be explained and the correct manpages referenced.

--- Jeff

On Wed, 1 Jan 2003, Richard Levitte - VMS Whacker via RT wrote:

> Date: Wed,  1 Jan 2003 14:58:09 +0100 (MET)
> From: Richard Levitte - VMS Whacker via RT <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: [openssl.org #423] openssl-0.9.7-stable-SNAP-20021229: ldd
>     problems
>
>
> In message <[EMAIL PROTECTED]> on Wed,  1 Jan 2003 13:36:23 
>+0100 (MET), "Jeff A. Earickson via RT" <[EMAIL PROTECTED]> said:
>
> rt> "man crle" on a Sun box. It is:
>
> Not on the machine I currently have access to :-):
>
> $ man crle
> No manual entry for crle.
>
> rt> crle - configure runtime linking environment
> rt>
> rt> which determines the search path for dynamic libs.  I had forgotten
> rt> that I had added /opt/openssl/lib to this path.  When I was testing
> rt> 0.9.7 in various forms, I installed it in /opt/openssl-0.9.7, but
> rt> forgot to add the path via crle.  So I couldn't get dynamic loading
> rt> to work and was going nuts...
>
> Can you recommend some piece of text that should be output?
>
> --
> Richard Levitte   \ Spannvägen 38, II \ [EMAIL PROTECTED]
> Redakteur@Stacken  \ S-168 35  BROMMA  \ T: +46-8-26 52 47
>                     \      SWEDEN       \ or +46-708-26 53 44
> Procurator Odiosus Ex Infernis                -- [EMAIL PROTECTED]
> Member of the OpenSSL development team: http://www.openssl.org/
>
> Unsolicited commercial email is subject to an archival fee of $400.
> See <http://www.stacken.kth.se/~levitte/mail/> for more info.
>
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to