On Thu, 2004-02-05 at 03:40, name wrote: > Why doesn't installation copy libtool.m4 to aclocal? > Assuming you are talking about CVS HEAD (libtool 1.5a, future 1.6 release) this is because libtoolize now copies libtool.m4 from its own data directory into your macro directory.
"Your macro directory" is a directory in your source to hold macro files that would've gone into aclocal.m4. Call it something like 'm4' and specify it with 'AC_CONFIG_MACRO_DIR([m4])' in your configure.ac and add 'ACLOCAL_AMFLAGS = -I m4' in your top-level Makefile.am. (If you don't do this, your top-level source directory will simply be used instead.) This is consistent with "The Future of `aclocal'" as outlined in the Automake manual chapter of the same title. The great advantage of this is that it ensures that libtool.m4 and ltmain.sh are matched versions, running libtoolize and forgetting to run aclocal, or the reverse, used to be the source of many developer's woes in the past. Scott -- Have you ever, ever felt like this? Had strange things happen? Are you going round the twist?
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
