[openssl-dev] Build issue

[Matthew Stickney]

Aha, victory! Turns out this was a line-ending problem: after removing
the mingw perl, the mkdef.pl debug output had (among many, many other
things), the following when I went looking for MD2 references:

> DEBUG: include/openssl/md2.h: found tag OPENSSL_NO_MD2^M = -1

I checked, and sure enough the md2 header had windows line endings.
core.autocrlf was false, and core.eol was lf, so I'm not sure how only
some headers had the wrong line endings, but an "rm -rf * && git
checkout ." produced a working build.

Thanks for the time and assistance, everybody.

-Matt Stickney

On Wed, Aug 2, 2017 at 4:07 AM, Matt Caswell <matt at openssl.org> wrote:
>
>
> On 02/08/17 03:19, Matthew Stickney wrote:
>> Ok, progress (sort of)! It turns out I was indeed using the wrong
>> version of perl -- I was using the perl that was installed as part of
>> the msys2 base-devel group, not the mingw-w64-<arch>-perl package,
>> which is a whole separate thing.
>
>
> Errr no. You were right the first time - you should be using the msys2
> perl. This is my perl --version output:
>
> This is perl 5, version 22, subversion 1 (v5.22.1) built for
> x86_64-msys-thread-multi
>
> Do NOT use the mingw perl (I think Richard misspoke when he said this
> before - the "matching perl" requirement means that using msys2 shell
> requires msys2 perl).
>
> Just to check - you are using the msys2 shell right?
>
> Matt
>
>
>>
>> However, having installed the mingw-w64 version of perl, the configure
>> script is failing because it thinks this is a unix-like platform, but
>> perl is producing windows-style paths:
>>
>>> This perl implementation doesn't produce Unix like paths (with forward slash
>>> directory separators).  Please use an implementation that matches your
>>> building platform.
>>
>>> This Perl version: 5.22.0 for MSWin32-x64-multi-thread
>>
>> I can't follow the configure script well enough to tell where it's
>> detecting the relevant bits from -- the build_scheme key seems to be
>> responsible for triggering the unix-checker.pm script that fails, but
>> grep only turns up two references to it: the readme, and the configure
>> script. Is this an issue with msys2+mingw-w64 environments?
>>
>> -Matt Stickney
>>
>> On Tue, Aug 1, 2017 at 8:54 AM, Sergio NNX <sfhacker at hotmail.com> wrote:
>>>> Ok, I have still not been able to reproduce this.
>>>
>>> Neither have I!
>>>
>>>
>>> I've just downloaded OpenSSL 1.1.0f and built it from source.
>>>
>>> This is my configuration:
>>>
>>>
>>> Microsoft Windows [Version 10.0.15063]
>>>
>>> This is perl 5, version 24, subversion 1 (v5.24.1)
>>>
>>> GCC v6.3.0 (64-bit)
>>>
>>>
>>> ./config mingw64  ........
>>>
>>> make depend
>>>
>>> make all
>>>
>>>
>>> After a while, I get the executable and libraries.
>>>
>>>
>>> OpenSSL 1.1.0f  25 May 2017
>>> built on: reproducible build, date unspecified
>>> platform: mingw64
>>>
>>>
>>> perl util/mkdef.pl 32 crypto debug 2> mkdef-debug.txt > /dev/null
>>> [It generates a huge file (125MB)]
>>>
>>> Cheers.
>>>
>>> Ser/
>>>
>>>
>>> P.S.: Try to use a more specific subject next time!
> --
> openssl-dev mailing list
> To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev