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

Hi Daniel, > config.h still has a > > #define HAVE_DUPLOCALE 1 > > line, however. This will be misleading for application code. Yes, there is a potential for application code to be misled. But - Any application code can do AC_CHECK_FUNCS_ONCE([duplocale]), and this would conflict with gnu

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

On Sat, 2019 Dec 14 08:36-05:00, Bruno Haible wrote: > On Freitag, 13. Dezember 2019 15:33:42 CET Daniel Richard G. wrote: > > On Fri, 2019 Dec 13 05:32-05:00, Bruno Haible wrote: > > > > > > This should fix it. Thanks for the feedback. > > > > Arrrgh, not quite there yet >_< > > > > Tested Git

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

On Freitag, 13. Dezember 2019 15:33:42 CET Daniel Richard G. wrote: > On Fri, 2019 Dec 13 05:32-05:00, Bruno Haible wrote: > > > > This should fix it. Thanks for the feedback. > > Arrrgh, not quite there yet >_< > > Tested Git 83710ffa. test-locale now builds, but test-duplocale still > does no

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

On Fri, 2019 Dec 13 05:32-05:00, Bruno Haible wrote: > > This should fix it. Thanks for the feedback. Arrrgh, not quite there yet >_< Tested Git 83710ffa. test-locale now builds, but test-duplocale still does not, failing in the same place. HAVE_WORKING_DUPLOCALE appears to be 1 (true). Isn't

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

Daniel Richard G. wrote: > I can now get past the library build, but then get errors compiling > test-duplocale.c and test-locale.c. The former fails at line 26: > > SIGNATURE_CHECK (duplocale, locale_t, (locale_t)); > > The latter fails at line 49: > > locale_t b = LC_GLOBAL_LOCALE; >

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

Hi Bruno, On Thu, 2019 Dec 12 07:56-05:00, Bruno Haible wrote: > > The REPLACE_DUPLOCALE=1 is wrong. HAVE_DUPLOCALE should be 0, not only > when set by localename.m4 but also when set by duplocale.m4. This > patch should fix it. Tested with Git ea54538a. I can now get past the library build, but

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

Hi Daniel, > > 3) Please provide all three of the following: > > - grep locale configure.out > ... > > - grep -i locale config.status > > bash-2.03$ grep -i locale config.status > S["gl_LTLIBOBJS"]=" alphasort.lo asnprintf.lo at-func2.lo > canonicalize-lgpl.lo cnd.lo dirfd.lo

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

On Mon, 2019 Nov 18 06:41-05:00, Bruno Haible wrote: > 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 whether wcrtomb works

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

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 >

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

Hi Bruno, On Sun, 2019 Nov 17 19:17-05:00, Bruno Haible wrote: > > This patch should do it. > > 2019-11-17 Bruno Haible > > locale, localename: Improve z/OS support. > Reported by Daniel Richard G. in > .

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

Hello Daniel, > BROKEN LOCALE FUNCTIONS > > The configure script finds the following: > > checking for xlocale.h... no > checking for duplocale... yes > checking for uselocale... yes > checking for newlocale... yes > checking for freelocale... yes > > checking whether lo