From: Efraim Flashner <efraim@flashner.co.il>
To: Leo Famulari <leo@famulari.name>
Cc: Vagrant Cascadian <vagrant@debian.org>,
Grant Wilson II <grantm.wilsonii@gmail.com>,
help-guix@gnu.org
Subject: Re: Pinebook pro build
Date: Tue, 20 Apr 2021 10:26:20 +0300 [thread overview]
Message-ID: <YH6CHCi6kr6d0UgM@3900XT> (raw)
In-Reply-To: <YH4fRmWwahSsrPXG@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 1224 bytes --]
On Mon, Apr 19, 2021 at 08:24:38PM -0400, Leo Famulari wrote:
> On Mon, Apr 19, 2021 at 03:55:05PM -0700, Vagrant Cascadian wrote:
> > So... I'm not very familiar with how --target=ARCH cross-building works
> > in guix, but that somehow appears to trigger the issue...
>
> Thanks for your analysis. I wonder if anyone else can help us further...
> More pings!
I agree with vagrant that building u-boot-* is supposed to automagically
create a working binary for whichever system it is meant for. Also I see
that there's a pinebook-pro.scm in gnu/system/images, and I was able to
build it with `guix system build --image-type=pinebook-pro-raw
gnu/system/images/pinebook-pro.scm --target=aarch64-linux-gnu`
In the past when I've built images for my pine64 I generally build a
minimal image using --target=aarch64-linux and then reconfigure on the
board with the full config. Except when test building I've never really
tried to build it piecemeal; Guix is setup to take care of all of that.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-04-20 7:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-18 20:06 Pinebook pro build Grant Wilson II
2021-04-18 23:03 ` Leo Famulari
2021-04-18 23:27 ` Grant Wilson II
2021-04-19 4:03 ` Leo Famulari
2021-04-19 22:55 ` Vagrant Cascadian
2021-04-20 0:24 ` Leo Famulari
2021-04-20 7:26 ` Efraim Flashner [this message]
2021-04-24 8:44 ` Vincent Legoll
2021-04-20 1:10 ` Vagrant Cascadian
2021-04-20 2:02 ` Leo Famulari
2021-04-20 3:40 ` Brian Woodcox
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=YH6CHCi6kr6d0UgM@3900XT \
--to=efraim@flashner.co.il \
--cc=grantm.wilsonii@gmail.com \
--cc=help-guix@gnu.org \
--cc=leo@famulari.name \
--cc=vagrant@debian.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.
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).