> From: DJ Delorie <d...@redhat.com>
> Cc: gcc-patches@gcc.gnu.org, gdb-patc...@sourceware.org
> Date: Mon, 22 May 2017 15:38:40 -0400
>
> Since (or "if") nobody will (should) use waitpid() on mingw anyway, and
> since libiberty really wants to include waitpid.o, how difficult would
> it be to use some #ifdefs to have waitpid() just return an error on
> mingw? That at least gets past the mingw build problem.
Instead of making waitpid an always-failing stub on MinGW, wouldn't it
be better to make it work on MinGW? Like this:
--- libiberty/waitpid.c~0 2016-08-01 18:50:21.000000000 +0300
+++ libiberty/waitpid.c 2017-05-23 21:19:34.302415000 +0300
@@ -23,6 +23,11 @@ does the return value. The third argume
#include <sys/wait.h>
#endif
+#ifdef __MINGW32__
+#include <process.h>
+#define wait(s) _cwait(s,pid,_WAIT_CHILD)
+#endif
+
pid_t
waitpid (pid_t pid, int *stat_loc, int options ATTRIBUTE_UNUSED)
{
