Debian Patches

Status for libtool/2.4.6-15

Patch Description Author Forwarded Bugs Origin Last update
nopic.patch =================================================================== no
0001-libtool-fix-GCC-linking-with-specs.patch [PATCH 01/20] libtool: fix GCC linking with -specs=*
References:
https://bugzilla.redhat.com/show_bug.cgi?id=985592

* build-aux/ltmain.in (func_mode_link): Pass -specs=*
to the linker, Fedora uses this option for hardening.
Pavel Raiskup <praiskup@redhat.com> no 2015-09-18
version_type.patch =================================================================== no
0003-libtoolize-fix-infinite-recursion-in-m4.patch [PATCH 03/20] libtoolize: fix infinite recursion in m4
Some projects use this construct in configure.ac:

m4_define([version], m4_include([version]))
pkg_version=version

When the m4_include builtin is undefined (as was done in
libtoolize and extract-trace scripts), the call to this 'version'
macro enters an infinite recursion (until ENOMEM). So rather
re-define all potentially dangerous macros by empty strings,
suggested by Eric Blake.

While we are on it, merge the macro-"blacklist" with similar list
implemented in gettext, except for 'm4_esyscmd'. It's kept
defined because we already trace AC_INIT macro for package
version, while it is often specified by
m4_esyscmd(git-version-gen). Similarly to m4_include, m4_esyscmd
might be opt-in-blacklisted in future.

References:
http://lists.gnu.org/archive/html/libtool/2015-09/msg00000.html
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764580

* gl/build-aux/extract-trace (_G_mini): Redefine trace-breaking
macros to empty strings rather than undefining those. Use 'dnl'
for comments.
* bootstrap: Likewise, sync with extract-trace.
* NEWS: Document.
* NO-THANKS: Mention Hiroyuki Sato.
Pavel Raiskup <praiskup@redhat.com> no 2015-09-18
0011-libtool-optimizing-options-parser-hooks.patch [PATCH] libtool: optimizing options-parser hooks
Its not necessary to (re)func_quote_for_eval in each function in
the hook hierarchy. Usually it is enough if the leaf function
does func_quote_for_eval and its caller just re-uses the
<CALLEE>_return variable.

This is follow up for the previous commit.

* gl/build-aux/options-parser (func_run_hooks): Propagate
$EXIT_SUCCESS return code down to caller if *any* hook succeeded.
Never re-quote the result -- either the arguments are left
untouched, or the options have already been properly quoted by
succeeding hooks.
(func_parse_options): Quote '$@' and return $EXIT_SUCCESS only if
we changed something.
(func_validate_options): Likewise.
(func_options_prep): Likewise.
(func_options_finish): New hook-caller for 'func_options' hooks.
(func_options): Propagate return value down to top-level caller,
but pay attention we have always set $func_options_result.
* build-aux/ltmain.in (libtool_options_prep): Quote '$@' and
return $EXIT_SUCCESS only if we changed something.
(libtool_parse_options): Likewise.
* bootstrap: Sync gl/build-aux/with option-parser.
Pavel Raiskup <praiskup@redhat.com> no 2015-10-05
0015-syntax-check-fix-sed-syntax-errors.patch [PATCH 15/20] syntax-check: fix sed syntax errors
Multi-line single-quoted shell arguments defined within makefile
rules end up having the trailing backslash. This caused problem
in some sc_* rules as GNU sed does not interpret trailing
backslash the same way as SHELL (== appending next line).
Switching to double quotes means that SHELL will remove the
trailing backslash for subsequent sed call. This silences a lot
of GNU sed warnings seen before like:

sed: -e expression #1, char 96: unterminated address regex

* cfg.mk (sc_libtool_m4_cc_basename): Use $(SED) instead of sed,
use double quotes for sed's multi-line argument.
(sc_prohibit_set_dummy_without_shift): Likewise.
(sc_prohibit_test_const_follows_var): Likewise.
Pavel Raiskup <praiskup@redhat.com> no 2015-10-31
0020-libtool-fix-GCC-clang-linking-with-fsanitize.patch [PATCH 20/20] libtool: fix GCC/clang linking with -fsanitize=*
References:
https://lists.gnu.org/archive/html/libtool/2014-04/msg00026.html

* build-aux/ltmain.in (func_mode_link): Pass -fsanitize=* to the
linker to allow trivial use of the clang address sanitizer.
Jeremy Huddleston Sequoia <jeremyhu@macports.org> no 2015-10-18
link_all_deplibs.patch ## Do not link against deplibs. This is not needed for shared libs
## on atleast ELF systems since those already know which libs they
## need themself. This seems to break a few things and will be fixed
## in a better way in a future upstream version.

