all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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 18:10:01 -0700	[thread overview]
Message-ID: <8735vlpxqu.fsf@yucca> (raw)
In-Reply-To: <875z0hq3zq.fsf@yucca>

[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]

On 2021-04-19, Vagrant Cascadian wrote:
> 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)"`
...
> 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... I'm not very familiar with how --target=ARCH cross-building works
> in guix, but that somehow appears to trigger the issue...

I should also mention that arm-trusted-firmware and u-boot packages have
support for cross-building when not using --target=ARCH. e.g. Building
these packages on x86_64 builds working binaries for the aarch64 boot
firmware.

Maybe somehow the internal cross-building support is interfering with
how the --target=ARCH style cross-building works?

live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  parent reply	other threads:[~2021-04-20  1:11 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
2021-04-24  8:44           ` Vincent Legoll
2021-04-20  1:10       ` Vagrant Cascadian [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8735vlpxqu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.