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

sisyphus1 at optusnet.com.au sisyphus1 at optusnet.com.au
Sun Mar 12 05:15:47 UTC 2017


-----Original Message----- 
From: Richard Levitte
Sent: Sunday, March 12, 2017 3:25 PM
To: openssl-users at openssl.org
Subject: Re: [openssl-users] mingw 64-bit build of 1.1.0e

> Just add -m64 on the config line, like this:
>
> ./config no-shared zlib -m64 -IC:/_64/msys_630/1.0/local/include \
> -LC:/_64/msys_630/1.0/local/lib --prefix=C:/_64/msys_630/1.0/local
>
> This is weird, though...  what config target did you get when configuring? 
> Ideally, you should have gotten 'mingw64', which already uses the -m64 
> flag, so what gives?  If you show us the config output, maybe we can help 
> you figure out what actually goes wrong...
>

Hi Richard,

The command I originally tried was
./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

For that command, the config is in the attached conf0.txt.

If I add the '-m64' switch, then the output (see conf1.txt) changes very 
little.
According to diff, the only change is the insertion of '-m64' in the "CFLAG" 
line.

Having included the '-m64' switch, if I then proceed to run 'make', I very 
quickly get a long list of assembler error messages pertaining to push, pop, 
pushf and popf:

crypto/aes/aes-586.s: Assembler messages:
crypto/aes/aes-586.s:969: Error: invalid instruction suffix for `push'
...
crypto/aes/aes-586.s:970: Error: invalid instruction suffix for `pop'
...
crypto/aes/aes-586.s:2233: Error: invalid instruction suffix for `pushf'
...
crypto/aes/aes-586.s:2350: Error: invalid instruction suffix for `popf'
...

(Adding the no-asm switch to ./config works around that particular problem.)

Matt suggested running 'perl Configure mingw64 no-shared zlib'.
The config output for it is in the attached conf2.txt, and is much more in 
keeping with expectations.

I'm quite happy to continue building openssl by running that perl command.
I'm also happy to assist with investigating the problem that led to my 
original post.

Cheers,
Rob
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: conf0.txt
URL: <http://mta.openssl.org/pipermail/openssl-users/attachments/20170312/ffd161f4/attachment.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: conf1.txt
URL: <http://mta.openssl.org/pipermail/openssl-users/attachments/20170312/ffd161f4/attachment-0001.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: conf2.txt
URL: <http://mta.openssl.org/pipermail/openssl-users/attachments/20170312/ffd161f4/attachment-0002.txt>


More information about the openssl-users mailing list