[Top][All Lists]

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

Re: Handling fatal signals in GNU make

From: Eli Zaretskii
Subject: Re: Handling fatal signals in GNU make
Date: Mon, 10 Jun 2019 19:35:29 +0300

> From: Paul Smith <address@hidden>
> Date: Sun, 09 Jun 2019 18:11:50 -0400
> Cc: address@hidden
> > This is what sigsuspend is for.
> Unfortunately sigsuspend() is not an option since it's not available on
> Windows (as far as I can tell).

Windows also doesn't have SIGCHLD, and most other signals involved in
this story.  So maybe the fact that sigsuspend is missing there is not
that bad?  The test for exited children is done differently on

> I haven't even considered VMS, which is still active.  Or any of the
> most-likely-disused ports such as MS-DOS or AmigaOS.

No SIGCHLD on MS-DOS, either: it's a single-process OS.

reply via email to

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