From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.5.0-0.8
Date: Mon, 21 Mar 2016 17:59:00 -0000 [thread overview]
Message-ID: <56F0018C.9070505@cornell.edu> (raw)
In-Reply-To: <20160321130651.GA2796@calimero.vinschen.de>
On 3/21/2016 9:06 AM, Corinna Vinschen wrote:
> Hi Ken,
>
> On Mar 21 08:05, Ken Brown wrote:
>> On 3/20/2016 4:24 PM, Yaakov Selkowitz wrote:
>>> On 2016-03-20 12:29, Ken Brown wrote:
>>>>>> Never mind. I just sent a report to bug-gnulib, so you can follow up
>>>>>> there.
>>>>
>>>> http://lists.gnu.org/archive/html/bug-gnulib/2016-03/msg00054.html
>>>>
>>>> Please check what I wrote in response to Paul and correct any mistakes I
>>>> might have made.
>>>
>>> Treating Cygwin just like glibc should generally be the solution.
>>
>> The problem is now fixed in upstream Gnulib.
>
> I just read the thread and it occured to me that this doesn't only
> affect Cygwin, but all systems using newlib starting with the next
> version of newlib.
>
> That reminds me that we have to bump newlib's version about now.
>
> Would you mind to follow up with that problem on bug-gnulib? The test
> should probably look like this, more or less:
>
> #!((defined __GLIBC__ \
> || (defined __NEWLIB__ \
> && ((__NEWLIB__ == 2 && __NEWLIB_MINOR__ >= 4) || __NEWLIB__ >= 3))) \
> && !defined __UCLIBC__)
>
> As for the actual version number to test I have to talk to Jeff if we
> can change the version to 2.4 or at least 2.3.1. 2.4 would simplify the
> test in gnulib, otherwise the test gets a bit more complicated.
Sure, I'll follow up on bug-gnulib as soon as you settle on the version
number.
Ken
next prev parent reply other threads:[~2016-03-21 14:13 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <announce.20160318203409.GA11113@calimero.vinschen.de>
[not found] ` <56EC6BDA.7050505@cornell.edu>
2016-03-18 21:45 ` Corinna Vinschen
2016-03-18 22:25 ` Ken Brown
2016-03-18 22:40 ` Ken Brown
2016-03-18 23:05 ` Yaakov Selkowitz
2016-03-18 23:29 ` Yaakov Selkowitz
2016-03-19 2:24 ` Ken Brown
2016-03-19 10:32 ` Corinna Vinschen
2016-03-19 12:34 ` Ken Brown
2016-03-19 18:03 ` Ken Brown
2016-03-20 15:26 ` Corinna Vinschen
2016-03-20 19:27 ` Ken Brown
2016-03-20 19:40 ` Ken Brown
2016-03-20 20:18 ` Ken Brown
2016-03-20 20:47 ` Yaakov Selkowitz
2016-03-21 14:13 ` Ken Brown
2016-03-21 16:30 ` Corinna Vinschen
2016-03-21 17:59 ` Ken Brown [this message]
2016-03-22 11:15 ` Corinna Vinschen
2016-03-22 14:59 ` Ken Brown
2016-03-30 21:17 ` Corinna Vinschen
2016-03-31 11:55 ` Ken Brown
2016-03-20 4:50 ` Yaakov Selkowitz
2016-03-20 15:18 ` Corinna Vinschen
2016-03-20 10:59 ` Achim Gratz
2016-03-20 11:14 ` Marco Atzeri
2016-03-20 15:25 ` Corinna Vinschen
2016-03-20 19:27 ` Achim Gratz
2016-03-20 20:53 ` Corinna Vinschen
2016-03-20 21:30 ` Corinna Vinschen
2016-03-20 20:24 ` Achim Gratz
2016-03-20 20:45 ` Yaakov Selkowitz
2016-03-22 9:31 ` Achim Gratz
2016-03-25 9:00 ` Dodgy functions (was: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.5.0-0.8) Achim Gratz
2016-03-26 0:16 ` Dodgy functions Achim Gratz
2016-03-26 19:41 ` Dodgy functions (finitel, strold) Achim Gratz
2016-03-29 16:09 ` Doug Henderson
2016-03-29 16:09 ` Corinna Vinschen
2016-04-01 19:04 ` Achim Gratz
2016-03-22 17:43 ` [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.5.0-0.8 Chris Sutcliffe
2016-03-22 18:02 ` Corinna Vinschen
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=56F0018C.9070505@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-apps@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).