On Sat, Jan 14, 2023 at 09:37:03PM +0100, Bruno Haible wrote:
> Eric Blake wrote:
> > Instead of using -- to force sh to realize the command being passed is
> > intended to be a script to run (even if it starts with - or +), it is
> > also possible to prepend a space.
>
> Indeed, that it simpler t
Hi Eric,
Continuing this mail thread:
https://lists.gnu.org/archive/html/bug-m4/2022-09/msg0.html
https://lists.gnu.org/archive/html/bug-m4/2023-01/msg4.html
https://lists.gnu.org/archive/html/bug-m4/2023-01/msg5.html
The situation is still the same on FreeBSD 14.0:
$ sh -c -- pwd
Eric Blake wrote:
> Instead of using -- to force sh to realize the command being passed is
> intended to be a script to run (even if it starts with - or +), it is
> also possible to prepend a space.
Indeed, that it simpler than testing whether the command starts with - or +.
> I'm thinking of try
On Fri, Sep 23, 2022 at 02:38:03AM +0200, Bruno Haible wrote:
> Hi,
>
> With the current m4 from git (branch-1.4), several tests fail on FreeBSD 13
> and AIX 7.1 and 7.2, indicating that the syscmd built-in is completely
> dysfunctional there:
Thanks for the report. I'm still thinking about this
Hi,
With the current m4 from git (branch-1.4), several tests fail on FreeBSD 13
and AIX 7.1 and 7.2, indicating that the syscmd built-in is completely
dysfunctional there:
$ gmake check
Checking ../../checks/001.preprocess
Checking ../../checks/002.debugging_
Checking ../../checks/003.command_li
