Re: m4 on native Windows

[Eric Blake]

On Wed, May 26, 2021 at 08:52:51AM -0500, Eric Blake wrote:
> > +++ 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.

I'm still trying to figure out how the names differ.  Can you confirm
what is output by:
  src/m4 --help | head -n1

in that setup?  That output comes from usage() which uses program_name
directly, while the other messages come from calling error_at_line()
which uses program_invocation_name (on glibc) or getprogname()
(otherwise), but as far as I can tell, unless we are running under
libtool (where getprogname() strips off the lt- prefix), that should
resolve to the same program_name as just printed in usage().  So what
is going on differently in your native windows build that is changing
what error_at_line() produces?

At this point, I'm probably going to just go ahead and release 1.4.19
without trying to address the Windows testsuite failures.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org