From: "Ludovic Courtès" <ludo@gnu.org>
To: Vivien Kraus <vivien@planete-kraus.eu>
Cc: 62916@debbugs.gnu.org
Subject: [bug#62916] [PATCH core-updates 0/2] Try to fix p11-kit compilation to mingw
Date: Tue, 25 Apr 2023 18:11:36 +0200 [thread overview]
Message-ID: <87ildkym9z.fsf_-_@gnu.org> (raw)
In-Reply-To: <234715f3c0fe265574fd9708abe0e057ee3c1641.1681770007.git.vivien@planete-kraus.eu> (Vivien Kraus's message of "Tue, 18 Apr 2023 00:09:55 +0200")
Hi,
Vivien Kraus <vivien@planete-kraus.eu> skribis:
> * gnu/packages/gcc.scm (gcc-configure-flags-for-triplet): Disable gcov when
> targetting mingw.
Pushed this one as 74038cf66e3a8cdcd9d97a81d9176c3cdefdaaf7.
The p11-kit story isn’t good, but I’m not sure how to address it. When
we find a way, we can add a feature branch to rebuild everything that
depends on it though.
Thanks!
Ludo’.
next prev parent reply other threads:[~2023-04-25 16:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 22:20 [bug#62916] [PATCH core-updates 0/2] Try to fix p11-kit compilation to mingw Vivien Kraus via Guix-patches via
2023-04-17 22:09 ` [bug#62916] [PATCH core-updates 1/2] gnu: gcc: do not build gcov Vivien Kraus via Guix-patches via
2023-04-25 16:11 ` Ludovic Courtès [this message]
2023-04-25 16:16 ` [bug#62916] [PATCH v2 0/1] Fix p11-kit build system for mingw Vivien Kraus via Guix-patches via
2023-04-25 15:50 ` [bug#62916] [PATCH v2 1/1] gnu: p11-kit: fix build on mingw Vivien Kraus via Guix-patches via
2023-04-25 21:33 ` [bug#62916] [PATCH v3 0/1] Simpler fix for p11-kit@mingw Vivien Kraus via Guix-patches via
2023-04-25 15:50 ` [bug#62916] [PATCH v3 1/1] gnu: p11-kit: fix build on mingw Vivien Kraus via Guix-patches via
2023-04-17 22:17 ` [bug#62916] [PATCH core-updates 2/2] NOT WORKING gnu: p11-kit: switch to meson-build-system Vivien Kraus via Guix-patches via
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ildkym9z.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=62916@debbugs.gnu.org \
--cc=vivien@planete-kraus.eu \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.