unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: "Ludovic Courtès" <ludo@gnu.org>, 50778-done@debbugs.gnu.org
Subject: bug#50778: [PATCH] m4: Don't require courage on unsupported systems.
Date: Tue, 14 Dec 2021 18:36:48 +0200	[thread overview]
Message-ID: <YbjIICzphn2XTdZd@3900XT> (raw)
In-Reply-To: <YW1leipsxkUyeWEC@3900XT>

[-- Attachment #1: Type: text/plain, Size: 2396 bytes --]

Finally took care of this today.

On Mon, Oct 18, 2021 at 03:15:54PM +0300, Efraim Flashner wrote:
> On Mon, Oct 18, 2021 at 10:43:54AM +0200, Ludovic Courtès wrote:
> > 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?
> 
> 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.
> 
> -- 
> Efraim Flashner   <efraim@flashner.co.il>   רנשלפ םירפא
> GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
> Confidentiality cannot be guaranteed on emails sent or received unencrypted



-- 
Efraim Flashner   <efraim@flashner.co.il>   רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2021-12-14 16:38 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
2021-12-14 16:36         ` Efraim Flashner [this message]

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=YbjIICzphn2XTdZd@3900XT \
    --to=efraim@flashner.co.il \
    --cc=50778-done@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 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).