Am Wed, 7 May 2008 19:23:09 -0400 (EDT) schrieb Eric Belanger <belanger@ASTRO.UMontreal.CA>:
On Thu, 8 May 2008, Andreas Radke wrote:
hm. no signoffs?
libtool 2.2.4 is out.
2.2.4-1 is in testing. New in 2.2.4: 2008-05-04: CVS version 2.2.3a, Libtool team: * New features: - New libtoolize option --no-warn, for users that want to continue to use old libtool style without being nagged. - Options --debug, --no-warn, --quiet and --verbose can be passed to libtoolize through the environment variable LIBTOOLIZE_OPTIONS, for cleaner interaction between the user and libtoolize when called by autoreconf. * Bug fixes: - The documentation for lt_dlopenadvise showed the wrong type for the lt_dladvise parameter. - The public declarations for lt_dlhandle and lt_dladvise are now incomplete struct types rather than void*, which means that nearly all casting is eliminated allowing the compiler to provide more type checking. - libtoolize no longer reports up-to-date files that it would have copied, unless --force is passed. - No longer reports that lt~obsolete.m4 needs to be added to aclocal.m4 when it is already there. - When `aclocal' copied the libtool macros directly into `aclocal.m4' (i.e. AC_CONFIG_MACRO_DIR is not being used), libtoolize no longer reports that all macros need to be added to `aclocal.m4', and diagnoses only the macro files that are missing or not up-to-date. - libtoolize now advises use of AC_CONFIG_MACRO_DIR to keep matching libtool macros in-tree where appropriate. - libtoolize now advises use of `ACLOCAL_AMFLAGS = -I m4' (or equivalent) where appropriate, and errors out when ACLOCAL_AMFLAGS names a different directory to AC_CONFIG_MACRO_DIR. please signoff. -Andy