From: Vagrant Cascadian <vagrant@debian.org>
To: Maxime Devos <maximedevos@telenet.be>, 48371@debbugs.gnu.org
Subject: [bug#48371] Add crust firmware for sunxi devices
Date: Sat, 29 May 2021 17:55:04 -0700 [thread overview]
Message-ID: <87r1hpf3br.fsf@yucca> (raw)
In-Reply-To: <334cfe187104a05a822dadd12436bc37dd1fcbb1.camel@telenet.be>
[-- Attachment #1: Type: text/plain, Size: 1202 bytes --]
On 2021-05-13, Maxime Devos wrote:
> Vagrant Cascadian schreef op di 11-05-2021 om 15:15 [-0700]:
>> + #:make-flags (list
>> + "CROSS_COMPILE=or1k-elf-"
>> + "DEBUG=1"
>> + "HOSTCC=gcc"
>> + "HOSTAR=ar"
>> + "HOST_COMPILE=aarch64-linux-gnu-"
>> + "LEX=flex")
>
> IIUC, CROSS_COMPILE is the system Crust will run on, and HOST_COMPILE
> is the system where Crust is compiled. So shouldn't HOST_COMPILE be
>
> (string-append (nix-system->gnu-triplet (%current-system)) "-")
>
> such that Crust can be cross-compiled from non-aarch64 or non-linux systems?
Good point!
Although I couldn't get it to work, always ending in:
ERROR: In procedure %resolve-variable:
Unbound variable: nix-system->gnu-triplet
firmware.scm includes:
#:use-module (guix utils)
Which is where I think that is defined, but...
Setting HOST_COMPILE to an empty value appears to work and it just uses
the defined HOSTCC and HOSTAR, so this is probably better anyways!
There's a new crust version available, so I'll give that a quick test
before sending updated patches.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2021-05-30 0:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 22:15 [bug#48371] Add crust firmware for sunxi devices Vagrant Cascadian
2021-05-13 13:00 ` Maxime Devos
2021-05-30 0:55 ` Vagrant Cascadian [this message]
2021-05-30 1:30 ` Vagrant Cascadian
2023-07-07 20:07 ` bug#48371: " Maxim Cournoyer
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=87r1hpf3br.fsf@yucca \
--to=vagrant@debian.org \
--cc=48371@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
/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).