DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=sk/bXCV2w5jOzjD4
	L7NbEFEw0nomKMrfCUaI71PQ4QBYD2KNoDpc0FldM4Sjky+KZTiAl28J5gTDDnm3
	YJUJSOdCnfCCyHrgswRsw2cOA3VwN67AMGDlGiUgClHPb/tf7zHPkozw5RWoz9OM
	TZwQk5vgqUOLKXU027AMDDw/upc=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Subject: =?UTF-8?B?UmU6IOKAmFNJR19TRVRNQVNL4oCZIGFuZCAtc3RkPWM5OQ==?=
To: cygwin AT cygwin DOT com
References: <2adce715-b45b-ed1c-567e-68bc826710ec AT gmail DOT com> <87vam16nez DOT fsf AT Rainer DOT invalid>
From: Marco Atzeri <marco DOT atzeri AT gmail DOT com>
Message-ID: <77932431-b0cc-0e23-3cb8-0659a5c3307a@gmail.com>
Date: Sun, 6 Aug 2017 16:51:56 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <87vam16nez.fsf@Rainer.invalid>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

On 06/08/2017 11:44, Achim Gratz wrote:
> Marco Atzeri writes:
>> building again hdf5-1.8.18 on latest cygwin I hit
>>
>> error: ‘SIG_SETMASK’ undeclared
>>
>> removing  "-std=c99" from CFLAGS solves the issue.
>
> https://stackoverflow.com/questions/20849917/invalid-signal-processing-library-in-linux

That is not very informative as signal.h is in C99.
http://www.open-std.org/jtc1/sc22/WG14/www/docs/n1256.pdf

however SIG_SETMASK is not
http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/signal.h.html

>
>> As before the "-std=c99" was not causing any problem , it is not clear
>> to me if the current behavior is correct or a side effect of latest
>> cygwin header reshuffle.
>
> The "-std=c*" options are not meant to expose any symbols that are not
> defined in the respective C standard.  You almost always want to use
> "-std=gnu*" instead if you target POSIX-y systems.

formally you are right. However it seems that Cygwin is now
more stringent than Linux where this problem does not arise.


> Regards,
> Achim.

Regards
Marco


--
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