From: Efraim Flashner <efraim@flashner.co.il>
To: ludo@gnu.org
Cc: 31473@debbugs.gnu.org
Subject: [bug#31473] [PATCH] daemon: Allow building for armhf-linux on aarch64-linux.
Date: Thu, 17 May 2018 11:27:07 +0000 [thread overview]
Message-ID: <2FB15D41-02E7-41CA-87D5-6E3C3DF0EE2F@flashner.co.il> (raw)
In-Reply-To: <87po1u34u5.fsf@gnu.org>
On May 17, 2018 11:21:38 AM UTC, ludo@gnu.org wrote:
>Hello Efraim,
>
>Efraim Flashner <efraim@flashner.co.il> skribis:
>
>> * nix/libstore/build.cc (canBuildLocally): Allow building armhf-linux
>> builds on aarch64-linux.
>> (DerivationGoal::runChild) Throw error if attempting to build for
>> armhf-linux on an unsupported platform.
>> * doc/guix.texi (Invoking guix build): Document how to build natively
>> for armhf-linux on aarch64-linux. Add note that on some aarch64
>> machines this is unsupported.
>
>Awesome! If you’ve confirmed that it works for you, go for it.
>
>> +@quotation Note
>> +Building for an @code{armhf-linux} system is unconditionally enabled
>on
>> +@code{aarch64-linux} machines, although certain aarch64 chipsets do
>not
>> +allow for this functionality.
>> +@end quotation
>
>Perhaps we should list a couple of chipsets known to support this?
>Would it make sense?
>
>Thank you!
>
>Ludo’.
The ThunderX for sure, and I've heard the expressobin might not but I'm not sure. I didn't want to have an incomplete list. The closest I've heard for a way to check is to compile and run a program called all-arch, but it's harder on a source distro.
I could change it to "... not allow this functionality, notably the ThunderX."
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2018-05-17 11:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 12:10 [bug#31473] [PATCH] daemon: Allow building for armhf-linux on aarch64-linux Efraim Flashner
2018-05-17 11:21 ` Ludovic Courtès
2018-05-17 11:27 ` Efraim Flashner [this message]
2018-05-17 14:08 ` Ludovic Courtès
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=2FB15D41-02E7-41CA-87D5-6E3C3DF0EE2F@flashner.co.il \
--to=efraim@flashner.co.il \
--cc=31473@debbugs.gnu.org \
--cc=ludo@gnu.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.
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.