Re: [PATCH 4/4] Windows: MSYS Autotools doc disabling hack

[Eli Zaretskii]

> Date: Sat, 20 Apr 2013 15:52:03 +0100
> From: Ray Donnelly <address@hidden>
> Cc: address@hidden
> 
> I tried with various autoconf versions, including 2.65, and also with three
> different versions of m4.exe ( all from
> http://sourceforge.net/projects/mingw/files/MSYS/Extension/m4/ ) with both
> dos and unix line-endings and each time ran into the same problem.

Then maybe it's Automake, or Perl, or one of the programs invoked by
Automake or Autoconf when you run 'autoreconf'.  How about removing
the MinGW bin/ directory from PATH and watching for any error
messages?  Any MinGW program (as opposed to MSYS program) that gets
run by 'autoreconf' is a possible suspect; install its MSYS namesake
and see if the problem goes away.

> Eli, would it be possible to describe your environment?

What exactly do you want me to describe?  It's a fairly complete MSYS
installation.  I've been configuring and building Unix and GNU
packages with it for more than a year.

> I tar.xz'ed (hopefully all of) the pertinent files via the following:
> 
> git clean -dxf; autoconf -v -i -d > autoconf.log 2>&1; tar -cJf
> gnumake-autoconf.tar.xz autom4te.cache configure.ac acinclude.m4 configure
> autoconf.log
> 
> I'm not sure if attachments work, or are frowned up, so here's my archive
> on Dropbox:
> 
> https://www.dropbox.com/s/uo16sugl70rk60n/gnumake-autoconf.tar.xz

I see ^M characters here and there in your autom4te.cache/output.0 and
in autom4te.cache/traces.0 files.  In fact, one such place in traces.0
is exactly at the locus of your problem:

  m4trace:configure.ac:512: -1- AC_CONFIG_FILES([Makefile glob/Makefile 
po/Makefile.in config/Makefile \^M
                   doc/Makefile w32/Makefile])

There are no such ^M characters in the corresponding files I have on
my machine:

  m4trace:configure.ac:512: -1- AC_CONFIG_FILES([Makefile glob/Makefile 
po/Makefile.in config/Makefile \
                   doc/Makefile w32/Makefile])

So it definitely looks like some program invoked in the process is a
MinGW (or otherwise native Windows) program, not an MSYS program.
Find it and install the corresponding MSYS package, and the problem
will most probably go away.  Or maybe you should just re-arrange your
PATH so that MSYS's bin directory comes earlier.