From: Maxime Devos <maximedevos@telenet.be>
To: Thiago Jung Bauermann <bauermann@kolabnow.com>, 49565@debbugs.gnu.org
Subject: [bug#49565] [PATCH core-updates] gnu: bootstrap: Use %current-target-system to decide bootstrap path
Date: Fri, 16 Jul 2021 10:20:20 +0200 [thread overview]
Message-ID: <27e26df84bc02d681b1ff0904bdd63dfa80313bf.camel@telenet.be> (raw)
In-Reply-To: <20210716013143.901859-1-bauermann@kolabnow.com>
[-- Attachment #1: Type: text/plain, Size: 1171 bytes --]
Hi,
> diff --git a/gnu/packages/bootstrap.scm b/gnu/packages/bootstrap.scm
> index 5a8028a4652c..b14dc63062e8 100644
> --- a/gnu/packages/bootstrap.scm
> +++ b/gnu/packages/bootstrap.scm
> @@ -927,7 +927,7 @@ exec ~a/bin/.gcc-wrapped -B~a/lib \
> (define (%bootstrap-inputs)
> ;; The initial, pre-built inputs. From now on, we can start building our
> ;; own packages.
> - (match (%current-system)
> + (match (or (%current-target-system) (%current-system))
> ((or "i686-linux" "x86_64-linux")
> `(("linux-libre-headers" ,%bootstrap-linux-libre-headers)
> ("bootstrap-mescc-tools" ,%bootstrap-mescc-tools)
This makes sense to me.
However, you may need to modify 'package-from-tarball' as well,
replacing
("tarball" ,(bootstrap-origin (source (%current-system))))))
with
("tarball" ,(bootstrap-origin (source (or (%current-target-system) (%current-system)))))))
Could you verify the architecture of the binaries in the output
of "./pre-inst-env guix build gcc-toolchain@11 --target=powerpc64le-linux-gnu",
and its references (you can use "guix gc --references /gnu/store/..." and objdump)?
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-16 9:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 0:46 [bug#49565] [PATCH] gnu: glibc-headers-mesboot: Use %build-inputs in setenv phase Thiago Jung Bauermann via Guix-patches via
2021-07-15 2:04 ` Thiago Jung Bauermann via Guix-patches via
2021-07-15 12:58 ` Maxime Devos
2021-07-15 15:03 ` Thiago Jung Bauermann via Guix-patches via
2021-07-15 16:00 ` Maxime Devos
2021-07-15 17:02 ` Thiago Jung Bauermann via Guix-patches via
2021-07-16 1:31 ` [bug#49565] [PATCH core-updates] gnu: bootstrap: Use %current-target-system to decide bootstrap path Thiago Jung Bauermann via Guix-patches via
2021-07-16 8:20 ` Maxime Devos [this message]
2021-07-16 20:01 ` Thiago Jung Bauermann via Guix-patches via
2021-07-18 16:10 ` Maxime Devos
2021-07-18 16:45 ` Thiago Jung Bauermann via Guix-patches via
2021-07-20 0:01 ` [bug#49565] [PATCH core-updates v2] " Thiago Jung Bauermann via Guix-patches via
2021-07-20 13:16 ` Thiago Jung Bauermann via Guix-patches via
2021-07-21 20:30 ` Thiago Jung Bauermann via Guix-patches via
2021-07-21 22:01 ` [bug#49565] [PATCH] gnu: glibc-headers-mesboot: Use %build-inputs in setenv phase Ludovic Courtès
2021-07-22 0:32 ` 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=27e26df84bc02d681b1ff0904bdd63dfa80313bf.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=49565@debbugs.gnu.org \
--cc=bauermann@kolabnow.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).