to tell CMake that the project requires at least <min> but has been updated to work with policies introduced by <max> or earlier. Or, add -DCMAKE_POLICY_VERSION_MINIMUM=3.5 to try configuring anyway. -- Configuring incomplete, errors occurred! * ERROR: app-misc/vcontrold-0.98.11::gentoo failed (configure phase): * cmake failed ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 23.0_no_multilib_hardened_systemd-20250411-223002 KEYWORDED/UNMASKED [cmake-4] Requested by sam =dev-build/cmake-4* [gcc-15] Requested by sam <sys-devel/gcc-15.0.9999:15 The attached etc.portage.tar.xz has all details. ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-15 * clang version 20.1.2 llvm-config: 20.1.2 Python 3.12.10 Available Ruby profiles: [1] ruby32 (with Rubygems) [2] ruby34 (with Rubygems) * Available Rust versions: [1] rust-bin-1.85.1 * HEAD of ::gentoo commit 1ddad8ad1896390646271827b9eb390cb9dbcc88 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Sun Apr 13 02:35:18 2025 +0000 2025-04-13 02:35:17 UTC The tinderbox task was: app-misc/vcontrold emerge -qpvO =app-misc/vcontrold-0.98.11 [ebuild N ] app-misc/vcontrold-0.98.11 USE="man vclient -vsim"
Created attachment 924551 [details] emerge-info.txt
Created attachment 924552 [details] app-misc:vcontrold-0.98.11:20250413-034507.log
Created attachment 924553 [details] emerge-history.txt
Created attachment 924554 [details] environment
Created attachment 924555 [details] etc.clang.tar.xz
Created attachment 924556 [details] etc.portage.tar.xz
Created attachment 924557 [details] logs.tar.xz
Created attachment 924558 [details] qlist-info.txt
Created attachment 924559 [details] temp.tar.xz
All I can say is that compilation works without a problem with the current stable gcc 14.2.1_p20241221 and cmake 3.31.5 ... Both gcc 15 and cmake 4 are currently hard-masked. I suppose they are for a reason ... tbh I don't want to break my system trying upgrading core parts to hard masked versions. As soon as those are at least testing, I'll see if I can do something about it. However, you're of course welcome to fix this, I'll gladly forward this to upstream!
Is there some safe way to test this? Seems we have some chicken-egg problem here ...