Woohoo!! About time! :)
On Tue, Dec 8, 2020 at 12:14 PM Zack Weinberg wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> We are pleased to announce stable release 2.70 of GNU Autoconf.
>
> This release includes eight years of development work since the
> previous release, 2.69.
Hi Peter,
On 3/14/2010 10:38 AM, Peter Johansson wrote:
Hello,
I experience that autoreconf, for some reason, thinks I'm not using
libtool. I slimmed down my configure.ac to the following:
AC_INIT([1.0], [hello])
AM_INIT_AUTOMAKE([foreign])
AC_LANG([C++])
AC_PROG_CXX
AC_PROG_LIBTOOL
When Autoconf is used without Automake, 'autoreconf --install' doesn't
install
a copy of the install-sh script when it detects the use of the
AC_PROG_INSTALL
macro in configure.ac. There are two problems here:
First, while the Autoconf manual indicates that Autoconf ships with a
version
of
When you enter './config.status --help' at the command line, you get:
$ ./config.status --help
`config.status' instantiates files from templates according to the
current configuration.
Usage: ./config.status [OPTION]... [FILE]...
...
The 'Usage' line above should read:
On 4/17/2009 10:07 PM, Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to John Calcote on 4/17/2009 3:39 PM:
When Autoconf is used without Automake, 'autoreconf --install' doesn't
install
a copy of the install-sh script when it detects the use
