Hi, Guenter. All I did was add $(SSLLIBS) and $(WINLIBS) in the LNK line in Makefile.VC6 as the release-ssl config did not include them out of the box. Not sure why I'm getting the warnings.

Here's a sample:

ssleay32.lib(ADVAPI32.dll) : warning LNK4006: _ConvertSecurityDescriptorToString
SecurityDescriptorA_at_12 already defined in libeay32.lib(ADVAPI32.dll); second def
inition ignored

I get tons of warnings similar to that.

It looks like ssleay32.lib and libeay32.lib duplicate some (or all) of the symbols. What do you think could cause this? I did not do anything special to OpenSSL. Just followed the instructions to build it. Did you have to do something not in the documentation before building OpenSSL?

By the way, the _BN_* linker errors are gone. Apparently, the RSA Crypto-C library that I was using had conflicts with OpenSSL. RSA asked us to use a later version, which fixed the problem.

Thanks,
Ever

----------------------------------------------------------------------

Message: 1
Date: Mon, 28 Jun 2004 18:15:54 +0200
From: Guenter Knauf <eflash_at_gmx.net>
Subject: Re: Linking problems (_BN_* stuff)
To: curl-library_at_cool.haxx.se
Message-ID: <ye02DcmMQ2Fcymiiz6J6aol4Qn2pPmT77ESswhnoitk_at_akmail>
Content-Type: text/plain; charset=us-ascii

Hi Olano,
I dont know what you're hacking in the makefiles; if you set the paths right and call:
nmake vc-ssl
all goes fine without any warning; just look at:
http://curl.haxx.se/auto/log.cgi?id=20040628180032-27355
where you can see the buildlog from my build I've just done....

Guenter.
Received on 2004-06-29