This package does not support Python 3.12. Please test it with Python 3.12 as a matter of urgency as the default will change in early June, as per message on gentoo-dev: https://www.mail-archive.com/gentoo-dev@lists.gentoo.org/msg99104.html. Please check the information provided in the tracker. Ask in #gentoo-python on IRC if need any help.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9d5cefbcb6fdcfe5deb2f679b27f8b510c18c7c9 commit 9d5cefbcb6fdcfe5deb2f679b27f8b510c18c7c9 Author: Sv. Lockal <lockalsash@gmail.com> AuthorDate: 2024-06-02 11:03:33 +0000 Commit: Andrew Ammerlaan <andrewammerlaan@gentoo.org> CommitDate: 2024-06-03 13:27:02 +0000 sci-libs/blis: don't autodetect CPU, build according to cpu_flags_* This PR closes multiple issues: * binary packaging had flaws, because even on x86-64 target machine won't always match host cpu * crossdev compilation did not work, because correct compilers were not passed * tests did not work, because LD_LIBRARY_PATH had hardcoded `haswell` target * PYTHON_COMPAT: drop 3.9, add 3.12 and 3.13 This also adds few checks for aarch64 architecture, but aarch64 was not added to KEYWORDS, as few tests failed (in 0.9, not in 1.0). Note that while cpu_flags_*-based configuration resembles automatic one, it is not fully the same. For example, there are 2 types of Skylake CPUs: with 1 or 2 FMA units. Attempt to enable cpu_flags_x86_avx512vl on CPUs with 1 FMA unit will result in reduced performance. Previously this was handled by automatic detection of 1FMA Skylake as Haswell; now user should not specify cpu_flags_x86_avx512vl if CPU has degraded AVX-512 support. Closes: https://bugs.gentoo.org/928018 Closes: https://bugs.gentoo.org/765805 Closes: https://bugs.gentoo.org/929769 Signed-off-by: Sv. Lockal <lockalsash@gmail.com> Signed-off-by: Andrew Ammerlaan <andrewammerlaan@gentoo.org> .../{blis-0.9.0.ebuild => blis-0.9.0-r1.ebuild} | 59 +++++++++++++++------- 1 file changed, 41 insertions(+), 18 deletions(-)
