In other words, enable wrapping for non-multilib systems as well. While
this isn't necessary, it shouldn't hurt and it improves consistency
between systems. As a result, ebuilds can now safely use
'${CHOST}-executable' calls without checking whether the system is
multilib.
---
eclass/multilib-build.eclass | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/eclass/multilib-build.eclass b/eclass/multilib-build.eclass
index 02f9634..4b6a953 100644
--- a/eclass/multilib-build.eclass
+++ b/eclass/multilib-build.eclass
@@ -295,7 +295,7 @@ multilib_prepare_wrappers() {
[[ ${#} -le 1 ]] || die "${FUNCNAME}: too many arguments"
- [[ ${#MULTIBUILD_VARIANTS[@]} -le 1 ]] && return
+ [[ ${COMPLETE_MULTILIB} == yes ]] && return
local root=${1:-${ED}}
local f
@@ -421,7 +421,7 @@ multilib_install_wrappers() {
[[ ${#} -le 1 ]] || die "${FUNCNAME}: too many arguments"
- [[ ${#MULTIBUILD_VARIANTS[@]} -le 1 ]] && return
+ [[ ${COMPLETE_MULTILIB} == yes ]] && return
local root=${1:-${ED}}
--
1.9.2
