[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: m4 on native Windows
From: |
Eric Blake |
Subject: |
Re: m4 on native Windows |
Date: |
Wed, 26 May 2021 08:52:49 -0500 |
User-agent: |
NeoMutt/20210205 |
On Fri, May 14, 2021 at 12:58:18PM +0200, Bruno Haible wrote:
> Compiling a recent m4 snapshot on native Windows:
> - The "make" step works fine.
> - The "make check" step fails. Find attached the log.
>
> Essentially, there are failures around syscmd, and error messages display
> the absolute file name of the 'm4.exe' executable.
Thanks for the report. I'll see if I can fine-tune any of these
tests, but the failures are in the testsuite and not the built
executable, so I'm okay with releasing even if these still fail.
> Checking ../../checks/021.macro_argu
> @ ../doc/m4.texi:1607: Origin of test
> ../../checks/021.macro_argu: stderr mismatch
> --- m4-tmp.432/m4-xerr 2021-05-14 02:31:09.407442400 +0200
> +++ m4-tmp.432/m4-err 2021-05-14 02:31:09.296595600 +0200
> @@ -1,2 +1,2 @@
> -C:\cygwin64\home\bruno\m4-2021-05-13\build-mingw64\src\m4.exe:stdin:1:
> Warning: too few arguments to builtin `index'
> -C:\cygwin64\home\bruno\m4-2021-05-13\build-mingw64\src\m4.exe:stdin:3:
> Warning: excess arguments to builtin `index' ignored
> +m4.exe:stdin:1: Warning: too few arguments to builtin `index'
> +m4.exe:stdin:3: Warning: excess arguments to builtin `index' ignored
Failures like this look like we just need to fix the sed script in
checks/check-them to properly filter the name output by native
Windows.
> Checking ../../checks/194.syscmd
> @ ../doc/m4.texi:6592: Origin of test
> ../../checks/194.syscmd: stdout mismatch
> --- m4-tmp.432/m4-xout 2021-05-14 02:37:05.500248600 +0200
> +++ m4-tmp.432/m4-out 2021-05-14 02:37:05.298096600 +0200
> @@ -1,3 +1,2 @@
>
> -foo
>
> @ ../doc/m4.texi:6592: Origin of test
> ../../checks/194.syscmd: stderr mismatch
> --- m4-tmp.432/m4-xerr 2021-05-14 02:37:05.875718100 +0200
> +++ m4-tmp.432/m4-err 2021-05-14 02:37:05.735120300 +0200
> @@ -0,0 +1,2 @@
> +m4.exe: syscmd subprocess failed: No such file or directory
> +m4.exe:stdin:2: cannot run command `echo foo': No such file or directory
These will indeed be hairier to fix, especially since it has now been
a long time since I've used a Windows machine.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org