From: Maxime Devos <maximedevos@telenet.be>
To: "Ludovic Courtès" <ludo@gnu.org>, "Mathieu Othacehe" <othacehe@gnu.org>
Cc: 49659@debbugs.gnu.org
Subject: [bug#49659] [PATCH core-updates] gnu: guile: Fix failing tests on i686-linux.
Date: Fri, 23 Jul 2021 11:27:30 +0200 [thread overview]
Message-ID: <bafd3cf0cd2053d2acf37d402abb226d63ee4a8b.camel@telenet.be> (raw)
In-Reply-To: <8735s5cs9q.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 747 bytes --]
Ludovic Courtès schreef op vr 23-07-2021 om 11:07 [+0200]:
> Hi,
>
> Mathieu Othacehe <othacehe@gnu.org> skribis:
>
> > > I tweaked the commit log and pushed as
> > > fccc0275091af10a46471c68df525d19f446af9e.
> > >
> > > Looks like we should be able to move forward with this branch now,
> > > thank you!
> >
> > Thanks for taking care of that Maxime & Ludo :). Should we create a
> > core-updates-frozen branch that Cuirass would build for the "all"
> > subset? I can take care of that if so.
>
> There are “two last things” to check IMO: [...]
For --target=x86_64-w64-mingw32, the patch
<https://issues.guix.gnu.org/49694> is required,
to fix a build failure of x86_64-w64-mingw32-binutils.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2021-07-23 9:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 11:27 [bug#49659] [PATCH core-updates] gnu: guile: Fix failing tests on i686-linux Maxime Devos
2021-07-20 13:55 ` Ludovic Courtès
2021-07-20 16:55 ` Maxime Devos
2021-07-20 20:51 ` Ludovic Courtès
2021-07-20 18:22 ` Efraim Flashner
2021-07-20 21:34 ` [bug#49659] [PATCH v2\ core-updates v2] " Maxime Devos
2021-07-21 13:49 ` bug#49659: [PATCH core-updates] " Ludovic Courtès
2021-07-21 14:50 ` [bug#49659] " Mathieu Othacehe
2021-07-23 9:07 ` Ludovic Courtès
2021-07-23 9:27 ` Maxime Devos [this message]
2021-07-25 23:52 ` Thiago Jung Bauermann 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
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=bafd3cf0cd2053d2acf37d402abb226d63ee4a8b.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=49659@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=othacehe@gnu.org \
/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).