From: Andrey Borzenkov <arvidjaar@mail.ru>
To: Alex Riesen <fork0@users.sf.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.0-test5-mm1
Date: Sun, 14 Sep 2003 18:01:55 +0400 [thread overview]
Message-ID: <200309141801.55700.arvidjaar@mail.ru> (raw)
In-Reply-To: <20030914135248.GA9729@steel.home>
On Sunday 14 September 2003 17:52, Alex Riesen wrote:
> Andrey Borzenkov, Sun, Sep 14, 2003 10:46:01 +0200:
> > On Saturday 13 September 2003 13:13, Alex Riesen wrote:
> > > > really-use-english-date-in-version-string.patch
> > > > really use english date in version string
> > >
> > > - echo \#define LINUX_COMPILE_TIME \"`LANG=C date +%T`\"
> > > + echo \#define LINUX_COMPILE_TIME \"`LC_ALL=C LANG=C date +%T`\"
> > >
> > > LC_ALL overrides everything, so LANG is not needed anymore. Should be:
> > >
> > > + echo \#define LINUX_COMPILE_TIME \"`LC_ALL=C date +%T`\"
> >
> > I need to set three! variables to make man display manpage in english not
> > in russian. I have no idea which variables all versions of date out there
> > respect and which one wins. If you are sure LC_ALL is enough for everyone
> > - so be it.
>
> $ info libc
> ...
> Categories of Activities that Locales Affect
> ...
> `LC_ALL'
> This is not an environment variable;
please quote the correct part of documentation. LC_ALL is environment
variable; usually it should win over separate LC_* variables that in turn win
over LANG. But I repeat - I have no way to verify it for all combinations of
date/libc/glibc out there; autoconf sets all variables it needs to be on safe
side so actually instead of removing LANG I'd rather add LC_TIME.
-andrey
it is only a macro that you
> can use with `setlocale' to set a single locale for all purposes.
> Setting this environment variable overwrites all selections by the
> other `LC_*' variables or `LANG'.
next prev parent reply other threads:[~2003-09-14 14:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 6:50 2.6.0-test5-mm1 Andrew Morton
2003-09-09 7:02 ` 2.6.0-test5-mm1 Joshua Kwan
2003-09-09 21:57 ` 2.6.0-test5-mm1 Cliff White
2003-09-09 7:53 ` 2.6.0-test5-mm1 Jeremy Fitzhardinge
2003-09-10 19:59 ` 2.6.0-test5-mm1 usb keyboard prob Jonathan Brown
2003-09-10 21:17 ` 2.6.0-test5-mm1 Wiktor Wodecki
2003-09-11 6:53 ` 2.6.0-test5-mm1 William Lee Irwin III
2003-09-13 9:13 ` 2.6.0-test5-mm1 Alex Riesen
2003-09-14 8:46 ` 2.6.0-test5-mm1 Andrey Borzenkov
2003-09-14 13:52 ` 2.6.0-test5-mm1 Alex Riesen
2003-09-14 14:01 ` Andrey Borzenkov [this message]
2003-09-09 20:14 2.6.0-test5-mm1 Jan Ischebeck
2003-09-09 23:14 ` 2.6.0-test5-mm1 Joshua Kwan
2003-09-10 23:01 2.6.0-test5-mm1 Nakajima, Jun
2003-09-11 7:23 ` 2.6.0-test5-mm1 Wiktor Wodecki
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=200309141801.55700.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--cc=akpm@osdl.org \
--cc=fork0@users.sf.net \
--cc=linux-kernel@vger.kernel.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 NNTP newsgroup(s).