IssueTracker

abargher@ noticed that get_libdir always returned lib instead of the necessary lib64 even when installing to an amd64 device. After thorough debugging, we found out that setup_cross_toolchain unsets the ABI global, and never resets it.

Specifically, in 2017, we added a CL to unset ABI: crrev/c/509148 for cross-compiled toolchain packages.

In the past, with EAPI=5 and earlier, this worked fine because setup_cross_toolchain set DEFAULT_ABI through the multilib.eclass's multilib_env, and multilib defined its own get_libdir which used DEFAULT_ABI.

However, with EAPI=6 and later, our Portage itself defines its own get_libdir in phase-helpers.sh, and this implementation does NOT care about DEFAULT_ABI: it only uses ABI. When the given ABI is unset, get_libdir silently defaults to lib incorrectly.

Because setup_cross_toolchain undef's ABI, this has been broken since our move to EAPI=6 and later.

I spoke to manojgupta@ about the original intent, and we agreed this is probably a real bug.

We use get_libdir in a few toolchain packages. Re-evaluate their usage, and maybe update setup_cross_toolchains to ensure it's no longer doing the wrong thing.