Front page | perl.perl5.porters |
Postings from February 2020
Re: MinGW builds broken
Thread Previous
From:
Steve Hay via perl5-porters
Date:
February 19, 2020 08:09
Subject:
Re: MinGW builds broken
Message ID:
CADED=K4uhLog31SayMcO2oPNrj7LA5isYdrEsBeaQP3Mjj+sHA@mail.gmail.com
On Tue, 18 Feb 2020 at 00:50, Tomasz Konojacki <me@xenu.pl> wrote:
> On Mon, 17 Feb 2020 18:03:31 +0000
> Steve Hay via perl5-porters <perl5-porters@perl.org> wrote:
>
> > In testing a patch with a variety of builds today I've found that blead
> > currently doesn't build with my mingw.org x86 compilers v3.4.5 or
> v4.8.1.
> > They both fail in Time::HiRes because of struct timespec not being known.
> >
> > They need the same magic as daacfc6568, but I'm fuzzy on the details of
> how
> > to identify a particular version of MinGW gcc and/or its various headers
> > and runtime components.
>
> mingw.org added the timespec struct to their headers in 2014[1].
>
> >
> > The MinGW-w64 version of gcc v4.5.3 that I have works fine, so the
> required
> > test would need to be carefully tailored to pick out just old mingw.org
> > versions. Or else we could consider dropping support for them and say
> only
> > the MinGW-w64 versions are now supported, especially since MinGW/gcc
> v5.3.0
> > and v6.3.0 (the latest one that I have) both have a different problem
> > occurring earlier in the build regarding mkstemp being redefined.
> >
> > Does anyone know how to identify these problematic mingw.org compilers,
> or
> > have any views on dropping support for them?
>
> IMO supporting old mingw.org versions is a waste of time.
>
> mingw.org was almost completely replaced by mingw-w64 more than 10 years
> ago. Almost no one is using it these days.
>
> Also, upgrading a compiler is a very easy task on Windows, much easier
> than on the other platforms because it isn't integrated with the OS. I
> suppose that's the reason why mingw.org doesn't even provide downloads
> for non-latest versions of their environment.
>
> Nevertheless, if the build is broken on the *latest* version of
> mingw.org, I think we should fix it.
>
>
Thanks. I think I agree. It would be nice if older versions worked too, but
I struggle to justify any time working on it if it doesn't just work unless
anyone comes up with some reason why they have to use mingw.org and can't
use the latest one.
I am trying out 9.2.0, and will probably just end up updating readmes etc
as appropriate if that is working.
Thread Previous