bug#53426: closed (mingw-w64-{x86_64,i686}-winpthreads broken after absorption of binutils-next )

[GNU bug Tracking System]

Your message dated Mon, 11 Jul 2022 17:52:38 -0400
with message-id <87bktvb9ll.fsf_-_@gmail.com>
and subject line Re: bug#53426: mingw-w64-{x86_64,i686}-winpthreads broken 
after absorption of binutils-next 
has caused the debbugs.gnu.org bug report #53426,
regarding mingw-w64-{x86_64,i686}-winpthreads broken after absorption of 
binutils-next 
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
53426: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=53426
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

--- Begin Message --- Subject: mingw-w64-{x86_64,i686}-winpthreads broken after absorption of binutils-next Date: Fri, 21 Jan 2022 16:30:05 -0500

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

--- End Message ---

> --- Begin Message ---
>
>
>
> 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
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux)
>
>
>
>
> Hi Michael,
>
> Michael Ford <fanquake@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
>
>
> --- End Message ---