From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: building libpng-1.6.29 fails with error in signal.h
Date: Tue, 04 Jul 2017 23:16:00 -0000 [thread overview]
Message-ID: <4003d202-e983-51ca-378e-a0254173ba11@cygwin.com> (raw)
In-Reply-To: <dd6cc3ce-d99a-ea06-46eb-e68d0efd7685@gmail.com>
On 2017-07-04 15:46, Marco Atzeri wrote:
> On 04/07/2017 20:59, Denis Excoffier wrote:
>> I tried to compile libpng-1.6.29 and failed at first. I obtain:
>>
>> /usr/include/cygwin/signal.h:328:34: error: unknown type name 'siginfo_t'
>> void (*sa_sigaction) ( int, siginfo_t *, void * );
>> ^
>> I really don't know which (signal.h or libpng) is okay (or none). Will
>> someone investigate this?
> > Reading
> http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/signal.h.html
>
> I have the impression that the current cygwin header behaviour
> is correct as siginfo_t is an extension POSIX.1-2008.
True, but I missed that struct sigaction (which is correctly guarded as
POSIX.1-1990) uses siginfo_t. This part needs to be guarded as
POSIX.1b-1993 without breaking the struct, as is done in glibc.
> In theory "_GNU_SOURCE" should be defined by default
No, I'll fix this in the header shortly, along with updating libpng.
--
Yaakov
--
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:[~2017-07-04 23:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-04 18:59 Denis Excoffier
2017-07-04 20:47 ` Marco Atzeri
2017-07-04 23:16 ` Yaakov Selkowitz [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=4003d202-e983-51ca-378e-a0254173ba11@cygwin.com \
--to=yselkowitz@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).