bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org
Subject: Re: two ill effects of maint.mk
Date: Thu, 10 Jun 2021 10:21:37 -0700	[thread overview]
Message-ID: <1ac72169-92b8-a873-d122-3331f8c13552@cs.ucla.edu> (raw)
In-Reply-To: <3602589.5xaz5SmDSz@omega>

On 6/10/21 10:12 AM, Bruno Haible wrote:
>> Perhaps we could try to get the best
>> of both worlds, by changing it to set LC_ALL to an English UTF-8 locale
>> if available, and the C locale if not.
> This still would prevent the GNU m4 test suite from producing a test failure
> for the aforementioned m4-1.4.19 regression (because the English locale
> has less variation regarding the decimal separator than the whole set
> of possible locales).

True.

How about this idea instead? Have the GNUmakefile code run the 'locale' 
command and include its output in the 'make' output. That way, the 
'make' transcript would indicate this particular detail of the test 
environment.


  parent reply	other threads:[~2021-06-10 17:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-10 15:41 two ill effects of maint.mk Bruno Haible
2021-06-10 16:09 ` Paul Eggert
2021-06-10 17:12   ` Bruno Haible
2021-06-10 17:14     ` Bruno Haible
2021-06-10 17:21     ` Paul Eggert [this message]
2021-06-10 17:34       ` Bruno Haible
2021-06-10 17:38         ` Paul Eggert
2021-06-20 22:15 ` Bruno Haible
2021-06-21  2:47   ` Paul Eggert
2021-06-21  8:52     ` Bruno Haible

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://lists.gnu.org/mailman/listinfo/bug-gnulib

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

  git send-email \
    --in-reply-to=1ac72169-92b8-a873-d122-3331f8c13552@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=bruno@clisp.org \
    --cc=bug-gnulib@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.
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).