From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.6.0-0.11
Date: Tue, 23 Aug 2016 16:20:00 -0000 [thread overview]
Message-ID: <20160823161152.GA6100@calimero.vinschen.de> (raw)
In-Reply-To: <35c2b18f-ac98-d69e-32fe-2eae2d128f85@SystematicSw.ab.ca>
[-- Attachment #1: Type: text/plain, Size: 863 bytes --]
On Aug 23 07:27, Brian Inglis wrote:
> Compared lists of locale_t headers and functions for POSIX, Cygwin,
> and glibc, attached below for comparison, and found:
>
> * missed string.h(strerror_l) on my first check;
> not sure if you can implement that easily on Windows?
>
> * GNU also supports wchar.h(wcsftime_l) and time.h(strptime_l);
>
> * GNU also defines string.h(str[n]casecmp_l) functions as an extension,
> as well as in POSIX specified strings.h.
I just applied a couple of patches to add the missing strerror_l,
strptime_l and wcsftime_l. I also added the missing str[n]casecmp_l
prototypes to strings.h. I'll create a new test release in a bit.
Thanks a lot,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-08-23 16:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-20 22:09 Corinna Vinschen
2016-08-23 13:41 ` Brian Inglis
2016-08-23 16:20 ` Corinna Vinschen [this message]
2016-08-24 8:22 ` Brian Inglis
2016-08-24 8:28 ` Brian Inglis
2016-08-24 8:31 ` Corinna Vinschen
2016-08-24 18:29 ` Brian Inglis
2016-08-24 18:53 ` Corinna Vinschen
2016-08-25 7:30 ` Brian Inglis
2016-08-25 10:03 ` Corinna Vinschen
2016-08-25 14:46 ` Brian Inglis
2016-08-25 14:48 ` Eliot Moss
2016-08-25 15:01 ` Corinna Vinschen
2016-08-25 15:29 ` Brian Inglis
2016-08-25 22:23 ` Eliot Moss
2016-08-25 15:21 ` Eric Blake
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160823161152.GA6100@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/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).