bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: "Daniel Richard G." <skunk@iSKUNK.ORG>
To: "Bruno Haible" <bruno@clisp.org>
Cc: bug-gnulib@gnu.org
Subject: Re: IBM z/OS compatibility issues - per-thread locale functions
Date: Thu, 19 Dec 2019 18:46:36 -0500	[thread overview]
Message-ID: <2f1a81cd-6eaa-4b5d-83e3-5914b234c70b@www.fastmail.com> (raw)
In-Reply-To: <16620594.a5J0cL7pUW@omega>

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 83710ffa. test-locale now builds, but test-duplocale 
> > still does not, failing in the same place. HAVE_WORKING_DUPLOCALE 
> > appears to be 1 (true).
> 
> Oops. The patch below should fix that (hopefully).

I'm happy to report that the build now completes without issue. The 
test-duplocale test exits with status 77, giving the message "Skipping 
test: function duplocale not available".

> > Isn't it possible to get a final result of HAVE_DUPLOCALE=0,
> > REPLACE_DUPLOCALE=0,
> 
> We have that result already, as you showed through
> 'grep -i locale config.status'.

config.h still has a

    #define HAVE_DUPLOCALE 1

line, however. This will be misleading for application code.


--Daniel


-- 
Daniel Richard G. || skunk@iSKUNK.ORG
My ASCII-art .sig got a bad case of Times New Roman.


  reply	other threads:[~2019-12-19 23:47 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-05 18:03 IBM z/OS compatibility issues Daniel Richard G.
2019-11-05 22:23 ` Paul Eggert
2019-11-06 14:57   ` Daniel Richard G.
2019-11-06 19:32     ` Paul Eggert
2019-11-08 21:22       ` Daniel Richard G.
2019-11-17 23:21         ` Bruno Haible
2019-11-18 19:30           ` Daniel Richard G.
2019-12-13 12:58             ` Bruno Haible
2019-12-14  1:51               ` Daniel Richard G.
2019-12-14 13:51                 ` Bruno Haible
2020-01-09  5:46                   ` Daniel Richard G.
2019-11-18  0:17 ` IBM z/OS compatibility issues - per-thread locale functions Bruno Haible
2019-11-18  5:36   ` Daniel Richard G.
2019-11-18 11:41     ` Bruno Haible
2019-11-18 18:49       ` Daniel Richard G.
2019-12-12 12:56         ` Bruno Haible
2019-12-12 19:35           ` Daniel Richard G.
2019-12-13 10:32             ` Bruno Haible
2019-12-13 20:33               ` Daniel Richard G.
2019-12-14 13:36                 ` Bruno Haible
2019-12-19 23:46                   ` Daniel Richard G. [this message]
2019-12-20  6:43                     ` Bruno Haible
2019-11-18  3:18 ` IBM z/OS compatibility issues - pthread Bruno Haible
2019-11-18 21:06   ` Daniel Richard G.
2019-12-13 12:43     ` Bruno Haible
2019-12-13 21:10       ` Daniel Richard G.
2019-12-14 13:42         ` Bruno Haible
2019-12-20  0:10           ` Daniel Richard G.
2019-12-21  5:30             ` Bruno Haible
2019-11-18  3:24 ` IBM z/OS compatibility issues - shell environment Bruno Haible
2019-11-18 23:13   ` Daniel Richard G.
2019-11-18  3:34 ` IBM z/OS compatibility issues - environment variables Bruno Haible
2019-11-19  3:20   ` Daniel Richard G.
2019-11-18  3:41 ` IBM z/OS compatibility issues - miscellaneous bugs Bruno Haible
2019-11-19  3:39   ` Daniel Richard G.

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2f1a81cd-6eaa-4b5d-83e3-5914b234c70b@www.fastmail.com \
    --to=skunk@iskunk.org \
    --cc=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).