Re: FYI, temporary "make check" build requirement

[Jim Meyering]

Ralf Wildenhues <address@hidden> wrote:

> Hello Jim,
>
> * Jim Meyering wrote on Thu, Nov 01, 2007 at 12:59:49PM CET:
>> I noticed some minor of "make check" failures.
>> Once you've built autoconf, if you want to run "make check" with some
>> other version of autoconf tools in your path, here's what you have to
>> do in order to avoid a couple of spurious test failures due to version
>> string mismatch:
>>
>>   touch configure.ac && PATH=$PWD/tests:$PATH make check
>>
>> That ensures that all of the generated files are regenerated
>> using the just-built tools, rather than the ones in your path.
...
> For this, it would help if you posted those spurious test failures.

Sure.

  1: Syntax of the shell scripts                     ok
  2: Syntax of the Perl scripts                      ok
  3: autom4te cache                                  ok
  4: autom4te --force                                ok
  5: autoconf --trace: user macros                   ok
  6: autoconf --trace: builtins                      ok
  7: autoconf: forbidden tokens, basic               ok
  8: autoconf: forbidden tokens, exceptions          ok
  9: autoconf: automatically allowed tokens          ok
 10: autoconf: the empty token                       ok
 11: autoconf: subdirectories                        ok
 12: autoconf: input from stdin                      ok
 13: autoconf: AC_AUTOCONF_VERSION                   FAILED (tools.at:419)
 14: ifnames                                         ok
 15: autoheader                                      ok
 16: autoupdate                                      ok
 17: autoupdating AC_LINK_FILES                      ok
 18: autoupdating AC_PREREQ                          FAILED (tools.at:676)


>From the log for 13,

    ./tools.at:419: grep 'version 2.61a-248-dc51 version' configure
    stdout:
    ./tools.at:419: exit code was 1, expected 0

It couldn't find the current version string (set when I ran "make dist"
just before).  The actual version string recorded in configure is

    $ grep version.2.61a configure
    version 2.61a-249-10281-dirty version

And that is easy to fix.  Just run "make clean; make" to regenerate
stale files like autoconf, autoheader, autom4te, etc.

This is still the new dependency problem that I partially addressed
already, and for which you proposed a new VERSION file.
Those files should all depend on the new version, one way or another.

That's why I said it was a temporary work-around.
The fix won't be hard.