Paul Eggert <[EMAIL PROTECTED]> wrote:
> I couldn't do a bootstrap build of coreutils with the latest publicly
> released tools due to the "1.10a" in configure.ac. Is that "1.10a"
> obsolete now? Is it OK to use automake 1.10.1 now? Anyway, this
> patch worked around my bootstrap problem:
1.10a is deemed (at least by automake and m4) to indicate a newer
version than 1.10.1. counter-intuitive? This matters because
sort --version now disagrees with that ordering:
$ printf 'automake-1.10%s\n' .1 a|sort -V
automake-1.10a
automake-1.10.1
This stems from the new gnulib filevercmp module.
There's actually a minor dependency in coreutils on the
newer automake.
> 2008-10-15 Paul Eggert <[EMAIL PROTECTED]>
>
> * configure.ac (AM_INIT_AUTOMAKE): Bump Automake version from
> 1.10a to 1.10.1.
_______________________________________________
Bug-coreutils mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-coreutils
