[openssl-users] mingw 64-bit build of 1.1.0e

Matt Caswell matt at openssl.org
Sun Mar 12 00:13:57 UTC 2017



On 12/03/17 00:06, sisyphus1 at optusnet.com.au wrote:
> -----Original Message----- From: sisyphus1 at optusnet.com.au
> Sent: Saturday, March 11, 2017 10:21 PM
> To: openssl-users at openssl.org
> Subject: [openssl-users] mingw 64-bit build of 1.1.0e
> 
>> In the msys2 shell, I run:
>>
>> ./config no-shared zlib -IC:/_64/msys_630/1.0/local/include
>> -LC:/_64/msys_630/1.0/local/lib --prefix=C:/_64/msys_630/1.0/local &&
>> make && make test && make install
>>
>> Works beautifully ... except that libssl.a and libcrypto.a turn out to
>> be 32-bit builds !!
>> That is, the built library works fine with the same vendor's 32-bit
>> compiler (gcc version 6.3.0 (i686-posix-sjlj-rev1, Built by MinGW-W64
>> project)), but the x64 compiler that built the damned things regards
>> them as incompatible.
>>
>> I'm thinking that I just need to specify an -m64 switch in there. How
>> do I do that ?
> 
> After another couple of hours fossicking about, I did it by firstly
> setting the CC environment variable to 'gcc -m64'. (I would normally do
> that by specifying 'CC="gcc -m64"' as part of the ./config command, but
> ./config found that to be objectionable, so I pre-set it in a separate
> command prior to running ./config.)
> And I added '-m64' as a ./config arg.
> 
> I don't know if *both* of those steps were necessary, but it did the trick.
> 
> Disconcertingly, the summary at the end of ./config still announces
> "THIRTY_TWO_BIT mode" but, at the end of the build, I definitely have
> the X64 libraries that I wanted.

Did you just try:

perl Configure mingw64 no-shared zlib


Matt



More information about the openssl-users mailing list