Summary: | dev-lang/lua: uses system-wide libtool rather than generating local copy (needed to cross-compile) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michał Górny <mgorny> |
Component: | Current packages | Assignee: | William Hubbs <williamh> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | leho, sam, vapier |
Priority: | Normal | Keywords: | PullRequest |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=791451 https://bugs.gentoo.org/show_bug.cgi?id=739764 https://github.com/gentoo/gentoo/pull/24018 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Build log |
Well, as we now continue to ship slot :5.1, I'll look into using configure.in for this one, too (notice how lua-5.2 already generates it's own libtool files). lua-5.2 also runs /usr/bin/libtool The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3f0c95ca346af106169ceef830e4e0ae5ea3eed2 commit 3f0c95ca346af106169ceef830e4e0ae5ea3eed2 Author: Alexandra Parker <alex.iris.parker@gmail.com> AuthorDate: 2022-01-31 03:01:47 +0000 Commit: William Hubbs <williamh@gentoo.org> CommitDate: 2022-02-14 07:33:58 +0000 dev-lang/lua:5.1.5-r107 5.3.6-r3 bump - Cross-compile fix, use libtol on the target system and move libtool to DEPEND instead of BDEPEND. Closes: https://bugs.gentoo.org/515554 Closes: https://bugs.gentoo.org/739764 Closes: https://github.com/gentoo/gentoo/pull/24018 Package-Manager: Portage-3.0.30, Repoman-3.0.3 Signed-off-by: Alexandra Parker <alex.iris.parker@gmail.com> Signed-off-by: William Hubbs <williamh@gentoo.org> dev-lang/lua/lua-5.1.5-r107.ebuild | 157 ++++++++++++++++++++++++++++ dev-lang/lua/lua-5.3.6-r3.ebuild | 206 +++++++++++++++++++++++++++++++++++++ 2 files changed, 363 insertions(+) |
Created attachment 379804 [details] Build log Long story short, /usr/bin/libtool uses whatever random CC/CXX was used when libtool was last installed. So, using system-wide libtool means mixing CC/CXX used when building the package with CC/CXX used when building libtool, with the latter likely no longer installed. Solution: only possible I know is to use autotools macros to have proper local libtool suited for currently used CC/CXX. Or not use libtool at all.