[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Signals on Mingw

From: Eli Zaretskii
Subject: Re: Signals on Mingw
Date: Mon, 23 Nov 2020 18:09:40 +0200

> From: Reuben Thomas <rrt@sc3d.org>
> Date: Sun, 22 Nov 2020 23:46:37 +0000
> Cc: bug-gnulib <bug-gnulib@gnu.org>
>    - Is it useful to have these signal names defined at all? If they can never
>      occur on native Windows, it does not necessarily make sense to define 
> them.
> If I wanted native (non-POSIX) functionality, I would not have used the 
> signal-h module.
> However, it seems _POSIX, when it was used in MSVC, may refer to Windows's 
> old POSIX subsystem:
> https://sourceforge.net/p/mingw-w64/mailman/message/33014416/
>  Also consider the workarounds that Gnulib already does, in
>  doc/posix-headers/signal.texi .
> I'm already using this, of course! It defines SIGPIPE (but not other missing 
> signals).
> signal.texi claims that sigset_t will be defined on Windows, but it does this 
> just by #including <sys/types.h>,
> which does not define sigset_t unless _POSIX is defined.
> The only mention I can find of _POSIX in gnulib is in 
> doc/posix-functions/getlogin.texi, which mentions that
> getlogin is only defined on mingw if _POSIX is defined (as I noted above). 
> The solution of the getlogin module
> is to use the unistd module to declare getlogin, if I understand correctly.

Can you elaborate what are you using this module for in the MinGW
build?  AFAIK, Posix signals can never work well enough on Windows to
care about them.  Maybe I'm missing something.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]