[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#930715: marked as done (unblock: gcc-mingw-w64/21.3~deb10u1)

Your message dated Sat, 22 Jun 2019 21:33:56 +0200
with message-id <58aee4f3-3b48-afc9-bbde-9a2c2714a0a6@debian.org>
and subject line Re: Bug#930715: release.debian.org: gcc-mingw-w64 Buster upload
has caused the Debian Bug report #930715,
regarding unblock: gcc-mingw-w64/21.3~deb10u1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
930715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930715
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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 <skitt@debian.org>  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)

--- End Message ---
--- Begin Message --- 
Hi Stephen,

On 22-06-2019 12:35, Stephen Kitt wrote:
>> OK. Please go ahead with the 21.3~deb10u1 upload and set the distribution to
>> 'buster' (not 'testing' or 'testing-proposed-updates') and remove the
>> moreinfo tag from this bug once the upload has been accepted and built
>> everywhere.
> 
> It’s now built everywhere:
> https://buildd.debian.org/status/package.php?p=gcc-mingw-w64&suite=buster

Unblocked, thanks.

Paul

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: