[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: make check errors in autoconf 2.52

From: Paul Eggert
Subject: Re: make check errors in autoconf 2.52
Date: Thu, 3 Jan 2002 14:24:31 -0800 (PST)

> From: Akim Demaille <address@hidden>
> Date: 03 Jan 2002 14:23:11 +0100
> So, unless I am mistaken somewhere, we have to clear out all the LC
> variables.

I still don't see why we need to clear them out, given the fixes to
this area that have been installed since Autoconf 2.52.

Autoconf 2.52 uses this pattern for each of the LC* variables:

   $as_unset LC_ALL || test "${LC_ALL+set}" != set || { LC_ALL=C; export 

This pattern causes a problem for him, since it unsets LC_ALL and
therefore exposes his LC_MONETARY setting.

But since then, we've changed the pattern to look like this instead:

   (set +x; test -n "`(LC_ALL=C; export LC_ALL) 2>&1`") &&
       { $as_unset LC_ALL || test "${LC_ALL+set}" != set; } ||
         { LC_ALL=C; export LC_ALL; }

This newer Autoconf behavior should fix his problem, because it should
set LC_ALL to C on his host, and therefore all the other LC and LANG
variables should be irrelevant on his host.  His LC_MONETARY setting
shouldn't matter.

(I am tempted to change the pattern to just this:

  LC_ALL=C; export LC_ALL

as the ancient hosts that don't let you set LC_ALL to 'C' are probably
all gone by now.  But I am resisting the temptation.  :-)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]