Eric Blake wrote on 2008-06-02:
| Does the execute module allow distinguishing exits due to signals from
| regular exits? M4 is currently documented as treating the sysval macro
| differently to allow the user to distinguish between signals, but it looks
| like wait_subprocess collapses all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 6/1/2008 3:58 AM:
| What about OSF/1 4.0 and 5.1? On these systems, CONFIG_SHELL gets set to
| /bin/ksh. I take this as an indication that /bin/sh is not POSIX conforming
| either. The manual pages of system() and popen()
Eric Blake wrote:
it could even allow a configure-time option for
mingw to pick a POSIX shell (particularly when targetting an MSYS build,
where such a shell is known to exist), rather than being hard-coded to the
current 'cmd /c' provided by system(). But it might also introduce
Hi Eric,
| It seems that your problem is that you want execute a script via system()
| and at the same time force a particular shell, namely the $CONFIG_SHELL
found
| at configure time?
Something along those lines - POSIX doesn't require m4 to use system(2),
merely that it treat the
