Hello Mohammed Bilal, I've checked the bug report and the attached build log but I have some concern that it is actually related to libgit2.
The build process actually stops here: Run-time dependency threads found: YES Found pkg-config: /usr/bin/pkg-config (0.29.2) Run-time dependency nanomsg found: YES 1.1.5 Found CMake: /usr/bin/cmake (3.23.0) WARNING: CMake Toolchain: Failed to determine CMake compilers state Run-time dependency nanopb found: NO and most probably the reason that it fails to detect nanopb is that the cmake compiler has trouble compiling the test code. A healthy run looks like this: Run-time dependency threads found: YES Found pkg-config: /usr/bin/pkg-config (0.29.2) Run-time dependency nanomsg found: YES 1.1.5 Found CMake: /usr/bin/cmake (3.23.1) Run-time dependency nanopb (modules: nanopb::protobuf-nanopb-static) found: YES 0.4.5 Run-time dependency libgit2 found: YES 1.3.0 As you can see, the autoconfigure script not even reached checking the libgit in the failed case. (Minor detail, in the successful case, the CMake version is 3.23.1, not 3.23.0. Unfortunately, based on the criticality I thought the new version of the libgit2 library is already in unstable, so first I tried to upgrade the criterion version and just started to investigate afterwards. So I actually do not know if the old version is actually has any incompatibility with the libgit2 version 1.3.0. But (with some tweak) I was able to successfully compile the new Criterion version with the new libgit2 version, I will simply close this ticket using the new version Changelog.
signature.asc
Description: This is a digitally signed message part
