Hi Ben,
* Ben Pfaff wrote on Mon, Aug 02, 2010 at 10:38:45PM CEST:
> One possible solution would be for autoscan to notice
> AC_PROG_LIBTOOL and then suppress a warning about AC_PROG_RANLIB.
> Is that a good solution?
Yes.
> If so, then I will see what it takes to implement it.
Thanks; unfortun
So gnulib could have --enable-c++.
I guess I missed some discussion on bug-gnulib. Overall, "cplusplus"
seems like it would have been simpler/more customary. (That ++ causes
endless hassle everywhere.)
Easier to remember option names? Dunno.
I'd say the opposite: allowing lots of "ran
[Please retain CC in followups. Thank you.]
In April 2008, Jack Bates reported that
autoscan recommends adding AC_PROG_RANLIB to configure.ac, but
that libtoolize subsequently complains about AC_PROG_RANLIB as
"obsolete".
The AC_PROG_RANLIB macro is not really obsolete from an Autoconf
point of
Hi Eric,
* Eric Blake wrote on Mon, Aug 02, 2010 at 10:07:41PM CEST:
> On 08/02/2010 01:18 PM, Ralf Wildenhues wrote:
> > group to run, its output will include a banner containing
> > @var{test-category-name} prior to any tests run from that category. The
> > banner should be no more than abou
On 08/02/2010 01:18 PM, Ralf Wildenhues wrote:
> * Noteworthy changes in release ?.? (-??-??) [?]
>
>
> +** AT_BANNER() with empty argument will cause visual separation from previous
> + test cagegory.
> +
> * Major changes in Autoconf 2.67 (2010-07-21) [stable]
s/cagegory/category/ -
Hello everybody.
Now that the regressions of autoconf 2.66 and the problems with the
release procedure of autoconf 2.67 seem solved, I'd like to ping this
bug report, which was probably overlooked due to the cropping up of
those (much more serious) issues.
Regards,
Stefano
The GNU Autoconf team is pleased to announce the stable release of
Autoconf 2.67. Autoconf is an extensible package of M4 macros that
produce shell scripts to automatically configure software source code
packages. These scripts can adapt the packages to many kinds of
UNIX-like systems without man
* Ralf Wildenhues wrote on Sat, Jul 31, 2010 at 06:31:54PM CEST:
> Quick question: we document
>
> -- Macro: AT_BANNER (TEST-CATEGORY-NAME)
> This macro identifies the start of a category of related test
> groups. When the resulting `testsuite' is invoked with more than
> one test
