summaryrefslogtreecommitdiffstats
path: root/lib/libalpm
diff options
context:
space:
mode:
authorAllan McRae <allan@archlinux.org>2020-01-16 12:20:19 +0100
committerAllan McRae <allan@archlinux.org>2020-01-27 08:53:50 +0100
commit2e32d51a262fef398a94a17c0a0d4ff3233990b5 (patch)
tree12e7ee2c812ac1662f80bad411779e3f4ae79438 /lib/libalpm
parent75bf8e887cd9fe0f6ba1eb2b6554dbfbcda0294a (diff)
downloadpacman-2e32d51a262fef398a94a17c0a0d4ff3233990b5.tar.gz
pacman-2e32d51a262fef398a94a17c0a0d4ff3233990b5.tar.xz
Remove unneeded ltmain patch
Many moons ago, libtool was bad - I mean worse than today! It gobbled all --as-needed and we ended up with an overlinked libalpm. This was annoying, particularly when dealing with soname bumps in libraries pacman/libalpm had no business linking to. Luckily we had a fix, stolen from GNOME I believe. And with that fix, we lived in harmony with libtool for many years. Until one day, unbeknownst to us, libtool was "fixed". We kept applying our patch, because it still applied, but it did worse than nothing. It gobbled up our other LDFLAGS, and our libalpm started missing out on RELRO and BIND_NOW. This made the Arch Security Team unhappy. We will make them happy again by stopping the patch. Signed-off-by: Allan McRae <allan@archlinux.org>
Diffstat (limited to 'lib/libalpm')
0 files changed, 0 insertions, 0 deletions