From: Michael Haubenwallner <michael.haubenwallner@ssi-schaefer.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] cygwin 3.1.0-0.4 (TEST)
Date: Mon, 16 Sep 2019 11:54:00 -0000 [thread overview]
Message-ID: <3e1a1596-3267-6f16-0aaf-cd860b9b8283@ssi-schaefer.com> (raw)
In-Reply-To: <d5d9f1da-5f42-48d4-d1c8-9ada6bc199e6@maxrnd.com>
Hi Mark,
On 9/14/19 12:08 AM, Mark Geisert wrote:
> Michael Haubenwallner wrote:
>> On 9/5/19 3:16 PM, Ken Brown wrote:
>>> The following packages have been uploaded to the Cygwin distribution
>>> as test releases:
>>>
>>> * cygwin-3.1.0-0.4
>>> * cygwin-devel-3.1.0-0.4
>>> * cygwin-doc-3.1.0-0.4
>>
>>> - New APIs: sched_getaffinity, sched_setaffinity, pthread_getaffinity_np,
>>> Â Â pthread_setaffinity_np, plus CPU_SET macros.
>>
>> There's some problem with <sched.h>, seen with boost-1.71.0/bootstrap.sh,
>> even after tweaking their sysinfo.cpp like this to include <sched.h>:
>>
>> Actually it is boost's fault to include <pthread.h> before defining _GNU_SOURCE,
>> but it feels like Cygwin should *not* define CPU_COUNT_S without _GNU_SOURCE.
> Thanks for the problem report. Blame me for this one. I believe your last
> suggestion is the correct fix but I want to double-check something additional.
> Shortly I'll submit a patch to correct this one way or another.
Fix does work as expected, thanks!
/haubi/
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2019-09-16 7:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 13:17 Ken Brown
2019-09-13 18:39 ` Michael Haubenwallner
2019-09-13 22:14 ` Mark Geisert
2019-09-16 11:54 ` Michael Haubenwallner [this message]
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=3e1a1596-3267-6f16-0aaf-cd860b9b8283@ssi-schaefer.com \
--to=michael.haubenwallner@ssi-schaefer.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).