On Thu, Oct 17, 2019 at 01:37:13PM -0400 I heard the voice of
Stefan Monnier, and lo! it spake thus:
>
> It's not just "often enough", it's "every time".
So much the better; easier to track down and verify a fix :)
> That's my question. When I try to run `m4` manually with
>
> /usr/bin/m4 -s ~/tmp/foo.m4 -
Check the output of the build, or the generated build/ctwm_config.h,
to see what M4CMD wound up being; maybe it's running a different one.
e.g.,
-- Enabling m4 support (/usr/bin/m4).
Or, maybe there's some trivial different in the syscmd() invocations?
--
Matthew Fuller (MF4839) | [email protected]
Systems/Network Administrator | http://www.over-yonder.net/~fullermd/
On the Internet, nobody can hear you scream.
