bug-gnulib
[Top][All Lists]
Advanced

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

Re: IBM z/OS compatibility issues - per-thread locale functions


From: Bruno Haible
Subject: Re: IBM z/OS compatibility issues - per-thread locale functions
Date: Mon, 18 Nov 2019 12:41:51 +0100
User-agent: KMail/5.1.3 (Linux/4.4.0-166-generic; KDE/5.18.0; x86_64; ; )

Hi Daniel,

> Locale-related configure findings:
> 
>     bash-2.03$ grep locale configure.out | fgrep -v '(cached)'
>     checking for xlocale.h... no
>     checking for duplocale... yes
>     checking for uselocale... yes
>     checking for newlocale... yes
>     checking for freelocale... yes
>     checking for a traditional french locale... fr_FR
>     checking whether locale.h defines locale_t... no
>     checking whether locale.h conforms to POSIX:2001... yes
>     checking whether uselocale works... no
>     checking for a traditional japanese locale... none
>     checking for a transitional chinese locale... none
>     checking for a french Unicode locale... none
>     checking whether the C locale is free of encoding errors... yes
>     checking whether wcwidth works reasonably in UTF-8 locales... yes
>     checking whether duplocale(LC_GLOBAL_LOCALE) works... no
>     checking whether setlocale supports the C locale... yes
>     checking whether wcrtomb works in the C locale... yes
>     checking for a turkish Unicode locale... none

I don't understand this.

> Please let me know if there is any additional reconnaissance I can
> provide that may be helpful.

Yes, I need more details here.

  1) Please make sure you build in a fresh directory ('rm -rf testdir'
     before you generate a new testdir), and have no global config cache.
  2) Run configure with option '-C'.
  3) Please provide all three of the following:
     - grep locale configure.out
     - grep -i locale config.cache
     - grep -i locale config.status

Bruno




reply via email to

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