In message <[EMAIL PROTECTED]> on Mon, 22 Mar 2004 14:33:59 +0100 (MET), "[EMAIL PROTECTED] via RT" <[EMAIL PROTECTED]> said:
rt> Libeay32 linked fine. I got the problems when linking ssleay32. It rt> complained about 2 unresolved symbols. I ended up copying the rt> "asn1_lib.obj" line from the CRYPTOOBJ dependency section and pasting it rt> into the SSLOBJ dependency section. That seemed to solve the problem. That is weird. When linking ssleay32, there should really be no problems, as it's just about putting together all the object files that belong there. When linking *an application* against ssleay32, you must not forget to also link against libeay32. Maybe that's what's missing? Could you say which two symbols are missing? ----- Please consider sponsoring my work on free software. See http://www.free.lp.se/sponsoring.html for details. -- Richard Levitte \ Tunnlandsv�gen 52 \ [EMAIL PROTECTED] [EMAIL PROTECTED] \ S-168 36 BROMMA \ T: +46-708-26 53 44 \ SWEDEN \ 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]
