all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 50778@debbugs.gnu.org
Subject: [bug#50778] [PATCH] m4: Don't require courage on unsupported systems.
Date: Sun, 17 Oct 2021 10:20:45 +0300	[thread overview]
Message-ID: <YWvOzaqr3beHD1kZ@3900XT> (raw)
In-Reply-To: <87h7dls3j3.fsf@gnu.org>

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

On Wed, Oct 13, 2021 at 11:00:16AM +0200, Ludovic Courtès wrote:
> Efraim Flashner <efraim@flashner.co.il> skribis:
> 
> > * m4/guix.m4 (GUIX_ASSERT_SUPPORTED_SYSTEM): Don't error if building on
> > an unsupported system.
> > * doc/guix.texi (GNU Distribution): Relabel mips64el-linux as
> > unsupported.
> > ---
> >
> > As we discussed previously with the powerpc-linux patches, I've gotten
> > around to changing the m4 error to a warning. Also, I didn't change
> > i586-gnu to say unsupported next to it in GNU Distribution in the
> > manual, although I suppose the other option would be to add i586-gnu to
> > supported in m4/guix.m4.
> 
> 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

****************************************

WARNING: YOU ARE ATTEMPTING TO BUILD GUIX ON AN UNSUPPORTED PLATFORM!
PROCEED AT YOUR OWN RISK!!! YOU HAVE BEEN WARNED! HERE BE DRAGONS!!!!

****************************************

> > -@item mips64el-linux (deprecated)
> > +@item mips64el-linux (unsupported)
> 
> Good idea.  :-)
> 
> Thanks!
> 
> Ludo’.
> 
> 
> 

-- 
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 --]

  reply	other threads:[~2021-10-17  7:22 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 [this message]
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         ` 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

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

  git send-email \
    --in-reply-to=YWvOzaqr3beHD1kZ@3900XT \
    --to=efraim@flashner.co.il \
    --cc=50778@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 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.