From: Chris Marusich <cmmarusich@gmail.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: othacehe@gnu.org, bug#24841 <24841@debbugs.gnu.org>
Subject: bug#24841: Cross-building bootstrap binaries fail in current master
Date: Mon, 05 Jul 2021 20:36:38 -0700 [thread overview]
Message-ID: <875yxow1tl.fsf@gmail.com> (raw)
In-Reply-To: <85lf6p85kz.fsf_-_@gmail.com> (zimoun's message of "Fri, 02 Jul 2021 10:47:56 +0200")
[-- Attachment #1: Type: text/plain, Size: 695 bytes --]
zimoun <zimon.toutoune@gmail.com> writes:
> What is the status of this bug#24841 report [1]?
>
> 1: <http://issues.guix.gnu.org/issue/24841>
I agree we can close this old bug report. As you mentioned, it is now
possible to build bootstrap binaries for various architectures.
If someone needs to build bootstrap binaries for a specific
architecture, and they are unable to do so, then they should open a new
bug report for that problem specifically. Currently, I have no need to
do this, since I am not bootstrapping any new architectures at the
moment, or updating any bootstrap binaries.
If nobody else comments, I'll close this bug report in a week or two.
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
next prev parent reply other threads:[~2021-07-06 3:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7tmvhzxubh.fsf@gmail.com>
[not found] ` <87eg3bb04s.fsf@gnu.org>
[not found] ` <7tvawl7v6e.fsf@gmail.com>
2016-10-31 21:59 ` Cross-building bootstrap binaries fail in current master Ludovic Courtès
2017-11-28 4:31 ` bug#24841: " Chris Marusich
2018-02-22 9:47 ` bug#24841: Status: " Chris Marusich
2018-02-27 23:36 ` Ludovic Courtès
2021-07-02 8:47 ` bug#24841: " zimoun
2021-07-06 3:36 ` Chris Marusich [this message]
2021-07-06 8:31 ` zimoun
2021-07-30 6:43 ` bug#24841: close 24841 Chris Marusich
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=875yxow1tl.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=24841@debbugs.gnu.org \
--cc=othacehe@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).