develooper Front page | perl.perl5.porters | Postings from May 2018

[perl #128631] Win32 MinGW build failure

Thread Next
From:
sisyphus@cpan.org via RT
Date:
May 11, 2018 23:01
Subject:
[perl #128631] Win32 MinGW build failure
Message ID:
rt-4.0.24-11202-1526001274-83.128631-15-0@perl.org
On Thu, 10 May 2018 05:58:06 -0700, shay wrote:

> 
> Does anyone know what version is reported by "the fatally flawed
> mingwrt-4.x variants" reported? Is that what my 4.8.1 setup is using,
> despite reporting itself as 3.20? Or are there versions that report
> themselves as 4.x?

My take regarding 4.x is that all we need to do is assume that mkstemp() is not defined for runtimes that report __MINGW32_MAJOR_VERSION as 4 - and code accordingly.

> I've only just discovered that new mingw.org compilers (v5 and v6)
> even exist. But knowing this now, I wonder if this should be a 5.28
> blocker?

Fiddling with it now could be a little risky in that mingw-w64 compilers also define __MINGW32_MAJOR_VERSION and __MINGW32_MINOR_VERSIO - and UIM we definitely don't want them to start doing things differently.
However, mingw-w64 compilers seem to always define those values as "3" and "11" respectively and that would mean we could fiddle with __MINGW32_MAJOR_VERSION and __MINGW32_MINOR_VERSION without altering mingw-w64 behaviour (because we're not going to mess with anything less than 3.21, right ?).

I've checked my mingw-w64 compilers from 4.7.0 through to 7.2.0, and __MINGW32_MAJOR_VERSION and __MINGW32_MINOR_VERSION are always 3 and 11. It's __MINGW64_VERSION_MAJOR, __MINGW64_VERSION_MINOR that correctly identify their runtime version numbers.
However, I haven't checked for every mingw-w64 compiler. What are the chances ?

Cheers,
Rob





---
via perlbug:  queue: perl5 status: open
https://rt.perl.org/Ticket/Display.html?id=128631

Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About