Created attachment 493630 [details] build.log see build.log
Thank you for the report. Please *attach* the --info, https://wiki.gentoo.org/wiki/Bugzilla/Bug_report_guide#Report_a_build-time_bug_.28emerge_failed.29
Created attachment 494082 [details] emerge --info
i was not able to build it with USE=latex, thinking it was related to that other bug that's currenly open for 1.6.3
* Package: dev-python/sphinx-1.6.3-r2 * Repository: gentoo * Maintainer: python@gentoo.org * USE: abi_x86_64 amd64 elibc_glibc kernel_linux python_targets_python2_7 python_targets_python3_6 userland_GNU * FEATURES: preserve-libs sandbox userpriv usersandbox * Applying sphinx-1.5.1-fix-pycode-grammar.patch ... [ ok ] * python2_7: running distutils-r1_run_phase python_compile /usr/bin/python2.7 setup.py build error in Sphinx setup command: Invalid environment marker: python_version<"3.5" * ERROR: dev-python/sphinx-1.6.3-r2::gentoo failed (compile phase): * (no error message) * * Call stack: * ebuild.sh, line 124: Called src_compile * environment, line 3958: Called distutils-r1_src_compile * environment, line 1023: Called _distutils-r1_run_foreach_impl 'python_compile' * environment, line 366: Called python_foreach_impl 'distutils-r1_run_phase' 'python_compile' * environment, line 3451: Called multibuild_foreach_variant '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'python_compile' * environment, line 2526: Called _multibuild_run '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'python_compile' * environment, line 2524: Called _python_multibuild_wrapper 'distutils-r1_run_phase' 'python_compile' * environment, line 664: Called distutils-r1_run_phase 'python_compile' * environment, line 1016: Called python_compile * environment, line 3029: Called distutils-r1_python_compile * environment, line 891: Called esetup.py 'build' * environment, line 1576: Called die * The specific snippet of code: * "${@}" || die "${die_args[@]}"; * * If you need support, post the output of `emerge --info '=dev-python/sphinx-1.6.3-r2::gentoo'`, * the complete build log and the output of `emerge -pqv '=dev-python/sphinx-1.6.3-r2::gentoo'`. * The complete build log is located at '/tmp/.portage/dev-python:sphinx-1.6.3-r2:20171028-150507.log'. * For convenience, a symlink to the build log is located at '/tmp/.portage/portage/dev-python/sphinx-1.6.3-r2/temp/build.log'. * The ebuild environment file is located at '/tmp/.portage/portage/dev-python/sphinx-1.6.3-r2/temp/environment'. * Working directory: '/tmp/.portage/portage/dev-python/sphinx-1.6.3-r2/work/Sphinx-1.6.3' * S: '/tmp/.portage/portage/dev-python/sphinx-1.6.3-r2/work/Sphinx-1.6.3'
*** This bug has been marked as a duplicate of bug 635310 ***
This bug solved itself when it updated, there was no lingering sphinx*egg file like in the duplicate bug where there was an old cryptography*egg. But regardless, removing the old egg fixed the bug. Is there a portage tool to scan for old files like this ? Not just .egg , but also ebuilds? I a similar problem with layman having left an old ebuild.
