Re: AT_TESTED issues

[Ralf Wildenhues]

Ping.

* Ralf Wildenhues wrote on Sun, Oct 21, 2007 at 02:09:05PM CEST:
> * Eric Blake-1 wrote on Thu, Oct 18, 2007 at 06:15:03PM CEST:
> > 2007-10-18  Eric Blake  <address@hidden>
> > 
> >     Fix AT_TESTED, AT_KEYWORDS.
[...]
> 
> >     * tests/local.at (AT_TESTED): Add m4, perl.
> 
> If you do this, this fails:
> 
>   ./configure PERL=/some/where/not/in/PATH/perl
> 
> Likewise for m4.  I've been using it on some systems.  If there is
> another perl in the PATH, then the wrong data will be recorded.

At best, AT_TESTED([m4 perl]) finds different versions of the programs
than the first words of $M4, $PERL point to, at worst, the testsuite
fails because either m4 or perl do not live in $PATH at all.  I'm
hitting this on some test systems I have access to, where config.status
nicely saves my choice or $M4 and $PERL, but I forget to adjust $PATH
just for AT_TESTED:

OK to just revert this?

FWIW, this is exactly the reason why I find the AT_TESTED macro totally
useless.

Cheers,
Ralf

2007-11-18  Ralf Wildenhues  <address@hidden>

        * tests/local.at: Do not test m4, perl with AT_TESTED.

diff --git a/tests/local.at b/tests/local.at
index 298dfba..b17fff3 100644
--- a/tests/local.at
+++ b/tests/local.at
@@ -24,8 +24,6 @@ m4_pattern_allow([^m4_(define|shift)$])
 
 # Programs this package provides
 AT_TESTED([autom4te autoconf autoheader autoupdate autoreconf ifnames])
-# Programs this package depends on
-AT_TESTED([m4 perl])
 
 
 ## ---------------- ##