bug-libtool
[Top][All Lists]
Advanced

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

Re: FYI: adjust automake test suite for CVS libtoolize


From: Alexandre Duret-Lutz
Subject: Re: FYI: adjust automake test suite for CVS libtoolize
Date: Mon, 05 Jan 2004 01:08:34 +0100
User-agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (gnu/linux)

>>> "Gary" == Gary V Vaughan <address@hidden> writes:

 Gary> Hi Alexandre!
 Gary> On Friday, January 2, 2004, at 07:25  pm, Alexandre Duret-Lutz wrote:
 >> The new default behavior of CVS libtoolize is to not install
 >> config.sub and config.guess (contrary to what libtoolize 1.5
 >> did).  This breaks four tests in our test suite.

 Gary> Indeed... Sorry about that.  Ironically, it was for consistency with
 Gary> automake that I make that change :-/

No problem, I just meant to report it in case it was not
intentional.  Maybe you could NEWS this?  It can potentially
break some autogen.sh scripts.

Another new behavior is that libtoolize complains when
aclocal.m4 does not exist.

~/projs/cvs/automake/HEAD3/tests % ./libtool5.test
[...]
=== Running test ./libtool5.test
++ pwd
/home/adl/projs/cvs/automake/HEAD3/tests/testSubDir
+ set -e
+ cat
+ cat
+ libtoolize
cat: aclocal.m4: No such file or directory
libtoolize: copying file `./ltmain.sh'
libtoolize: copying file `./libtool.m4'
[...]

This one looks rather like a bug.

 >> @@ -46,4 +46,4 @@
 >> 
 >> libtoolize
 >> $ACLOCAL
 >> -$AUTOMAKE
 >> +$AUTOMAKE --add-missing

 Gary> wouldn't calling "libtoolize --force" be more consistent?

Either way seems fine.  Some other test cases already use
--force, and I presume it's not a bad idea to test more that one
way...
-- 
Alexandre Duret-Lutz





reply via email to

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