From: "Ludovic Courtès" <ludo@gnu.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: branch core-updates updated: gnu: coreutils-boot0: Fix building on arm architectures.
Date: Thu, 15 Dec 2022 15:56:24 +0100 [thread overview]
Message-ID: <87a63oogvb.fsf@gnu.org> (raw)
In-Reply-To: <E7C03CE1-3934-453E-B89E-98FF6A488675@flashner.co.il> (Efraim Flashner's message of "Mon, 12 Dec 2022 14:03:48 +0000")
Hi,
Efraim Flashner <efraim@flashner.co.il> skribis:
> On December 12, 2022 1:47:29 PM UTC, "Ludovic Courtès" <ludo@gnu.org> wrote:
[...]
>>> + ,@(if (target-arm?)
>>> + ;; Some binaries fail to build.
>>> + `(#:configure-flags '(,(string-append
>>> + "--enable-no-install-program="
>>> + ;; the defaults
>>> + "arch,coreutils,hostname"
>>> + ;; fails on aarch64
>>> + ",timeout,sort")))
>>
>>Isn’t there a risk that things will break down the road if ‘sort’,
>>‘hostname’, etc. are missing? How hard would it be to address the build
>>failure instead?
>>
>>Thanks,
>>Ludo’.
>
> I built all the way out to hello without any problems. Also %final-inputs has coreutils-final, so it really shouldn't be noticable.
That’s odd though. Isn’t there some upstream patch we could take?
Surely ‘sort’ has no reason to contain arch-specific code?
If there’s no such patch, we can go with the patch above, but then there
should be a comment linking to bug reports and reassuring the reader
that yes, some packages do build even without these commands. :-)
(There’s no “coreutils” command BTW, unless enabling the
everything-in-one-binary trick, no?)
Thanks,
Ludo’.
next prev parent reply other threads:[~2022-12-15 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <167079131409.22455.5790377740841482505@vcs2.savannah.gnu.org>
2022-12-12 13:47 ` branch core-updates updated: gnu: coreutils-boot0: Fix building on arm architectures Ludovic Courtès
2022-12-12 14:03 ` Efraim Flashner
2022-12-15 14:56 ` Ludovic Courtès [this message]
2023-02-12 19:10 ` Efraim Flashner
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=87a63oogvb.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=efraim@flashner.co.il \
--cc=guix-devel@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 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).