unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 36322@debbugs.gnu.org
Subject: [bug#36322] [PATCH 0/4] [core-updates] Fix cross-compiling bootstrap tarballs
Date: Thu, 07 Apr 2022 15:18:34 +0200	[thread overview]
Message-ID: <86lewh1179.fsf@gmail.com> (raw)
In-Reply-To: <20190621122411.17847-1-mbakke@fastmail.com> (Marius Bakke's message of "Fri, 21 Jun 2019 14:24:11 +0200")

Hi Marius,

What is the status of this patch series [1]?

1: <http://issues.guix.gnu.org/issue/36322>


On Fri, 21 Jun 2019 at 14:24, Marius Bakke <mbakke@fastmail.com> wrote:
> With these patches, we can again cross-compile the bootstrap tarballs on
> core-updates.
>
> As of commit bd0dc2df04a1550f41d3d5c7cc2c26ad12468b36, here are my
> results for armhf and Hurd(!):
>
> $ ./pre-inst-env guix build --target=arm-linux-gnueabihf bootstrap-tarballs
> /gnu/store/q245c0s6cc55ziamfxpv43lwbnxaw0n6-bootstrap-tarballs-0
> $ guix hash -rx $(!!)
> 01lksw8qw973bc2lllz97pxm67x84rz8crbdiqwnlbyjq0j3mvaq
>
> $ ./pre-inst-env guix build  --target=i586-pc-gnu bootstrap-tarballs
> /gnu/store/4i3zxmzcrpg2h8inwgfd24sdsgan9jw7-bootstrap-tarballs-0
> $ guix hash -rx $(!!)
> 17yjlqvwlv8v28qm5v888kshx30djylml9fgpwkcqvx3idzw7i1v
>
> Now, I haven't actually tried bootstrapping a system from these yet.
> Do we have automated tests for that?

I think the next action is waiting an answer for this question,
eventually. :-)

> Marius Bakke (4):
>   gnu: make-bootstrap: Remove obsolete header file.
>   gnu: make-bootstrap: Restore cross-compilation workarounds.
>   gnu: make-bootstrap: Adjust for GCC 7.
>   gnu: bootstrap-tarballs: Don't include the native mes when
>     cross-compiling.
>
>  gnu/packages/make-bootstrap.scm | 64 ++++++++++++++++++++++++---------
>  guix/build/make-bootstrap.scm   |  1 -
>  2 files changed, 47 insertions(+), 18 deletions(-)


What would the next step?  More tests?  Merge into core-updates?  Other?


Cheers,
simon




  parent reply	other threads:[~2022-04-07 13:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-21 12:24 [bug#36322] [PATCH 0/4] [core-updates] Fix cross-compiling bootstrap tarballs Marius Bakke
2019-06-21 12:26 ` [bug#36322] [PATCH 1/4] gnu: make-bootstrap: Remove obsolete header file Marius Bakke
2019-06-21 12:26   ` [bug#36322] [PATCH 2/4] gnu: make-bootstrap: Restore cross-compilation workarounds Marius Bakke
2019-06-21 12:26   ` [bug#36322] [PATCH 3/4] gnu: make-bootstrap: Adjust for GCC 7 Marius Bakke
2019-06-21 12:26   ` [bug#36322] [PATCH 4/4] gnu: bootstrap-tarballs: Don't include the native mes when cross-compiling Marius Bakke
2022-04-07 13:18 ` zimoun [this message]
2022-04-07 21:15   ` bug#36322: [PATCH 0/4] [core-updates] Fix cross-compiling bootstrap tarballs Marius Bakke

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=86lewh1179.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=36322@debbugs.gnu.org \
    --cc=mbakke@fastmail.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).