Re: using git Libtool with Autoconf 2.59, Automake 1.9.6

2010-08-22 Thread Ralf Wildenhues
* Gary V. Vaughan wrote on Sat, Aug 21, 2010 at 12:27:12PM CEST:
 On 21 Aug 2010, at 12:06, Ralf Wildenhues wrote:
  I tried running the Libtool test suites with old Autoconf 2.59 and
  Automake 1.9.6 (on GNU/Linux only) after 'autoreconf -fvi'-ing all
  but the toplevel directory with those tools.  I was surprised to see
  that it still works more or less!  :-)
  
  This patch fixes the fall-out.  OK to push if the use of $at_status is
  sanctioned?
  http://thread.gmane.org/gmane.comp.sysutils.autoconf.patches/7323
 
 Nice catch!  I have no idea about at_status, but pending that please
 do push.

Pushed now, under the provisional OK from Paul on autoconf-patches.
(If Autoconf does change later, then we're still not worse off than we
were before the patch, because at_status is only examined in the failure
case anyway.)

Thanks for the speedy review!
Ralf



Re: using git Libtool with Autoconf 2.59, Automake 1.9.6

2010-08-21 Thread Gary V. Vaughan
Hallo Ralf,

On 21 Aug 2010, at 12:06, Ralf Wildenhues wrote:
 I tried running the Libtool test suites with old Autoconf 2.59 and
 Automake 1.9.6 (on GNU/Linux only) after 'autoreconf -fvi'-ing all
 but the toplevel directory with those tools.  I was surprised to see
 that it still works more or less!  :-)
 
 This patch fixes the fall-out.  OK to push if the use of $at_status is
 sanctioned?
 http://thread.gmane.org/gmane.comp.sysutils.autoconf.patches/7323

Nice catch!  I have no idea about at_status, but pending that please
do push.

Cheers,
-- 
Gary V. Vaughan (g...@gnu.org)  



PGP.sig
Description: This is a digitally signed message part


using git Libtool with Autoconf 2.59, Automake 1.9.6

2010-08-20 Thread Ralf Wildenhues
I tried running the Libtool test suites with old Autoconf 2.59 and
Automake 1.9.6 (on GNU/Linux only) after 'autoreconf -fvi'-ing all
but the toplevel directory with those tools.  I was surprised to see
that it still works more or less!  :-)

This patch fixes the fall-out.  OK to push if the use of $at_status is
sanctioned?
http://thread.gmane.org/gmane.comp.sysutils.autoconf.patches/7323

Thanks,
Ralf

Fix getopt tests to skip with Autoconf  2.61.

* tests/getopt-m4sh.at (_LT_AT_GETOPT_M4SH_SETUP): Skip the test
of 'autom4te --language=m4sh' exits 63 because version 2.61 is
required.  Allows the testsuite to complete successfully with
Autoconf 2.59 and Automake 1.9.6.

diff --git a/tests/getopt-m4sh.at b/tests/getopt-m4sh.at
index 3e58db1..d2df827 100644
--- a/tests/getopt-m4sh.at
+++ b/tests/getopt-m4sh.at
@@ -48,12 +48,9 @@ M4SH_GETOPTS(
 ]])
 m4_pattern_forbid([m4_include])
 m4_pattern_forbid([AS_INIT])
-
-$M4SH -B $abs_top_srcdir/libltdl/config options.m4sh \
-| $SED \
-   -e s,@LN_S\@,$LN_S,g \
-   -e s,@SED\@,$SED,g \
- options
+AT_CHECK([$M4SH -B $abs_top_srcdir/libltdl/config options.m4sh  t-options],
+[], [], [], [AT_CHECK([test $at_status -eq 63  exit 77])])
+$SED s,@LN_S\@,$LN_S,g;s,@SED\@,$SED,g t-options  options
 ])# _LT_AT_GETOPT_M4SH_SETUP