public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: ‘SIG_SETMASK’ and -std=c99
Date: Sun, 06 Aug 2017 09:44:00 -0000	[thread overview]
Message-ID: <87vam16nez.fsf@Rainer.invalid> (raw)
In-Reply-To: <2adce715-b45b-ed1c-567e-68bc826710ec@gmail.com> (Marco Atzeri's	message of "Sun, 6 Aug 2017 11:04:26 +0200")

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

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


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs

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

  reply	other threads:[~2017-08-06  9:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-06  9:04 Marco Atzeri
2017-08-06  9:44 ` Achim Gratz [this message]
2017-08-06 14:52   ` Marco Atzeri
2017-08-06 16:16     ` Ken Brown
2017-08-06 17:00       ` Marco Atzeri
2017-08-06 20:43         ` Ken Brown
2017-08-06 21:49           ` Ken Brown

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=87vam16nez.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).