File "<string>", line 1, in <module> ModuleNotFoundError: No module named 'sip' CMake Error at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:137 (message): Could NOT find SIP (missing: SIP_INCLUDE_DIRS) Call Stack (most recent call first): /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:378 (_FPHSA_FAILURE_MESSAGE) ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop_gnome_systemd-20190823-111827 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.2.0 * Available Python interpreters, in order of preference: [1] python3.7 [2] python3.6 [3] python2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) [2] ruby25 (with Rubygems) * Available Rust versions: [1] rust-1.37.0 * java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.13.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm repository timestamp: ==> /var/db/repos/gentoo/metadata/timestamp.chk <== Sun, 25 Aug 2019 20:48:14 +0000 emerge -qpvO dev-libs/libsavitar [ebuild N ] dev-libs/libsavitar-4.2.0 USE="python -static-libs" PYTHON_SINGLE_TARGET="python3_6 -python3_5" PYTHON_TARGETS="python3_6 -python3_5"
Created attachment 588046 [details] emerge-info.txt
Created attachment 588048 [details] CMakeOutput.log
Created attachment 588050 [details] dev-libs:libsavitar-4.2.0:20190825-220429.log
Created attachment 588052 [details] emerge-history.txt
Created attachment 588054 [details] environment
Created attachment 588056 [details] etc.portage.tbz2
Created attachment 588058 [details] logs.tbz2
Created attachment 588060 [details] temp.tbz2
I ran into this as well. It was due to libsavitar (and libarcus) using python-3.7, but python-3.7 was not in my python targets. Adding: PYTHON_TARGETS="${PYTHON_TARGETS} python3_7" to my make.conf and re-emerging dev-python/sip fixed it, but I suspect this is the least good way to do it.
As a follow up (and I shared this in: https://forums.gentoo.org/viewtopic-p-8378952.html#8378952) it looks like libsavitar and libarcus don't follow eselect python for what versions they build against. I removed python 3.7 locally and re-installed them, which also 'fixed' this bug, and also made cura work.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=79c8cc57487541ba7ff75ce2b5c50df5266014c6 commit 79c8cc57487541ba7ff75ce2b5c50df5266014c6 Author: Michael Perlov <perlovka@gmail.com> AuthorDate: 2019-09-28 10:28:38 +0000 Commit: Joonas Niilola <juippis@gentoo.org> CommitDate: 2019-10-16 05:21:58 +0000 dev-libs/libsavitar: version bump to 4.3.0 Closes: https://bugs.gentoo.org/692862 Package-Manager: Portage-2.3.76, Repoman-2.3.17 Signed-off-by: Michael Perlov <perlovka@gmail.com> Signed-off-by: Joonas Niilola <juippis@gentoo.org> dev-libs/libsavitar/Manifest | 1 + dev-libs/libsavitar/libsavitar-4.3.0.ebuild | 50 +++++++++++++++++++++++++++++ 2 files changed, 51 insertions(+)
