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: Mon, 18 Oct 2021 10:43:54 +0200 [thread overview]
Message-ID: <87mtn6bu45.fsf@gnu.org> (raw)
In-Reply-To: <YWvOzaqr3beHD1kZ@3900XT> (Efraim Flashner's message of "Sun, 17 Oct 2021 10:20:45 +0300")
Hello!
Efraim Flashner <efraim@flashner.co.il> skribis:
> On Wed, Oct 13, 2021 at 11:00:16AM +0200, Ludovic Courtès wrote:
[...]
>> Yes, I’d rather mark i586-gnu as supported in m4/guix.m4 (it should have
>> been the case long ago) and keep the error and ‘--with-courage’ flag.
>>
>> WDYT?
>
> I'm OK with changing i586-gnu to supported in m4/guix.m4. However, part
> of the plan was to make it so that we didn't have to have the
> --with-courage flag when building for mips64el, and so we could remove
> powerpc-linux so it would also say that it is unsupported but we
> wouldn't need people to make special versions of the guix package so
> they can try to build it. I can make it bigger and flashier, so it looks
> more like
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?
Ludo’.
next prev parent reply other threads:[~2021-10-18 8:47 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 [this message]
2021-10-18 12:15 ` Efraim Flashner
2021-10-19 10:15 ` Ludovic Courtès
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=87mtn6bu45.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).