Created attachment 387410 [details] dev-libs:libxml2-2.9.1-r4:20141026-032847.log I think the libxml2_py_emake call fails because python_foreach_impl fails to copy some files. That is, the build environment is not set up entirelly as expected by the upstream(?) compile script. From what I can tell, the built script dies after the first folder in the following list: libxml2-2.9.1 libxml2-2.9.1-abi_x86_32.x86 libxml2-2.9.1-abi_x86_64.amd64 libxml2-2.9.1-abi_x86_64.amd64-python2_7 libxml2-2.9.1-abi_x86_64.amd64-python3_3 $ ebuild /usr/portage/dev-libs/libxml2/libxml2-2.9.1-r4.ebuild compile (...) * python3_3: running libxml2_py_emake top_builddir=/var/tmp/portage/dev-libs/libxml2-2.9.1-r4/work/libxml2-2.9.1-abi_x86_64.amd64 all /var/tmp/portage/dev-libs/libxml2-2.9.1-r4/temp/environment: line 2658: pushd: /var/tmp/portage/dev-libs/libxml2-2.9.1-r4/work/libxml2-2.9.1-abi_x86_64.amd64-python3_3/python: No such file or directory * ERROR: dev-libs/libxml2-2.9.1-r4::gentoo failed (compile phase): * (no error message) * * Call stack: * ebuild.sh, line 93: Called src_compile * environment, line 4710: Called multilib-minimal_src_compile * environment, line 3182: Called multilib_foreach_abi 'multilib-minimal_abi_src_compile' * environment, line 3406: Called multibuild_foreach_variant '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_compile' * environment, line 3023: Called _multibuild_run '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_compile' * environment, line 3021: Called _multilib_multibuild_wrapper 'multilib-minimal_abi_src_compile' * environment, line 655: Called multilib-minimal_abi_src_compile * environment, line 3176: Called multilib_src_compile * environment, line 3624: Called python_foreach_impl 'libxml2_py_emake' 'top_builddir=/var/tmp/portage/dev-libs/libxml2-2.9.1-r4/work/libxml2-2.9.1-abi_x86_64.amd64' 'all' * environment, line 4297: Called multibuild_foreach_variant '_python_multibuild_wrapper' 'libxml2_py_emake' 'top_builddir=/var/tmp/portage/dev-libs/libxml2-2.9.1-r4/work/libxml2-2.9.1-abi_x86_64.amd64' 'all' * environment, line 3023: Called _multibuild_run '_python_multibuild_wrapper' 'libxml2_py_emake' 'top_builddir=/var/tmp/portage/dev-libs/libxml2-2.9.1-r4/work/libxml2-2.9.1-abi_x86_64.amd64' 'all' * environment, line 3021: Called _python_multibuild_wrapper 'libxml2_py_emake' 'top_builddir=/var/tmp/portage/dev-libs/libxml2-2.9.1-r4/work/libxml2-2.9.1-abi_x86_64.amd64' 'all' * environment, line 901: Called libxml2_py_emake 'top_builddir=/var/tmp/portage/dev-libs/libxml2-2.9.1-r4/work/libxml2-2.9.1-abi_x86_64.amd64' 'all' * environment, line 2658: Called die * The specific snippet of code: * pushd "${BUILD_DIR}/python" > /dev/null || die;
Created attachment 387412 [details] emerge info
It seems I was able to dodge this because the error happens only when the library is built with the python USE flag. The only dependency on dev-libs/libxml2[python] in this system was by "itstool" and in turn app-text/yelp-tools and gnome-extra/yelp-xsl, leading do libgnome-keyring and potentially sys-auth/pambase. Luckilly, I don't have any use for gnome-keyring-daemon. Actually, it seems that only "gnome things" need dev-libs/libxml2[python], but I'm not sure how accurate that is.
Except for the parallel version of python build, I do not see a difference between 2.9.1-r4 ebuild and 2.9.2 revisions. Are you still hitting this issue ?
