Re: syscmd/esyscmd fail on windows with m4 1.4.13

[Eric Blake]

On 03/16/2010 09:15 AM, Henrique Martins wrote:
> Sent the message below to the gnuwin32-users list but got no
> response in about a week or so.  Trying here...

Thanks for the report.  However, you probably want to take the report
back to the gnuwin32 list, and ask them what value they used for
--with-syscmd-shell.  Or build m4 yourself, rather than relying on gnuwin32.

> Just tested it and both
>   syscmd(hostname)
>   esyscmd(hostname)
> work with 1.4.9, but error out with "no such file or directory"

This is symptomatic of not having the same shell as what m4 was compiled
to try and invoke (for example, if it was configure with ./configure
--with-syscmd-shell=/bin/sh, but you don't have /bin/sh, then syscmd
will fail with status 127 in trying to locate the missing sh).  For
Windows, it is possible to configure using --with-syscmd-shell=cmd,
which gives you Windows rather than sh semantics to syscmd, but without
knowing what the gnuwin32 folks did in their
build, I have no idea what you should be expecting from their
pre-compiled binary.

Another option would be to use the cygwin environment instead of the
gnuwin32; it is much more Linux-like, and I can vouch for the cygwin m4
1.4.14 build properly handling [e]syscmd (yes, the gnuwin32 folks are a
release behind, as of this email).

-- 
Eric Blake   address@hidden    +1-801-349-2682
Libvirt virtualization library http://libvirt.org

signature.asc
Description: OpenPGP digital signature