From: "Ludovic Courtès" <ludo@gnu.org>
To: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Cc: 58366-done@debbugs.gnu.org
Subject: bug#58366: Guix build guix fails on i686
Date: Sun, 09 Oct 2022 21:20:04 +0200 [thread overview]
Message-ID: <874jwc6byz.fsf_-_@gnu.org> (raw)
In-Reply-To: <20221008202757.4ca6b2e6@primary_laptop> (Denis Carikli's message of "Sat, 8 Oct 2022 20:27:57 +0200")
Hi,
Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> skribis:
> After a guix pull it now builds fine again. I've tested it with guix
> build -s i686-linux on x86_64 and guix build guix on i686.
Yes, this was addressed in <https://issues.guix.gnu.org/58352>.
> So the bug can now be closed.
Done, thanks!
Ludo’.
prev parent reply other threads:[~2022-10-09 19:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 20:54 bug#58366: Guix build guix fails on i686 Denis 'GNUtoo' Carikli
2022-10-08 18:27 ` bug#58366: Guix build " Denis 'GNUtoo' Carikli
2022-10-09 19:20 ` Ludovic Courtès [this message]
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=874jwc6byz.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=58366-done@debbugs.gnu.org \
--cc=GNUtoo@cyberdimension.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).