automake-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

2-gary-AC_LIBTOOL_TAGS-args.patch


From: Gary V. Vaughan
Subject: 2-gary-AC_LIBTOOL_TAGS-args.patch
Date: Thu, 15 Jan 2004 16:39:03 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20030925 Thunderbird/0.3

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Without this patch CVS automake barfs during libtool bootstrap :-(

Cheers,
        Gary.
- --
~  ())_. Gary V. Vaughan     gary@(oranda.demon.co.uk|gnu.org)
~  ( '/  Research Scientist  http://www.oranda.demon.co.uk       ,_())____
~  / )=  GNU Hacker          http://www.gnu.org/software/libtool  \'      `&
`(_~)_  Tech' Author        http://sources.redhat.com/autobook   =`---d__/
_________________________________________________________
This patch notification generated by cvsapply version 0.8
http://savannah.gnu.org/projects/cvs-utils
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD4DBQFABsInFRMICSmD1gYRAhI8AJiJhs/YJe3clWriAywE+YG37WI6AJwJF9SD
ee8a95GLKmodNFSa9+fwJw==
=c+k7
-----END PGP SIGNATURE-----
Index: ChangeLog
from  Gary V. Vaughan  <address@hidden>

        * automake.in (scan_autoconf_traces): AC_LIBTOOL_TAGS can be
        correctly called without arguments as evidenced by the libtool
        demo directories.

Index: automake.in
===================================================================
RCS file: /cvs/automake/automake/automake.in,v
retrieving revision 1.1540
diff -u -p -u -r1.1540 automake.in
--- automake.in 10 Jan 2004 00:24:28 -0000 1.1540
+++ automake.in 15 Jan 2004 16:24:14 -0000
@@ -4509,7 +4509,7 @@ sub scan_autoconf_traces ($)
                AC_CONFIG_LINKS => 1,
                AC_INIT => 0,
                AC_LIBSOURCE => 1,
-               AC_LIBTOOL_TAGS => 1,
+               AC_LIBTOOL_TAGS => 0,
                AC_SUBST => 1,
                AM_AUTOMAKE_VERSION => 1,
                AM_CONDITIONAL => 2,


reply via email to

[Prev in Thread] Current Thread [Next in Thread]