Created attachment 872103 [details] build log Traceback (most recent call last): File "/var/tmp/portage/dev-util/intel-graphics-compiler-1.0.15136.4/work/intel-graphics-compiler-igc-1.0.15136.4/IGC/GenISAIntrinsics/generator/generate_intrinsic_files.py", line 11, in <module> from Intrinsic_utils import file_path, dir_path File "/var/tmp/portage/dev-util/intel-graphics-compiler-1.0.15136.4/work/intel-graphics-compiler-igc-1.0.15136.4/IGC/GenISAIntrinsics/generator/Intrinsic_utils.py", line 14, in <module> from mako.template import Template ModuleNotFoundError: No module named 'mako' [I] dev-python/mako Available versions: 1.2.4^t {doc test PYTHON_TARGETS="pypy3 python3_10 python3_11 python3_12"} Installed versions: 1.2.4^t(08:15:54 2023-05-29)(-doc -test PYTHON_TARGETS="python3_11 -pypy3 -python3_10 -python3_12") ∞ eselect python list Available Python interpreters, in order of preference: [1] python3.11 [2] python3.12 (fallback) [3] python3.10 (fallback)
Created attachment 872104 [details] emerge --info
I have the same problem. AFAICT, cmake recognizes the higher version of python as the default one; building mako for python 3.12 allows to build the package. It is possible the ebuild needs adding an explicit -DPYTHON_EXECUTABLE pointing to the right version.
(In reply to Michelangelo Scopelliti from comment #2) > I have the same problem. > > AFAICT, cmake recognizes the higher version of python as the default one; > building mako for python 3.12 allows to build the package. > > It is possible the ebuild needs adding an explicit -DPYTHON_EXECUTABLE > pointing to the right version. This won't be enough, but I will commit a proper solution. I see the problem here, thanks!
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7b730475a81fb4efd79dfb6ed7348af4ee9e5c25 commit 7b730475a81fb4efd79dfb6ed7348af4ee9e5c25 Author: Conrad Kostecki <conikost@gentoo.org> AuthorDate: 2023-10-04 12:02:26 +0000 Commit: Conrad Kostecki <conikost@gentoo.org> CommitDate: 2023-10-04 14:41:30 +0000 dev-util/intel-graphics-compiler: add missing deps for mako Closes: https://bugs.gentoo.org/915117 Signed-off-by: Conrad Kostecki <conikost@gentoo.org> ...15136.4.ebuild => intel-graphics-compiler-1.0.15136.4-r1.ebuild} | 6 ++++++ 1 file changed, 6 insertions(+)
What's the reason behind the revbump?
(In reply to Sergey 'L29Ah' Alirzaev from comment #5) > What's the reason behind the revbump? Deps changed.
(In reply to Conrad Kostecki from comment #6) > (In reply to Sergey 'L29Ah' Alirzaev from comment #5) > > What's the reason behind the revbump? > > Deps changed. It doesn't make any sense to rebuild a package because its build-time dependencies that don't get incorportated into the package have changed, does it?
(In reply to Sergey 'L29Ah' Alirzaev from comment #7) > (In reply to Conrad Kostecki from comment #6) > > (In reply to Sergey 'L29Ah' Alirzaev from comment #5) > > > What's the reason behind the revbump? > > > > Deps changed. > > It doesn't make any sense to rebuild a package because its build-time > dependencies that don't get incorportated into the package have changed, > does it? From this perspective, you are right. But people, who have already this version installed, wouldn't get the updated deps in metadata written.
(In reply to Conrad Kostecki from comment #8) > (In reply to Sergey 'L29Ah' Alirzaev from comment #7) > > It doesn't make any sense to rebuild a package because its build-time > > dependencies that don't get incorportated into the package have changed, > > does it? > > From this perspective, you are right. But people, who have already this > version installed, wouldn't get the updated deps in metadata written. And does it matter? It's not like the upgrade or removal of the dependencies affect the installed package in any way.
