Package: libtool / 2.4.6-2
Metadata
Package | Version | Patches format |
---|---|---|
libtool | 2.4.6-2 | 3.0 (quilt) |
Patch series
view the series filePatch | File delta | Description |
---|---|---|
0001 libtool fix GCC linking with specs.patch | (download) |
build-aux/ltmain.in |
4 3 + 1 - 0 ! |
[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. Signed-off-by: Pavel Raiskup <praiskup@redhat.com> |
0003 libtoolize fix infinite recursion in m4.patch | (download) |
bootstrap |
42 27 + 15 - 0 ! |
[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. Signed-off-by: Pavel Raiskup <praiskup@redhat.com> |
0015 syntax check fix sed syntax errors.patch | (download) |
cfg.mk |
12 6 + 6 - 0 ! |
[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. |
0020 libtool fix GCC clang linking with fsanitize.patch | (download) |
build-aux/ltmain.in |
3 2 + 1 - 0 ! |
[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. Signed-off-by: Jeremy Huddleston Sequoia <jeremyhu@macports.org> Copyright-paperwork-exempt: Yes |
link_all_deplibs.patch | (download) |
build-aux/ltmain.in |
5 4 + 1 - 0 ! |
--- |
deplib_binary.patch | (download) |
build-aux/ltmain.in |
20 10 + 10 - 0 ! |
--- |
netbsdelf.patch | (download) |
m4/libtool.m4 |
20 16 + 4 - 0 ! |
--- |
version_type.patch | (download) |
build-aux/ltmain.in |
3 3 + 0 - 0 ! |
--- |
nopic.patch | (download) |
tests/demo.at |
2 1 + 1 - 0 ! |
--- |
deplibs_test_disable.patch | (download) |
tests/demo.at |
2 2 + 0 - 0 ! |
--- |
disable link order2.patch | (download) |
tests/link-order2.at |
2 2 + 0 - 0 ! |
--- |
deplibs ident.patch | (download) |
tests/deplibs-ident.at |
7 0 + 7 - 0 ! |
--- |
man add whatis info.diff | (download) |
Makefile.am |
4 2 + 2 - 0 ! |
--- |
no_hostname.patch | (download) |
m4/libtool.m4 |
1 0 + 1 - 0 ! |
--- |
bootstrap_options.conf | (download) |
bootstrap.conf |
2 0 + 2 - 0 ! |
--- |
version_string.patch | (download) |
build-aux/ltmain.in |
2 1 + 1 - 0 ! |
--- |