The gevent 1.3.7 and 1.4.0 fails to cross compile. This is for two primary reasons: 1. The includes that are are pulled in for compiling accidentally reference the host system's /usr/include/python2.7. This causes a violation. 2. Even though we specify that we don't want to use the embedded libev library, the setup.py still wants to build the embedded libev library. The issues is that the build script does not inform ./configure that we are doing a cross compile.
The proposed solution: https://github.com/linux4life798/gentoo/commit/3bf7986f8fc1e19ecfc57800858d3f67d98dd707
I submitted a PR at https://github.com/gentoo/gentoo/pull/14491 .
Please submit patches to the upstream projects. We try not to carry patches downstream long-term where it is avoidable. gevent-1.4.0-cross-compile-libev.patch looks Gentoo-specific with its references to CBUILD and CHOST. Could you come up with a solution that might be accepted upstream?
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8710aa0a9078053187c690a48117ea820fc91f5c commit 8710aa0a9078053187c690a48117ea820fc91f5c Author: Jakov Smolić <jsmolic@gentoo.org> AuthorDate: 2022-12-20 14:01:35 +0000 Commit: Jakov Smolić <jsmolic@gentoo.org> CommitDate: 2022-12-20 14:25:38 +0000 dev-python/gevent: treeclean Closes: https://bugs.gentoo.org/879011 Closes: https://bugs.gentoo.org/849350 Closes: https://bugs.gentoo.org/834795 Closes: https://bugs.gentoo.org/807628 Closes: https://bugs.gentoo.org/707024 Signed-off-by: Jakov Smolić <jsmolic@gentoo.org> dev-python/gevent/Manifest | 2 - dev-python/gevent/gevent-21.12.0-r1.ebuild | 102 ----------------------------- dev-python/gevent/gevent-22.10.1-r1.ebuild | 99 ---------------------------- dev-python/gevent/metadata.xml | 12 ---- profiles/package.mask | 9 --- 5 files changed, 224 deletions(-)
