From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Error: unknown type name ‘pthread_attr_t’ in signal.h
Date: Mon, 16 Oct 2017 08:55:00 -0000 [thread overview]
Message-ID: <590379dd-cffa-0b32-4d77-b043ddfe1457@gmail.com> (raw)
In-Reply-To: <CAH8yC8n+Dbr6ANUKrcnF+X2c_KWoJBDYXxmtTZyNHA1b1F7oAw@mail.gmail.com>
On 16/10/2017 10:39, Jeffrey Walton wrote:
> On Mon, Oct 16, 2017 at 3:12 AM, Jeffrey Walton <noloader@gmail.com> wrote:
>> Hi Everyone,
>>
>
> I think something is borked with the Cygwin headers. If I am parsing
> http://pubs.opengroup.org/onlinepubs/009695399/functions/xsh_chap02_02.html
> and https://cygwin.com/ml/cygwin/2006-01/msg00642.html correctly, it
> should be sufficient to define _XOPEN_SOURCE to 600. From the section
> "The _XOPEN_SOURCE Feature Test Macro":
>
> Since this volume of IEEE Std 1003.1-2001 is aligned with the ISO C
> standard, and since all functionality enabled by _POSIX_C_SOURCE set
> equal to 200112L is enabled by _XOPEN_SOURCE set equal to 600, there
> should be no need to define _POSIX_C_SOURCE if _XOPEN_SOURCE is so
> defined. Therefore, if _XOPEN_SOURCE is set equal to 600 and
> _POSIX_C_SOURCE is set equal to 200112L, the behavior is the same as
> if only _XOPEN_SOURCE is defined and set equal to 600...
>
>
> I would still appreciate some help in working around the compile failures.
>
> Jeff
>
hi Jeff,
see
/usr/include/sys/features.h
for explanation of the current behaviour and options
--
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
next prev parent reply other threads:[~2017-10-16 8:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 7:12 Jeffrey Walton
2017-10-16 8:39 ` Jeffrey Walton
2017-10-16 8:55 ` Marco Atzeri [this message]
2017-10-16 9:20 ` Corinna Vinschen
2017-10-16 14:59 ` Ken Brown
2017-10-17 22:36 ` Jeffrey Walton
2017-10-18 10:13 ` Corinna Vinschen
2017-10-18 11:52 ` Ken Brown
2017-10-18 14:11 ` Corinna Vinschen
2017-10-18 14:19 ` Ken Brown
2017-10-18 14:42 ` Yaakov Selkowitz
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=590379dd-cffa-0b32-4d77-b043ddfe1457@gmail.com \
--to=marco.atzeri@gmail.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).