On 8/6/2017 4:43 PM, Ken Brown wrote:
On 8/6/2017 12:59 PM, Marco Atzeri wrote:
hdf5 seems wrong to use sigsetjmp and C99 but Cygwin seems to
have a consistency issue.
I think you're right that Cygwin shouldn't declare or define sigsetjmp
under -std=c99. Here's a simple test:
$ cat test.c
On 8/6/2017 12:59 PM, Marco Atzeri wrote:
hdf5 seems wrong to use sigsetjmp and C99 but Cygwin seems to
have a consistency issue.
I think you're right that Cygwin shouldn't declare or define sigsetjmp
under -std=c99. Here's a simple test:
$ cat test.c
#include
int
main ()
{
sigjmp_buf e
On 06/08/2017 18:16, Ken Brown wrote:
On 8/6/2017 10:51 AM, Marco Atzeri wrote:
On 06/08/2017 11:44, Achim Gratz wrote:
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 P
On 8/6/2017 10:51 AM, Marco Atzeri wrote:
On 06/08/2017 11:44, Achim Gratz wrote:
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 righ
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
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 an
6 matches
Mail list logo
