summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSergei Trofimovich <slyfox@gentoo.org>2020-06-19 19:15:21 +0100
committerSergei Trofimovich <slyfox@gentoo.org>2020-06-19 21:52:43 +0100
commit92e383747ffc633ff6e85a02bf8cdb856eb1bcdc (patch)
tree56e3a5747be4479254f44e7e932eab6604e47c78 /dev-lua
parentmail-client/neomutt: Version bump to 2020-06-19 (diff)
downloadgentoo-92e383747ffc633ff6e85a02bf8cdb856eb1bcdc.tar.gz
gentoo-92e383747ffc633ff6e85a02bf8cdb856eb1bcdc.tar.bz2
gentoo-92e383747ffc633ff6e85a02bf8cdb856eb1bcdc.zip
toolchain.eclass: drop fix_libtool_files.sh
fixlafiles.awk can mangle two things in .la fils: 1. patch reference 'from .../libstdc++.la' to '-lstdc++' 2. change ${CHOST} when user switches CHOST and rebuilds the system [1.] is not relevant since gcc-4 in Gentoo where we started deleting libstdc++.la on gcc installation. Nothing should embed libstdc++.la paths anymore. [2.] is a rare one-off step that has a lot more caveats than just .la file patching. Generally .la files are tracked by package manager and should not be changed after they are installed on disk. 'fix_libtool_files.sh' breaks that invariant. On top of that portage's FEATURES=fixlafiles removes nested .la files references. Let's remove 'fix_libtool_files.sh' and 'fixlafiles.awk' completely. If really needed we can reintroduce it as a separate tool. Closes: https://bugs.gentoo.org/722554 Closes: https://bugs.gentoo.org/657330 Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
Diffstat (limited to 'dev-lua')
0 files changed, 0 insertions, 0 deletions