Re: mingw and execute vs. posix_spawn

2009-03-06 Thread Bruno Haible
Eric Blake wrote: > @@ -44,7 +44,7 @@ dup_noinherit (int fd) > (DWORD) 0, /* DesiredAccess */ > FALSE, /* InheritHandle */ > DUPLICATE_SAME_ACCESS)) /* Options */ > -error (EXIT_FAILURE,

Re: mingw and execute vs. posix_spawn

2009-03-06 Thread Bruno Haible
Eric Blake wrote: > Even though execute, pipe, and wait-process work just fine on mingw, the fact > that they pull in a dependency on posix_spawn on all other platforms means > that > the build attempts to compile files, like lib/spawni.c or test-posix_spawn.c > that cause failures on mingw. O

Re: mingw and execute vs. posix_spawn

2009-03-06 Thread Bruno Haible
Eric Blake wrote: > * lib/execute.c (execute) [_MSC_VER || __MINGW32__]: Avoid > compiler warning about incompatible types. > * lib/pipe.c (create_pipe) [_MSC_VER || __MINGW32__]: Likewise. Applied as follows: 2009-03-06 Eric Blake * lib/execute.c (execute) [WIN32_NATIVE]: Cast argum

mingw and execute vs. posix_spawn

2009-03-03 Thread Eric Blake
Bruno, I've run into an issue trying to make m4 use the execute module. The problem boils down to the fact that posix_spawn isn't ported to mingw yet[1]. Even though execute, pipe, and wait-process work just fine on mingw, the fact that they pull in a dependency on posix_spawn on all other pla