On 10/08/17 15:10, Paul Eggert wrote:
Tom G. Christensen wrote:
This broke the build on CentOS 6 since it has glibc 2.12 which is from
before the introduction of the internal __fsword_t type.
Thanks for reporting that. I reproduced the problem on a nearby old
server and fixed it by installing
Tom G. Christensen wrote:
> /usr/tgcware/gcc45/bin/gcc -std=gnu99 -g -O2 -L/usr/tgcware/lib
> -R/usr/tgcware/lib -o test-fts test-
> fts.o ../gllib/libgnu.a -lm -lm -lm-lm -lm -lm
> Undefined first referenced
> symbol in file
> libi
On 08/11/2017 11:21 AM, Tom G. Christensen wrote:
This exposed another problem when using external gettext:
/usr/tgcware/gcc45/bin/gcc -std=gnu99 -g -O2 -L/usr/tgcware/lib
-R/usr/tgcware/lib -o test-fts test-
fts.o ../gllib/libgnu.a -lm -lm -lm-lm -lm -lm
Undefined
On 08/11/2017 11:46 AM, Bruno Haible wrote:
This should fix it:
Ah, thanks, please ignore my previous message on this topic.
Eric Blake wrote:
> Still, if we are advocating mixed locale
> execution, we MUST ensure sane defaults for ALL of the LC_* variables.
In theory all the LC_* variables, yes. In practice, only those locale categories
that the programs actually uses (e.g. test-quotearg.c). Which rarely goes
beyond LC
