Re: Coreutils 5.0.1: spurious error from uniq

[Andreas Schwab]

Paul Eggert <address@hidden> writes:

|> We need a test program for this.  I cannot reproduce the problem on my
|> GNU/Linux host, under any of the locales it has installed.  What
|> locale were you using when you ran into the problem?

$ locale
LANG=en_US.UTF-8
LC_CTYPE=de_DE.UTF-8
LC_NUMERIC="en_US.UTF-8"
LC_TIME=POSIX
LC_COLLATE=POSIX
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES=en_US.UTF-8
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

This is fine-tuned to DTRT(tm) for my needs.  Maybe the LC_CTYPE and/or
LC_COLLATE settings are confusing glibc.  I'll check that, and see if
setting them to en_US.UTF-8 helps.

|> > The whole error checking in memcoll and xmemcoll is completely bogus.  The
|> > C standard says in 7.5#3:
|> 
|> It's not bogus, since it is relying on POSIX.

Ok, I didn't check POSIX.

Andreas.

-- 
Andreas Schwab, SuSE Labs, address@hidden
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."