> Did you modify the configuration scripts to set up the single library or =
> did you just edit the makefiles directly? That is the issue I am looking =
> into now. (If you have anything you want to share, we'd love to see it.)
After building openssl normally, we run the following script. Note that
we're after the magic "-Bsymbolic" option, which binds internal library
calls at link time instead of runtime; this prevents external symbols
(from our application or from other shared libraries) from over-riding
symbols in the OpenSSL library.
Sometimes you want the exact opposite behaviour, naturally...
(This works for 0.9.6 releases too; change the version number).
----- build-symbolic -----
#!/bin/sh
case `uname -s` in
Linux)
gcc -g -shared -o libopenssl.so.0.9.7 \
-Wl,-Bsymbolic \
-Wl,-soname=libopenssl.so.0 \
-Wl,--whole-archive libssl.a libcrypto.a \
-Wl,--no-whole-archive -ldl -lc
;;
SunOS)
gcc -v -g -shared -mimpure-text -o libopenssl.so.0.9.7 \
-Wl,-B,symbolic \
-Wl,-hlibopenssl.so.0 \
-Wl,-zallextract libssl.a libcrypto.a \
-Wl,-zdefaultextract -lsocket -lnsl -lc
;;
esac
/bin/rm -f libopenssl.so.0
ln -s libopenssl.so.0.9.7 libopenssl.so.0
/bin/rm -f libopenssl.so
ln -s libopenssl.so.0 libopenssl.so
----- build-symbolic -----
--
Harald Koch <[EMAIL PROTECTED]>
"It takes a child to raze a village."
-Michael T. Fry
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
