Package: release.debian.org Severity: normal Hi,
I uploaded an updated gcc-mingw-w64 package to unstable, 21.3, with a fix for #928214. I’ve since been informed (by Paul Gevers, re Mednafen) that gcc-8 8.3.0-7 won’t be migrating, which means gcc-mingw-w64 21.3 won’t either. Could I upload the package as 21.3~deb10u1 to testing-pu? The diff between 21.2 and 21.3 is as follows: diff --git a/debian/changelog b/debian/changelog index a2de56d..dcef4a3 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +gcc-mingw-w64 (21.3) unstable; urgency=medium + + * Configure LTO support correctly; thanks Alexey Izbyshev! + Closes: #928214. + + -- Stephen Kitt <[email protected]> Tue, 18 Jun 2019 08:59:34 +0200 + gcc-mingw-w64 (21.2) unstable; urgency=medium * Apply upstream dllimport fix for static data members. diff --git a/debian/rules b/debian/rules index 0b55196..e9e4416 100755 --- a/debian/rules +++ b/debian/rules @@ -202,8 +202,7 @@ CONFFLAGS += \ --enable-languages=$(languages) # LTO CONFFLAGS += \ - --enable-lto \ - --with-plugin-ld + --enable-lto # Thread-model-dependent CONFFLAGS += \ --enable-threads=$$threads \ The package is currently building in unstable, with a killed job on i386 for some reason; it also builds fine in testing. I don’t yet have a fix for #923698, the other RC bug against gcc-mingw-w64 — that will have to wait for a point release (assuming the fix is approvable). Regards, Stephen -- System Information: Debian Release: 9.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (100, 'unstable-debug'), (100, 'testing-debug'), (100, 'unstable'), (100, 'testing'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-9-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
