GNU bug report logs - #53426
mingw-w64-{x86_64,i686}-winpthreads broken after absorption of binutils-next

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 53426 in the body.
You can then email your comments to 53426 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Carl Dong <contact <at> carldong.me>
To: bug-guix <at> gnu.org
Subject: mingw-w64-{x86_64,i686}-winpthreads broken after absorption of
 binutils-next 
Date: Fri, 21 Jan 2022 16:30:05 -0500

[Message part 1 (text/plain, inline)]

Hi all,

The mingw-w64-{x86_64,i686}-winpthreads have been broken since the absorption of binutils-next in ce362bc1f35102e7d79ad7e0d638d20cef304f01. My very crude debugging (adding and removing configure flags from the binutils in gnu/packages/base.scm until the packages compiled) led me to the culprit: "--enable-compressed-debug-sections=all”.

I’m wondering what the best course of action is to fix the mingw-w64-{x86_64,i686}-winpthreads packages (e.g. just remove the configure flag for mingw-w64? Add that flag only for linux? Or something else?) and would love some help.

Cheers,
Carl Dong

[Message part 2 (text/html, inline)]

Message #8 received at 53426 <at> debbugs.gnu.org (full text, mbox):

From: Maxime Devos <maximedevos <at> telenet.be>
To: Carl Dong <contact <at> carldong.me>, 53426 <at> debbugs.gnu.org
Subject: Re: bug#53426: mingw-w64-{x86_64, i686}-winpthreads broken after
 absorption of binutils-next
Date: Fri, 21 Jan 2022 23:10:57 +0100

[Message part 1 (text/plain, inline)]

Carl Dong schreef op vr 21-01-2022 om 16:30 [-0500]:
> I’m wondering what the best course of action is to fix the mingw-w64-
> {x86_64,i686}-winpthreads packages (e.g. just remove the configure
> flag for mingw-w64? Add that flag only for linux? Or something else?)
> and would love some help.

I would assume that it works for Linux, it also works for the Hurd,
so I would prefer something like

#$@(if (target-mingw?) '() '("--some-configuration..."))

above

#$@(if (target-linux?) '("--some-configuration...") '())

Greetings,
Maxime.

[signature.asc (application/pgp-signature, inline)]

Message #11 received at 53426 <at> debbugs.gnu.org (full text, mbox):

From: Carl Dong <contact <at> carldong.me>
To: Maxime Devos <maximedevos <at> telenet.be>,
 53426 <at> debbugs.gnu.org
Subject: Re: bug#53426: mingw-w64-{x86_64, i686}-winpthreads broken after
 absorption of binutils-next
Date: Tue, 1 Feb 2022 12:54:12 -0500

[Message part 1 (text/plain, inline)]

I did some more exploration, and found that not only are the mingw-w64-{x86_64, i686}-winpthreads packages broken, but any --target=x86_64-w64-mingw32 package:

$ guix build --target=x86_64-w64-mingw32 hello

I have this patch which resolves the problem by simply disabling compressed debug sections, but perhaps it’d also be worthwhile to investigate the root cause...

--8<---------------cut here---------------start------------->8---
diff --git a/gnu/packages/cross-base.scm b/gnu/packages/cross-base.scm
index 78cbf871ac..397e4d4c1c 100644
--- a/gnu/packages/cross-base.scm
+++ b/gnu/packages/cross-base.scm
@@ -101,7 +101,8 @@ (define* (cross-binutils target #:optional (binutils binutils))
                                          "ath9k-htc-firmware-binutils.patch")))
                  ((target-mingw? target)
                   (package-with-extra-patches
-                   binutils
+                   (package-with-extra-configure-variable
+                    binutils "--enable-compressed-debug-sections" "no")
                    (search-patches "binutils-mingw-w64-timestamp.patch"
                                    "binutils-mingw-w64-deterministic.patch")))
                  (else binutils))
--8<---------------cut here---------------end--------------->8---

Cheers,
Carl Dong

> On Jan 21, 2022, at 5:10 PM, Maxime Devos <maximedevos <at> telenet.be> wrote:
> 
> Carl Dong schreef op vr 21-01-2022 om 16:30 [-0500]:
>> I’m wondering what the best course of action is to fix the mingw-w64-
>> {x86_64,i686}-winpthreads packages (e.g. just remove the configure
>> flag for mingw-w64? Add that flag only for linux? Or something else?)
>> and would love some help.
> 
> I would assume that it works for Linux, it also works for the Hurd,
> so I would prefer something like
> 
> #$@(if (target-mingw?) '() '("--some-configuration..."))
> 
> above
> 
> #$@(if (target-linux?) '("--some-configuration...") '())
> 
> Greetings,
> Maxime.
> 

[signature.asc (application/pgp-signature, attachment)]

Message #14 received at 53426 <at> debbugs.gnu.org (full text, mbox):

From: Michael Ford <fanquake <at> gmail.com>
To: 53426 <at> debbugs.gnu.org
Subject: mingw-w64-{x86_64,
 i686}-winpthreads broken after absorption of binutils-next
Date: Wed, 16 Mar 2022 10:05:51 +0000

[Message part 1 (text/plain, inline)]

Hi,

I think this bug can be closed now that https://issues.guix.gnu.org/53706
has been merged?

[Message part 2 (text/html, inline)]

Message #19 received at 53426-done <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Michael Ford <fanquake <at> gmail.com>
Cc: 53426-done <at> debbugs.gnu.org
Subject: Re: bug#53426: mingw-w64-{x86_64,i686}-winpthreads broken after
 absorption of binutils-next 
Date: Mon, 11 Jul 2022 17:52:38 -0400

Hi Michael,

Michael Ford <fanquake <at> gmail.com> writes:

> Hi,
>
> I think this bug can be closed now that https://issues.guix.gnu.org/53706
> has been merged?

I think so too!  Thanks for the heads-up.

Maxim

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.