Re: [lmi] PATCH: Building lmi with gcc 10 and C++20

[Greg Chicares]

On 2020-05-11 00:37, Vadim Zeitlin wrote:
> On Sun, 10 May 2020 23:38:03 +0000 Greg Chicares <gchicares@sbcglobal.net> 
> wrote:
> 
> GC> On 2020-05-10 22:12, Vadim Zeitlin wrote:
> GC> > 
> GC> >  I couldn't help myself and decided to test compilation of lmi in C++20
> GC> > mode as soon as g++ 10.1, implementing support for C++20, became 
> available
> GC> > in Debian.
> GC> 
> GC> This must be pc-linux-gnu or whatever it's called, as opposed to msw,
> 
>  Yes, it's the x86_64-pc-linux-gnu version (in 32 bits it would be
> i686-pc-linux-gnu).
> 
> GC> because even debian unstable still has only
> GC>   mingw-w64 (7.0.0-4), which depends upon
> GC>   g++-mingw-w64 (9.3.0-8+22)
> 
>  I don't know when did it appear there, but there is g++-mingw-w64-i686 ~10
> in experimental. We obviously shouldn't use it for anything serious, but
> it's a good sign as it means that it might migrate to unstable relatively
> soon and then I would at least be able to test it conveniently (I do use
> some packages from experimental from time to time, but I prefer not to do
> it unless it's really needed -- or I'm really dying from curiosity, and in
> this case I think I'll be able to restrain myself for a bit longer).

Apparently gcc-10 has moved to 'unstable' just minutes ago, which means that
building lmi in a freshly-created 'unstable' chroot doesn't quite succeed:
at the least, I need to change 'workhorse.make' to recognize gcc-10.0 .
I suppose I'll find that you've already adapted lmi's own code to gcc-10,
but that we'll need to upgrade wx.

I'm surprised to see that 'stable' now has gcc-8.3:

  https://packages.debian.org/buster/g++-mingw-w64
| Package: g++-mingw-w64 (8.3.0-6+21.3~deb10u1)

because I thought 'stable' only received security upgrades, and IIRC it
still had gcc-7 when 'buster' became 'stable'. There's an update notice
today:

  https://tracker.debian.org/news/1141612/mingw-w64-700-4-migrated-to-testing/

but it doesn't say anything about 'stable'.

Anyway, we're still using gcc-8.3 in production, so perhaps we should
just create a 'stable' chroot for now, because testing a wx upgrade
for this month's release would be "a bridge too far".