gcc treats --enable-libvtv as an override on top of
autodetection. It it never what we want. Happens to break
at least powerpc64 cross-compilers:
https://bugs.gentoo.org/661252
Reported-by: Ilia Mirkin
Closes: https://bugs.gentoo.org/661252
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
if in_iuse vtv ; then
confgcc+=(
$(use_enable vtv vtable-verify)
- $(use_enable vtv libvtv)
+ # See Note [implicitly enabled flags]
+ $(usex vtv '' --disable-libvtv)
)
fi
#
# GCC does not follow this pattern and instead overrides autodetection
# of the feature and enables it unconditionally.
-# See https://gcc.gnu.org/PR85663
+# See bugs:
+# https://gcc.gnu.org/PR85663 (libsanitizer on mips)
+# https://bugs.gentoo.org/661252 (libvtv on powerpc64)
#
# Thus safer way to enable/disable the feature is to rely on implicit
# enabled-by-default state: