unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Carl Dong <contact@carldong.me>, 53426@debbugs.gnu.org
Subject: bug#53426: mingw-w64-{x86_64, i686}-winpthreads broken after absorption of binutils-next
Date: Fri, 21 Jan 2022 23:10:57 +0100	[thread overview]
Message-ID: <5ec60e040300065c155dbf9e2653e6c44da6ef2e.camel@telenet.be> (raw)
In-Reply-To: <CE729A95-624F-4CC3-A757-2045B4B3E2F3@carldong.me>

[-- Attachment #1: Type: text/plain, Size: 562 bytes --]

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.


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2022-01-21 22:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-21 21:30 bug#53426: mingw-w64-{x86_64, i686}-winpthreads broken after absorption of binutils-next Carl Dong
2022-01-21 22:10 ` Maxime Devos [this message]
2022-02-01 17:54   ` Carl Dong
2022-03-16 10:05 ` Michael Ford
2022-07-11 21:52   ` Maxim Cournoyer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5ec60e040300065c155dbf9e2653e6c44da6ef2e.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=53426@debbugs.gnu.org \
    --cc=contact@carldong.me \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).