Ah, OK (on the 1.0.1 beta)
I agree with your reasoning and surprise on the misalignment (regarding
the appending, etc), but there it is. I am referring to my 3rd party
application, I didn't bother to inspect the openssl.exe. Also, it
doesn't _always_ wind up this way (though always for me,
Looks like it is still there in 1.0.0g
Again, it's an alignment issue of function pointers put into an array
processed by the C-runtime normally used for doing things like global
constructors.
Its in crypto/perlasm/x86_64-xlate.pl:558
Currently:
$v.= READONLY DWORD;
Should be:
configuration:
* openssl 1.0.0.e
* Win64, DS2010 toolchain
* static library
* default (using asm modules) configuration
When built in above configuration, a linking application will crash in
c-runtime startup code (i.e. before reaching main()).
This is due to some linker magic which causes
configuration:
* openssl 1.0.0.d
* Win32, VC6
* static library
(I don't know if the problem is confined to that configuration, but it's
what I'm using).
There appear to be two versions of opensslconf.h that are generated from
the Configure script. One is placed in ./include/openssl, and
/openssl/*.h
makes sure these will be.
Cheers,
Richard
In message
rt-3.4.5-52058-1305706213-1353.2519-2...@openssl.org on
Wed, 18 May 2011 10:10:13 +0200 (CEST), dave via RT
r...@openssl.org said:
configuration:
* openssl 1.0.0.d
* Win32, VC6
* static library
(I don't know
Hi everyone: we are a little new to OpenSSL, and recently upgraded our
distribution to 9.7c. I'm building on a BS2000 host. Everything builds
happliy, and make test runs for a while, then starts reporting errors in MD4
tests.
Before I start digging, I'd like to save a little time: Does
