creating /var/tmp/portage/dev-python/python-efl-1.18.0/work/python-efl-1.18.0-python2_7/temp.linux-x86_64-2.7/efl/eo x86_64-pc-linux-gnu-gcc -O2 -pipe -march=native -fPIC -DEFL_BETA_API_SUPPORT=1 -DEFL_EO_API_SUPPORT=1 -Iinclude/ -I/usr/include/python2.7 -c efl/eo/efl.eo.c -o /var/tmp/portage/dev-python/python-efl-1.18.0/work/python-efl-1.18.0-python2_7/temp.linux-x86_64-2.7/efl/eo/efl.eo.o -I/usr/include/eina-1/eina -I/usr/include/efl-1 -I/usr/include/eina-1 -I/usr/include/eo-1 efl/eo/efl.eo.c:1088:55: error: unknown type name ‘Eo_Event’; did you mean ‘Efl_Event’? static void __pyx_f_3efl_2eo__eo_event_del_cb(void *, Eo_Event const *); /*proto*/ ^~~~~~~~ Efl_Event ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-no-multilib-hardened_libressl_20180403-174803 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.0 * Available Python interpreters, in order of preference: [1] python3.5 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby22 (with Rubygems) [2] ruby23 (with Rubygems) * emerge -qpv dev-python/python-efl [ebuild N ] dev-python/python-efl-1.18.0 USE="-doc -examples" PYTHON_TARGETS="python2_7 python3_5 -python3_4 -python3_6"
Created attachment 527052 [details] emerge-info.txt
Created attachment 527054 [details] dev-python:python-efl-1.18.0:20180410-050829.log
Created attachment 527056 [details] emerge-history.txt
Created attachment 527058 [details] environment
Created attachment 527060 [details] etc.portage.tbz2
Created attachment 527062 [details] temp.tbz2
Okay. I believe this is either because you seem to have installed dev-libs/efl without X use flag, or because of mismatched versions between dev-libs/efl and dev-python/python-efl. (1.18 <=> 1.20) The X requirement is not documented upstream and I personally have efl installed with X enabled. But I see a clear warning about ecore-X missing. I will try to reproduce this and fix either by adding missing USE requirement for efl, or by making efl-1.18* requirement for this. Thanks for the report!
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=69d0f62b6762d8469f94d827408666b37e08b8de commit 69d0f62b6762d8469f94d827408666b37e08b8de Author: Joonas Niilola <juippis@gmail.com> AuthorDate: 2018-07-07 11:13:44 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2018-07-07 13:53:50 +0000 dev-python/python-efl: 1.18.0-r1 depends on =dev-libs/efl-1.18* Closes: https://bugs.gentoo.org/652924 Package-Manager: Portage[mgorny]-2.3.36.1 dev-python/python-efl/python-efl-1.18.0-r1.ebuild | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 deletions(-)
