From: Vagrant Cascadian <vagrant@debian.org>
To: Grant Wilson II <grantm.wilsonii@gmail.com>,
Leo Famulari <leo@famulari.name>
Cc: help-guix@gnu.org
Subject: Re: Pinebook pro build
Date: Mon, 19 Apr 2021 15:55:05 -0700 [thread overview]
Message-ID: <875z0hq3zq.fsf@yucca> (raw)
In-Reply-To: <CANK3aa1bbuZfUs0zsr9Aypr7rTvxJctOy9X2BkS_tLnzucZ-4w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2073 bytes --]
On 2021-04-18, Grant Wilson II wrote:
> If I interpret the source correctly, "firmware" is being provided to the
> package as a native input.
> When I attempt the build without cross compiling then it does succeed...
> `guix build -e "(@ (gnu packages bootloaders) u-boot-pinebook-pro-rk3399)"`
>
> However that does defeat the purpose.
>
> Why would the "firmware" native input not be available when targeting
> aarch64-linux-gnu?
That seems to be the problem, yes...
It is failing in the set-environment phase...
(define-public u-boot-pinebook-pro-rk3399
...
(add-after 'unpack 'set-environment
(lambda* (#:key inputs #:allow-other-keys)
(setenv "BL31" (string-append (assoc-ref inputs "firmware")
"/bl31.elf"))
#t))
Works:
guix build arm-trusted-firmware-rk3399
guix build u-boot-pinebook-pro-rk3399
guix build --target=aarch64-linux arm-trusted-firmware-rk3399
Fails:
guix build --target=aarch64-linux u-boot-pinebook-pro-rk3399
So the firmware (arm-trusted-firmware-rk3399) exists, but for some
reason isn't available while cross-building. It appears to be present in
the both the cross-built and "regular" firmware package:
$ guix build --target=aarch64-linux arm-trusted-firmware-rk3399
/gnu/store/v3nkj3hiihllwp9kn65ih7xi2bjbp58v-arm-trusted-firmware-rk3399-2.4
$ guix build arm-trusted-firmware-rk3399
/gnu/store/jpm4hfqh08s9ns3pd5h3r798z7pdbp0m-arm-trusted-firmware-rk3399-2.4
$ ls /gnu/store/v3nkj3hiihllwp9kn65ih7xi2bjbp58v-arm-trusted-firmware-rk3399-2.4 /gnu/store/jpm4hfqh08s9ns3pd5h3r798z7pdbp0m-arm-trusted-firmware-rk3399-2.4
/gnu/store/jpm4hfqh08s9ns3pd5h3r798z7pdbp0m-arm-trusted-firmware-rk3399-2.4:
bl31.elf rk3399m0.bin rk3399m0.elf rk3399m0pmu.bin rk3399m0pmu.elf share
/gnu/store/v3nkj3hiihllwp9kn65ih7xi2bjbp58v-arm-trusted-firmware-rk3399-2.4:
bl31.elf rk3399m0.bin rk3399m0.elf rk3399m0pmu.bin rk3399m0pmu.elf share
So... I'm not very familiar with how --target=ARCH cross-building works
in guix, but that somehow appears to trigger the issue...
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2021-04-19 22:56 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 [this message]
2021-04-20 0:24 ` Leo Famulari
2021-04-20 7:26 ` Efraim Flashner
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=875z0hq3zq.fsf@yucca \
--to=vagrant@debian.org \
--cc=grantm.wilsonii@gmail.com \
--cc=help-guix@gnu.org \
--cc=leo@famulari.name \
/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).