Fail build if libseccomp below some minimum version?

I'm well-aware of the warning text in the release notes

However we strongly suggest that you make use of your distribution's packages
or download them from the authoritative upstream sources, especially since
these libraries are related to the security of your containers.

Today I was looking at versions of libseccomp in various distros, and surprised/shocked to find that the newest versions of still-supported major releases like Alma 8.10/9.6 are on libsseccomp v2.5.2 which was released in Sept. 2021, 4 years ago.

So in many ways, relying on distro builds might not actually be such a good idea, even if they've been built by reputable sources? My question boils down to whether runc should fail to build (by default) if it finds a too-old libseccomp.

I see that the release scripts already contain a check

https://github.com/opencontainers/runc/blob/996278a1898690547c2546fdf6d2f2259b3eab8c/script/seccomp.sh#L8-L13

but this is not visible when doing make & make install.

Xref also #1016

Start by reading script/seccomp.sh lines 8–13 and comparing that check with the default make and make install path. Trace how libseccomp is detected during the build, then review the discussion and cross-reference in #1016. Done means the project has an agreed default behavior for too-old libseccomp and the relevant build path reflects it.