glib fails the test phase because it cannot PaX mark the executable assert-msg-test: --- >>> Source compiled. >>> Test phase: dev-libs/glib-2.56.4 * abi_x86_64.amd64: running multilib-minimal_abi_src_test * XATTR_PAX marking -mr /var/tmp/portage/dev-libs/glib-2.56.4/work/glib-2.56.4-abi_x86_64.amd64/tests/.libs/assert-msg-test with paxctl-ng * XATTR_PAX marking -mre /var/tmp/portage/dev-libs/glib-2.56.4/work/glib-2.56.4-abi_x86_64.amd64/tests/.libs/assert-msg-test with setfattr * Failed to set XATTR_PAX markings -mre /var/tmp/portage/dev-libs/glib-2.56.4/work/glib-2.56.4-abi_x86_64.amd64/tests/.libs/assert-msg-test. * ERROR: dev-libs/glib-2.56.4::gentoo failed (test phase): * Hardened adjustment failed * * Call stack: * ebuild.sh, line 124: Called src_test * environment, line 5797: Called multilib-minimal_src_test * environment, line 3985: Called multilib_foreach_abi 'multilib-minimal_abi_src_test' * environment, line 4158: Called multibuild_foreach_variant '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_test' * environment, line 3850: Called _multibuild_run '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_test' * environment, line 3848: Called _multilib_multibuild_wrapper 'multilib-minimal_abi_src_test' * environment, line 645: Called multilib-minimal_abi_src_test * environment, line 3979: Called multilib_src_test * environment, line 4439: Called die * The specific snippet of code: * pax-mark -mr "${BUILD_DIR}"/tests/.libs/assert-msg-test || die "Hardened adjustment failed"; --- The ebuild code is (shortend): --- multilib_src_test() { # ... if host-is-pax ; then pax-mark -mr "${BUILD_DIR}"/tests/.libs/assert-msg-test || die "Hardened adjustment failed" fi virtx emake check } --- The reason for the failure is that the executable assert-msg-test is build by 'make check' and thus is not present at the pax-mark call. A simple solution is to build the executable before the pax-mark call by adding emake -C tests assert-msg-test before the pax-mark call.
I've removed all pax handling in glib-2.60.6 bump.
*** Bug 616358 has been marked as a duplicate of this bug. ***
