pool/libtool
SHA256
2
0
Fork 1
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

- Update to libtool 2.4.3

Browse Source 
** New features:
 - Moved to gnulib release infrastructure.
 - M4 is now used for scanning the M4 macros in your configure.ac that
  'libtoolize' looks at to determine what files you want, and where you
   would like them installed.  This means that you can compose your
   version number or any other argument that Libtoolize needs to know at
   M4 time using git-version-gen from gnulib, for example.
 - Invoking 'libtoolize --ltdl' no longer maintains a separate autoconf
   macro directory in the libltdl tree, but automatically adjusts the
   installed libltdl configuration files to share whatever macro
   directory is declared by the parent project. (Note: if you were
   already sharing a macro directory with AC_CONFIG_MACRO_DIR(ltdl/m4)
   or similar, that still works as does any other directory choice).
 - Invoking 'libtoolize --ltdl' no longer maintains a separate auxiliary
   scripts directory in the libltdl tree, but automatically adjusts the
   installed libltdl configuration files to share whatever auxiliary
   scripts directory is declared by the parent project. (Note: if you
   were already sharing an auxiliary directory with subproject libltdl
   using AC_CONFIG_AUX_DIR(ltdl/config) or similar, that still works as
   does any other directory choice).
 - The legacy tests have all been migrated to the Autotest harness.
 - The Autotest testsuite can be run without the especially time consuming
   tests with:
       make check-local TESTSUITEFLAGS='-k "!expensive"'
** Bug fixes:
 - Fix a long-standing latent bug in autom4te include path for autotests
   with VPATH builds.
 - Fix a long-standing latent bug in libtoolize that could delete lines
   from libltdl/Makefile.am in recursive mode due to underquoting in a

OBS-URL: https://build.opensuse.org/package/show/Base:System/libtool?expand=0&rev=60
This commit is contained in:
Marcus Meissner 2014-11-04 06:31:25 +00:00 committed by Git OBS Bridge
parent 9eb63396df
commit 4dd758a7f1
1 changed files with 114 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

116
libtool-testsuite.changes
View File

@ -1,11 +1,123 @@
-------------------------------------------------------------------
Mon Nov 3 22:37:34 UTC 2014 - foss@grueninger.de
Mon Nov 3 22:35:18 UTC 2014 - foss@grueninger.de
- Update to libtool 2.4.3
- Drop patch config-guess-sub-update.patch for libltdl/config as the
folder no longer exists.
- Drop patch libtool-ppc64le.patch for ppc handling as it is already
part of v2.4.3
- Update to libtool 2.4.3
** New features:
- Moved to gnulib release infrastructure.
- M4 is now used for scanning the M4 macros in your configure.ac that
'libtoolize' looks at to determine what files you want, and where you
would like them installed. This means that you can compose your
version number or any other argument that Libtoolize needs to know at
M4 time using git-version-gen from gnulib, for example.
- Invoking 'libtoolize --ltdl' no longer maintains a separate autoconf
macro directory in the libltdl tree, but automatically adjusts the
installed libltdl configuration files to share whatever macro
directory is declared by the parent project. (Note: if you were
already sharing a macro directory with AC_CONFIG_MACRO_DIR(ltdl/m4)
or similar, that still works as does any other directory choice).
- Invoking 'libtoolize --ltdl' no longer maintains a separate auxiliary
scripts directory in the libltdl tree, but automatically adjusts the
installed libltdl configuration files to share whatever auxiliary
scripts directory is declared by the parent project. (Note: if you
were already sharing an auxiliary directory with subproject libltdl
using AC_CONFIG_AUX_DIR(ltdl/config) or similar, that still works as
does any other directory choice).
- The legacy tests have all been migrated to the Autotest harness.
- The Autotest testsuite can be run without the especially time consuming
tests with:
make check-local TESTSUITEFLAGS='-k "!expensive"'
** Bug fixes:
- Fix a long-standing latent bug in autom4te include path for autotests
with VPATH builds.
- Fix a long-standing latent bug in libtoolize that could delete lines
from libltdl/Makefile.am in recursive mode due to underquoting in a
sed script.
- Fix a long-standing bug in libtoolize, by outputting the 'putting
auxiliary files in' header with 'libtoolize --ltdl --subproject'.
- Fix a long-standing bug in libtoolize subproject installation, by not
installing a set of autoconf macro files into the parent project if
there is no configure.ac present to use them.
- The libtoolize subproject mode selector is now named '--subproject'
and is equivalent to the implied '--subproject' mode when no other
mode is selected; '--standalone' never worked, and is no longer
accepted.
- Libtool and libtoolize no longer choke on paths with a comma in them.
- In the case where $SHELL does not have the same enhanced features
(e.g. the ability to parse 'var+=append') as $CONFIG_SHELL, libtool
will now correctly fallback to using only vanilla shell features
instead of failing with a parse at startup.
- Correctly recognize import libraries when Microsoft dumpbin is used
as the name lister and extend the dumpbin wrapper to find symbols
in import libraries using the -headers option of dumpbin. Also fix a
bug in the dumpbin wrapper that could lead to broken symbol listings
in some corner cases.
- Use the improved Microsoft dumpbin support to mend preloading of
import libraries for Microsoft Visual C/C++.
- No longer mangle module-definition (.def) files when feeding them to
the Microsoft Visual C/C++ linker via the -export-symbols argument to
the libtool script, thus matching how .def files are handled when
using GNU tools.
- Recognize more variants (e.g. those starting with a LIBRARY statement)
of module-definitions (.def) files when using them instead of a raw
list of symbols to export.
- Fix a long-standing bug when using libtoolize without automake; we
no longer remove install-sh with --force, since it's not a file
libtoolize will reinstall without --install..
** Important incompatible changes:
- GNU M4 is required to run libtoolize in a directory with a
'configure.ac' (or 'configure.in') that needs tracing to determine
what modes and directories have been specified.
- The use of the idiosyncratically named 'Makefile.inc' in nonrecursive
libltdl builds is deprecated, although it will be supported for one
more year or until the next release, whichever takes longer. Please
upgrade to the more standard naming of 'ltdl.mk' in keeping with other
GNU projects.
- libtoolize now behaves consistenty in respect of multiple directory
arguments to ACLOCAL_AMFLAGS and multiple invocations of AC_CONFIG-
_MACRO_DIRS, where the first directory is always selected. Previous
releases took the first ACLOCAL_AMFLAGS argument, but the last
invocation of AC_CONFIG_MACRO_DIRS.
- The libtoolize program now advises use of the new Autoconf
AC_CONFIG_MACRO_DIRS declaration. If you follow that advice, all
your developers will need at least autoconf-2.70 and automake-1.13
to rebootstrap your probject. If you still need to support
bootstrap with older Autotools, then you should add the following
to your configure.ac file:
m4_ifndef([AC_CONFIG_MACRO_DIRS],
[m4_define([AC_CONFIG_MACRO_DIRS],
m4_defn([AC_CONFIG_MACRO_DIR]))])
- Overhead of probing for a non-backslash crippled echo equivalent
during initialization of every script has been removed in favor of
trusting that "printf %s\n" works out of the box on all non-museum
host architectures. Manually setting ECHO appropriately in the
build environment will be necessary on some ancient architectures.
** Changes in supported systems or compilers:
- Support for bitrig (*-*-bitrig*).
- Solaris 7 and earlier requires ECHO=/usr/ucb/echo in the build
environment, to build and use libtool.
-------------------------------------------------------------------
Tue Sep 9 03:55:16 UTC 2014 - coolo@suse.com