develooper Front page | perl.perl5.porters | Postings from February 2020

Re: MinGW builds broken

Thread Previous | Thread Next
February 19, 2020 10:49
Re: MinGW builds broken
Message ID:
On Wed, Feb 19, 2020 at 7:13 PM Steve Hay <>

> ...but we can't tell what version of the runtime we're using?

For that, you look at __MINGW32_MAJOR_VERSION and __MINGW32_MINOR_VERSION
(which both mingw-w64 and define.

I expected that, with a mingw-w64 compiler, __MINGW64_VERSION_MAJOR and
__MINGW32_MAJOR_VERSION would report the same value - and same, too, for
But that's not the case.
On my mingw-w64 gcc-8.1.0, I compiled this script:

#include <stdio.h>
int main(void){
    printf("%d %d %d\n", __MINGW64_VERSION_MAJOR, __MINGW64_VERSION_MINOR,
    printf("%d %d\n", __MINGW32_MAJOR_VERSION, __MINGW32_MINOR_VERSION);
    return 0;

That outputs:

6 0 0
3 11

So, I gather mingw-w64 and mingw,org use different numbering systems for
the same runtime ??

> They released a new gcc (9.2.0) last month

This is where mingw-w64 could bring themselves undone.
They haven't provided a release since 8.1.0, and steadfastly refuse
requests to release anything more recent.
Instead they point people to the build scripts - which, I think, is a risky
business plan to be pursuing.
Now, maybe they'll get away with that but I certainly don't want to be
messing around with building gcc from source.
Luckily, Strawberry Perl build and provide a new compiler every year when
the next stable perl is released - so, these days, I just end up using the
compiler that they're providing.

I might give this version of gcc-9.2.0 a try.


Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About