On Mon, Jan 05, 2004 at 08:53:23AM +0100, Jan Minar wrote:
> On Sun, Jan 04, 2004 at 04:58:50PM +, Colin Watson wrote:
> > On Sun, Jan 04, 2004 at 03:54:29PM +0100, David Baron wrote:
> > > Most everything I try to do, packages, compiles, etc., kick on the env locale.
> > >
> > > They say make
On Sun, Jan 04, 2004 at 04:58:50PM +, Colin Watson wrote:
> On Sun, Jan 04, 2004 at 03:54:29PM +0100, David Baron wrote:
> > Most everything I try to do, packages, compiles, etc., kick on the env locale.
> >
> > They say make sure your environment has (and the kernel supports):
> > LANG=en_ENu
On Sun, Jan 04, 2004 at 03:54:29PM +0100, David Baron wrote:
> Most everything I try to do, packages, compiles, etc., kick on the env locale.
...
> the kernel does not support en_us.
Like Colin said, it has nothing to do with Kernel.
It is one of glibc thing.
locales GNU C Library: National L
On Sun, Jan 04, 2004 at 03:54:29PM +0100, David Baron wrote:
> Most everything I try to do, packages, compiles, etc., kick on the env locale.
>
> They say make sure your environment has (and the kernel supports):
> LANG=en_ENus
> LC not set
> LANGUAGE=en_us
en_US, not either en_ENus or en_us. Als
Most everything I try to do, packages, compiles, etc., kick on the env locale.
They say make sure your environment has (and the kernel supports):
LANG=en_ENus
LC not set
LANGUAGE=en_us
(Yes, the US rules the world!)
I may have my arguments with the parenthetical alleged fact but it is a fact
th
5 matches
Mail list logo