https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: media-gfx/darktable-3.8.0-r2 fails to compile. Discovered on: amd64 (internal ref: tinderbox_musl) NOTE: This machine uses MUSL libc
Created attachment 763588 [details] build.log build log and emerge --info
Created attachment 763589 [details] 1-CMakeError.log 1-CMakeError.log
Created attachment 763590 [details] 1-CMakeOutput.log 1-CMakeOutput.log
Error(s) that match a know pattern: -- Package 'iso-codes', required by 'virtual:world', not found -- Could NOT find Jasper (missing: JASPER_LIBRARIES JASPER_INCLUDE_DIR) -- Could NOT find libheif (missing: libheif_DIR) -- Could NOT find libheif (missing: libheif_LIBRARY libheif_INCLUDE_DIR) (Required is at least version "1.9.0") error: #error Do not know how to query CPU L1d cache line size for this
See src/external/rawspeed/cmake/Modules/cpu-page-size.cpp
tinderbox_musl has reproduced this issue with version 4.2.0 - Updating summary.
OK, so the versions of sys-libs/musl currently in the tree have finally got support for the _SC_PAGESIZE syscall. Still nothing for the cache-line size one, though... On the plus side, rawspeed build scripts already already have the option to use hard-coded default values here in case of binary builds so it should be a fairly straightforward matter of making it possible to fall back to this mode in our case as well.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=05e28cce9d058d40e7d2001c1202b315b8a6742d commit 05e28cce9d058d40e7d2001c1202b315b8a6742d Author: Marek Szuba <marecki@gentoo.org> AuthorDate: 2023-02-28 12:07:15 +0000 Commit: Marek Szuba <marecki@gentoo.org> CommitDate: 2023-02-28 13:12:40 +0000 media-gfx/darktable: fix rawspeed CPU-property detection on musl For page-cache size, the sys-libs/musl version currently in the tree does support the relevant syscall so just make sure the test program recognises this correctly. For cache-line length, it does not presently seem to be possible to look this up on a musl system so have CMake fall back to the hard-coded default. It can already do so when in "build binary package" mode so it has been a simple matter of extending one condition to check for the ebuild-specified "am I linking against musl?" option. Closes: https://bugs.gentoo.org/832027 Signed-off-by: Marek Szuba <marecki@gentoo.org> media-gfx/darktable/darktable-4.2.1.ebuild | 2 ++ .../files/darktable-4.2.1_cmake-musl.patch | 22 ++++++++++++++++++++++ 2 files changed, 24 insertions(+)
