From: Dave Dykstra <[EMAIL PROTECTED]>
dwd> I meant to say that I would like to be able to have the source use static
dwd> libraries without having to change some files every time there's a new
dwd> release, and without having to remove the system-installed copies of the
dwd> shared libraries. Below is the patch I had to apply to get that to work,
dwd> but those files are not currently generated by Configure so I don't know
dwd> how to automate it.
There's no way to get what you want generated by Configure, at least
currently. Also, IIRC, on most Unixen, linking with libcrypto.a
rather than -lcrypto makes the linker suck in everything from that
library, regardless of if they are needed or not, while -lcrypto makes
the linker select the needed object files. I may be wrong about this.
I thought someone once made a patch that used some special option to
the linker so it wouldn't use system libraries at all, and then
explicitely included needed system libraries at the end of the linking
command line. It seems to me like that would be the best way to act,
really, provided those system libraries aren't renamed or moved to
different locations.
Anyone?
--
Richard Levitte \ Spannvägen 38, II \ [EMAIL PROTECTED]
Redakteur@Stacken \ S-168 35 BROMMA \ T: +46-8-26 52 47
\ SWEDEN \ or +46-733-72 88 11
Procurator Odiosus Ex Infernis -- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/
Software Engineer, GemPlus: http://www.gemplus.com/
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]
