From: "Jakub Kądziołka" <kuba@kadziolka.net>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: 42681-done@debbugs.gnu.org
Subject: bug#42681: [PATCH core-updates] gnu: bootstrap-gcc: Don't use CPATH search paths.
Date: Tue, 4 Aug 2020 14:34:35 +0200 [thread overview]
Message-ID: <20200804123435.pk3uqpasdctvjdo5@gravity> (raw)
In-Reply-To: <20200804060006.GM1134@E5400>
[-- Attachment #1: Type: text/plain, Size: 1032 bytes --]
On Tue, Aug 04, 2020 at 09:00:06AM +0300, Efraim Flashner wrote:
> On Mon, Aug 03, 2020 at 01:03:52PM +0200, Jakub Kądziołka wrote:
> > On Mon, Aug 03, 2020 at 09:40:26AM +0300, Efraim Flashner wrote:
> > > On Sun, Aug 02, 2020 at 10:34:21PM +0200, Jakub Kądziołka wrote:
> > > I'm building out to hello on my aarch64 board now, starting from
> > > make-boot0 apparently. Guile is only listed once so hopefully it won't
> > > take too long.
> >
> > Thanks!
> >
> > > I assume this doesn't break anything on x86_64?
> >
> > I don't have hello built on current core-updates (it also wants to start
> > from make-boot0), but I have confirmed that guix build --no-grafts -d
> > hello returns the same derivation path before and after the commit.
> > %bootstrap-gcc is not present at all in the package graph on x86.
> >
> > Regards,
> > Jakub Kądziołka
>
> I was able to successfully build all the way out to hello on
> aarch64-linux.
This is great news! Patch pushed.
Regards,
Jakub Kądziołka
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-08-04 12:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-02 20:34 [bug#42681] [PATCH core-updates] gnu: bootstrap-gcc: Don't use CPATH search paths Jakub Kądziołka
2020-08-03 6:40 ` Efraim Flashner
2020-08-03 11:03 ` Jakub Kądziołka
2020-08-04 6:00 ` Efraim Flashner
2020-08-04 12:34 ` Jakub Kądziołka [this message]
2020-08-05 8:56 ` Efraim Flashner
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=20200804123435.pk3uqpasdctvjdo5@gravity \
--to=kuba@kadziolka.net \
--cc=42681-done@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
/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).