I have figured out why these are now being pulled in - a change was made
unknown to me in our code which triggered it.
Please close this bug report and accept my humble apologies.
Chris Brook

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Chris Brook via RT
Sent: Friday, November 22, 2002 4:35 AM
Cc: [EMAIL PROTECTED]
Subject: [openssl.org #357] Shared in 0.9.7 B4



Has something changed in the make process in beta 4 regarding shared
libraries?  I am building OpenSSL with the same shell script on my Solaris
(see below), using Workshop/Forte 6, as I did with Beta 3 versions and now I
get unreferenced symbols: dlclose, dlsym, dlopen, etc.  I can get around it
by including -ldl in my app makefiles but I never had to in the past.  I
have "shared" in my Configure command line and this, as usual, produces
libcrypto.a and libcrypto.so.  I only use libcrypto.a when building my apps,
so why is it suddenly needing the dso/dl stuff?  My last B3 build was the
20021025 snapshot.  My app makefiles have not changed.  My Configure command
line is:

..../Configure threads shared no-asm no-hw no-ripemd no-idea no-bf no-cast
no-dh no
-mdc2 no-rc2 no-rc5 debug-solaris-sparcv9-cc

Any advice much appreciated.
Chris Brook


______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to