Re: Trunk r117046 fails on systems with older automake

[Eli Zaretskii]

> From: Andy Moreton <address@hidden>
> Date: Wed, 07 May 2014 00:53:37 +0100
> 
> On Tue 06 May 2014, Glenn Morris wrote:
> 
> > Hey, so please actually *give the details* of the problem that *you* see
> > caused by r117046.
> 
> I see exactly the same problems as Juanma and everybody else trying to
> get the autotools stuff working again on Windows:
> 
> Checking whether you have the necessary tools...
> (Read INSTALL.REPO for more details on building Emacs)
> 
> Checking for autoconf (need at least version 2.65)...
> ok
> Checking for automake (need at least version 1.11)...
> ok
> Checking for pkg-config (need at least version 0.9.0)...
> ok
> Checking for pkg.m4...
> Can't locate Automake/Getopt.pm in @INC (@INC contains: 
> /usr/share/automake-1.11 /usr/lib/perl5/5.8/msys /usr/lib/perl5/5.8 
> /usr/lib/perl5/site_perl/5.8/msys /usr/lib/perl5/site_perl/5.8 
> /usr/lib/perl5/site_perl/5.8 /usr/lib/perl5/vendor_perl/5.8/msys 
> /usr/lib/perl5/vendor_perl/5.8 /usr/lib/perl5/vendor_perl/5.8 .) at 
> /c/emacs/mingw-devel/msys/bin/aclocal line 984.
> BEGIN failed--compilation aborted at /c/emacs/mingw-devel/msys/bin/aclocal 
> line 984.
> ok
> Your system has the required tools.
> Running "ACLOCAL_PATH='/c/emacs/mingw-devel/share/aclocal' autoreconf -fi -I 
> m4" ...
> configure.ac:70: error: possibly undefined macro: AS_ECHO
>       If this token and others are legitimate, please use m4_pattern_allow.
>       See the Autoconf documentation.
> configure.ac:1351: error: possibly undefined macro: PKG_PROG_PKG_CONFIG
> configure.ac:1354: error: possibly undefined macro: PKG_CHECK_MODULES
> configure.ac:1363: error: possibly undefined macro: m4_default
> configure.ac:2293: error: possibly undefined macro: PKG_CONFIG
> autoreconf: /usr/bin/autoconf-2.68 failed with exit status: 1

Do you have pkg.m4 in MSYS share/aclocal directory?  If not, does
putting that file there solve the problem?  If not, perhaps you don't
have pkg-config installed, and should install it (see my other
messages in this thread).

> This all seems to be caused by the crazy mixture of tools required to
> get a native Win32 emacs built. The notes in nt/INSTALL are very useful
> but it is still quite some way from there to having a working toolchain.

Please tell what is missing from nt/INSTALL.