GNU bug report logs - #54073
[PATCH] tests: log autoconf & libtool version

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 54073 in the body.
You can then email your comments to 54073 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Mike Frysinger <vapier <at> gentoo.org>
To: automake-patches <at> gnu.org
Subject: [PATCH] tests: log autoconf & libtool version
Date: Sun, 20 Feb 2022 13:57:27 -0500

Having these in the sysconf log can be helpful when triaging test
failures from users.

* t/get-sysconf.sh: Log autoconf & libtoolize version.
---
 t/get-sysconf.sh | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/t/get-sysconf.sh b/t/get-sysconf.sh
index 77394ca82e0d..51ec7f5d1f23 100644
--- a/t/get-sysconf.sh
+++ b/t/get-sysconf.sh
@@ -46,6 +46,11 @@ $PERL -V || st=1
 # happen with older perl installation, or on MinGW/MSYS.
 $PERL -e 'use TAP::Parser; print $TAP::Parser::VERSION, "\n"' || :
 
+$AUTOCONF --version
+$AUTOCONF --help
+libtoolize --version
+libtoolize --help
+
 # It's OK if the selected Lex and Yacc programs don't know how to print
 # the version number or the help screen; those are usually available only
 # for Flex and Bison.
-- 
2.34.1

Message #8 received at 54073 <at> debbugs.gnu.org (full text, mbox):

From: Karl Berry <karl <at> freefriends.org>
To: vapier <at> gentoo.org
Cc: 54073 <at> debbugs.gnu.org
Subject: Re: [bug#54073] [PATCH] tests: log autoconf & libtool version
Date: Sun, 20 Feb 2022 15:25:39 -0700

    +$AUTOCONF --version
    +$AUTOCONF --help
    +libtoolize --version
    +libtoolize --help

Sure, all to the good.

Do we already log the automake version? What log is this, anyway :)?

Message #11 received at 54073 <at> debbugs.gnu.org (full text, mbox):

From: Mike Frysinger <vapier <at> gentoo.org>
To: Karl Berry <karl <at> freefriends.org>
Cc: 54073 <at> debbugs.gnu.org
Subject: Re: [bug#54073] [PATCH] tests: log autoconf & libtool version
Date: Sun, 20 Feb 2022 19:23:38 -0500

[Message part 1 (text/plain, inline)]

On 20 Feb 2022 15:25, Karl Berry wrote:
>     +$AUTOCONF --version
>     +$AUTOCONF --help
>     +libtoolize --version
>     +libtoolize --help
> 
> Sure, all to the good.
> 
> Do we already log the automake version?

i don't think so.  why would we care about the version installed in the host
system when we're compiling a new one ?  the host version shouldn't be used
by any compile or test steps unless i missed something.

> What log is this, anyway :)?

this is just for the test suite.  that way when people file reports & attach
test-suite.log, this test is included with extended system info so we don't
have to ask the user to run these commands for us.
-mike

[signature.asc (application/pgp-signature, inline)]

Message #14 received at 54073 <at> debbugs.gnu.org (full text, mbox):

From: Karl Berry <karl <at> freefriends.org>
To: vapier <at> gentoo.org
Cc: 54073 <at> debbugs.gnu.org
Subject: Re: [bug#54073] [PATCH] tests: log autoconf & libtool version
Date: Mon, 21 Feb 2022 16:31:13 -0700

    why would we care about the version installed in the host
    system when we're compiling a new one

We don't. But:

    this is just for the test suite.  that way when people file reports
    & attach test-suite.log, this test is included with extended system
    info ...

I guess the version of automake being tested is already reported in
test-suite.log, so fine. Sorry for the noise. -k

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.