===================================================================
no
deplib_binary.patch =================================================================== no
netbsdelf.patch ## Add support for netbsdelf*-gnu

===================================================================
no
deplibs_test_disable.patch ## This test is broken for several reasons:
## - It's linking a shared lib against a static lib. This is not
## portable, and we even give a warning about this.
## - The shared lib is not using any symbols from the static lib.
## - The test program is linked against the shared lib and using
## symbols from the static lib.

===================================================================
no
disable-link-order2.patch =================================================================== no
deplibs-ident.patch =================================================================== no
man-add-whatis-info.diff =================================================================== no
no_hostname.patch =================================================================== no
bootstrap_options.conf =================================================================== no
version_string.patch =================================================================== no
grep-spaces.patch Add spaces before -L in Grep searches Current searching for "-L" in link paths is over-greedy and incorrectly handles paths with -L in them
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896861 for example

===================================================================
Alastair McKinstry <mckinstry@debian.org> no
libtool-eval-nm.patch Avoid a broken AC_TRY_EVAL macro As said in the Autoconf source, the AC_TRY_EVAL macro is dangerous and
undocumented, and should not be used.
In particular, the one related to nm yields binary data in the config.log
file with dash, where "echo \\1" (echo with the argument \1) produces the
control character ^A instead of the usual \1 with most shells (POSIX says
that the result is implementation-defined). See:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910076
This patch attempts to replace this AC_TRY_EVAL occurrence by code with
similar behavior, but using $ECHO instead of echo in order to avoid the
backslash issue.

===================================================================
Vincent Lefevre <vincent@vinc17.net> no
libtool-2.4.6-am-1.16-test.patch Ensure that $(LIBLTDL) is built first

After Automake upstream commit f4e91bfc490d, the list in 'all-am:' is
reordered for this test-case (*_LTLIBRARIES is before *_PROGRAMS), which
means that linker will fail to link 'old' binary.

Previously (with automake <= 1.16), it was matter of luck -- it worked if
(a) the build was serial (-j1), and/or (b) libtool-ltdl-devel package was
installed on the box so ./configure picked the system version of libltdl.

Users should anyways use system's ltdl, so this has low priority.

diff --git a/tests/old-ltdl-iface.at b/tests/old-ltdl-iface.at
index cee29089..6f9c8001 100644
no
0025-libtool-pass-use-ld.patch libtool: pass through -fuse-ld flags Starting with gcc-4.8, there's a -fuse-ld flag that can be used to
select between bfd & gold. Make sure we pass it through to the
linking stage.

* build-aux/ltmain.in (func_mode_link): Pass -fuse-ld=* flags
through.

===================================================================
Mike Frysinger <vapier@gentoo.org> not-needed debian http://git.savannah.gnu.org/cgit/libtool.git/commit/?id=f9970d99293faf908fdc153a653fa5781095fb7a
0030-flang-support.patch Support for Flang Fortran compiler
===================================================================
Alastair McKinstry <mckinstry@debian.org> no
0035-ac-prereq.patch Increment PREREQ needed for gnulib
===================================================================
Alastair McKinstry <mckinstry@debian.org> no
0040-unsafe-eval.patch minor removal of unsafe shell script eval in these segements unnecessary

===================================================================
Alastair McKinstry <mckinstry@debian.org> no
0050-documentation.patch documentation inconsitent with libltdl3
===================================================================
Alastair McKinstry <mckinstry@debian.org> no
0055-pass-flags-unchanged.patch Pass more flags to the linker unchanged. Closes: #751161. Vincent Lefevre <vincent@vinc17.net> no
0060-ar.patch Change default AR flags to 'cr' to silence warning over default 'D' overriding 'u'

===================================================================
Alastair McKinstry <mckinstry@debian.org> no https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864018
0065-autoconf-version.patch Updated dependency needed for Gnulib
===================================================================
Alastair McKinstry <mckinstry@debian.org> no debian
0070-libtool-bigsur.patch libtool support for MacOS BigSur
===================================================================
Alastair McKinstry <mckinstry@debian.org> not-needed
0075-remove-dates-from-docs.patch Patch to remove dates from .info and .html documentation Vagrant Cascadian <vagrant@reproducible-builds.org> no 2020-02-10
0080-struct-names.patch Fix for incorrect struct docs in texi
===================================================================
Hans Ulrich Niedermann. no debian

All known versions for source package 'libtool'

Links