all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Mon, 12 Dec 2022 14:47:29 +0100	[thread overview]
Message-ID: <87bko820pa.fsf@gnu.org> (raw)
In-Reply-To: <167079131409.22455.5790377740841482505@vcs2.savannah.gnu.org> (guix-commits@gnu.org's message of "Sun, 11 Dec 2022 15:41:54 -0500")

Hello,

guix-commits@gnu.org skribis:

> commit 9782c4529249c8300501202112c095a6589845d3
> Author: Efraim Flashner <efraim@flashner.co.il>
> AuthorDate: Sun Dec 11 22:35:06 2022 +0200
> 
>     gnu: coreutils-boot0: Fix building on arm architectures.
>     
>     * gnu/packages/commencement.scm (coreutils-boot0)[arguments]: When
>     building for arm architectures skip building some programs.

[…]

> +       ,@(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’.


       reply	other threads:[~2022-12-12 13:48 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 ` Ludovic Courtès [this message]
2022-12-12 14:03   ` branch core-updates updated: gnu: coreutils-boot0: Fix building on arm architectures Efraim Flashner
2022-12-15 14:56     ` Ludovic Courtès
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

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

  git send-email \
    --in-reply-to=87bko820pa.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 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.