Openssl 1.0.2t build failed using Visual Studio

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Openssl 1.0.2t build failed using Visual Studio

Fabrice Manfroi
Hello,

Trying to build the last 1.0.2t on Windows with Visual Studio 2010, I
get the following build error:

===

LIBEAY32.def : error LNK2001: unresolved external symbol OPENSSL_rdtsc

===

If I remove the OPENSSL_rdtsc entry from the util/libeay.num file it
works without any probleme.

Is it a error? Or do I miss something?

Best Regards.




signature.asc (499 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Openssl 1.0.2t build failed using Visual Studio

Matt Caswell-2


On 12/09/2019 10:29, Fabrice Manfroi wrote:

> Hello,
>
> Trying to build the last 1.0.2t on Windows with Visual Studio 2010, I
> get the following build error:
>
> ===
>
> LIBEAY32.def : error LNK2001: unresolved external symbol OPENSSL_rdtsc
>
> ===
>
> If I remove the OPENSSL_rdtsc entry from the util/libeay.num file it
> works without any probleme.
>
> Is it a error? Or do I miss something?

I don't get this with VS2013 (the oldest version I have) so it may be a Visual
Studio version specific problem.

OPENSSL_rdtsc is only relevant on some platforms, and isn't present on others
which is why this problem occurs. Perhaps later Visual Studio versions are more
tolerant of this? Removing the entry from util/libeay.num is fine as a
workaround for now, and won't cause any adverse impacts.

Matt
Reply | Threaded
Open this post in threaded view
|

Re: Openssl 1.0.2t build failed using Visual Studio

Bin Ichiki
The same build error is occurred by visual studio 2017 community edition.
Specified Configure options is VC-WIN64A and no-asm.