From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: [PATCH] Feature test macros overhaul: signal.h (part 3)
Date: Mon, 19 Jun 2017 11:02:00 -0000 [thread overview]
Message-ID: <20170619110249.GB10902@calimero.vinschen.de> (raw)
In-Reply-To: <7047def8-194f-ca3a-0b46-dbf51a8d4b02@foss.arm.com>
[-- Attachment #1: Type: text/plain, Size: 816 bytes --]
On Jun 15 15:20, Thomas Preudhomme wrote:
> Please find attached a proposed git-format patch fixing both these issues:
>
> Commit 8a3b3bb4d7224d419cc1a4af60ccf7e70edc876b changed the guard on
> some functions from _POSIX_THREADS to __POSIX_VISIBLE. As a consequence,
> some use of siginfo_t and pthread_t became visible under configurations
> where _POSIX_THREADS is unset but __POSIX_VISIBLE is. Build then fails
> because the definition of those types are still unavailable.
>
> This commit make those type definition visible for __POSIX_VISIBLE
> configurations. This requires moving the siginfo_t definition out of the
> RTEMS specific definitions in sys/signal.h while still guarding it
> against cygwin case.
Pushed.
Thanks,
Corinna
--
Corinna Vinschen
Cygwin Maintainer
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-06-19 11:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 20:00 [PATCH] stdio.h: guard function macros with !__cplusplus Yaakov Selkowitz
2017-06-13 20:01 ` [PATCH] Feature test macros overhaul: signal.h (part 3) Yaakov Selkowitz
2017-06-15 9:48 ` Thomas Preudhomme
2017-06-15 12:52 ` Thomas Preudhomme
2017-06-15 14:20 ` Thomas Preudhomme
2017-06-19 8:29 ` Thomas Preudhomme
2017-06-19 11:02 ` Corinna Vinschen [this message]
2017-06-14 8:48 ` [PATCH] stdio.h: guard function macros with !__cplusplus 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=20170619110249.GB10902@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=newlib@sourceware.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).