From: "Ludovic Courtès" <ludo@gnu.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: 50778@debbugs.gnu.org
Subject: [bug#50778] [PATCH] m4: Don't require courage on unsupported systems.
Date: Tue, 19 Oct 2021 12:15:17 +0200 [thread overview]
Message-ID: <87k0i99v7u.fsf@gnu.org> (raw)
In-Reply-To: <YW1leipsxkUyeWEC@3900XT> (Efraim Flashner's message of "Mon, 18 Oct 2021 15:15:54 +0300")
Howdy!
Efraim Flashner <efraim@flashner.co.il> skribis:
> On Mon, Oct 18, 2021 at 10:43:54AM +0200, Ludovic Courtès wrote:
[...]
>> Ah! So I think you’re asking that there be three levels:
>>
>> 1. Fully supported (should include i586-gnu).
>>
>> 2. “Half supported” or “in the works”, like mips64el-linux and
>> powerpc-linux: in that case, maybe just emit a warning with
>> AC_MSG_WARN?
>>
>> 3. Unsupported: error asking users to pass ‘--with-courage’.
>>
>> How does that sound?
>
> I hadn't really planned on keeping the third category, but thinking
> about it more it would make sense to keep it for architectures that we
> don't even have bootstrap binaries for. Vagrant said he was able to
> build the guix package for riscv64-linux, I think without even adding my
> patches for adding the bootstrap binaries. By forcing people to pass
> --with-courage it goes past "it doesn't really work" and all the way
> into "really really unsupported"
>
> So yes, I like the idea of the three levels.
Alright. Can you send (or push) an updated patch?
Thanks!
Ludo’.
next prev parent reply other threads:[~2021-10-19 10:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 13:39 [bug#50778] [PATCH] m4: Don't require courage on unsupported systems Efraim Flashner
2021-10-13 9:00 ` Ludovic Courtès
2021-10-17 7:20 ` Efraim Flashner
2021-10-18 8:43 ` Ludovic Courtès
2021-10-18 12:15 ` Efraim Flashner
2021-10-19 10:15 ` Ludovic Courtès [this message]
2021-12-14 16:36 ` bug#50778: " 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=87k0i99v7u.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=50778@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
/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).