SECURITY WARNING: Never run commands you don't understand. Always review code before execution. Use at your own risk.
FixMyError.net
C++ New Added 17 October 2026

CMake Error: Compatibility with CMake < 3.5 has been removed from CMake.

CMake 4.0 dropped support for projects that declare cmake_minimum_required below 3.5. The code is unchanged; your CMake upgraded, often silently through Homebrew, pip or a CI image, and an old project or vendored dependency still says VERSION 2.8 or 3.1. Usually the fix belongs upstream, and in the meantime CMAKE_POLICY_VERSION_MINIMUM lets the build continue.

Quick fix

Read the commands before running them. Anything that restarts a service, deletes data or changes permissions should be tried on a non-production system first.

Quick fix
# Which CMake is running?
cmake --version

# Find every project file declaring an old minimum, including vendored ones
grep -rn --include=CMakeLists.txt "cmake_minimum_required" . | grep -E "VERSION (2\.|3\.[0-4][^0-9])"

# Your own project: raise the minimum to one you actually test with
# cmake_minimum_required(VERSION 3.16)

# Third-party code you cannot edit yet: override at configure time
cmake -S . -B build -DCMAKE_POLICY_VERSION_MINIMUM=3.5

# pip builds that call CMake underneath
CMAKE_POLICY_VERSION_MINIMUM=3.5 pip install somepackage

How to diagnose C++ errors

C++ errors fall into two very different worlds. Compile and link errors (undefined reference, multiple definition, template substitution failure) are deterministic and are almost always about declarations, the One Definition Rule, or link order. Runtime memory errors (segfaults, double free, use-after-free) are non-deterministic and should never be debugged by reading code alone; a sanitizer will find in seconds what code review misses for days.

If the quick fix above does not resolve it, work through these steps. They apply to this whole class of error, not just to this one message, which is usually what saves the time.

  1. Rebuild with sanitizers before anything else: -fsanitize=address,undefined -fno-omit-frame-pointer -g. AddressSanitizer reports the exact allocation and free sites for use-after-free and double-free.
  2. For undefined-reference errors, check link order, remembering that with GNU ld libraries must come after the objects that use them, and check for a C/C++ linkage mismatch that needs extern "C".
  3. Use nm -C libfoo.a | grep symbol to confirm the symbol is actually present and to see the demangled signature. A signature that differs by a const is a different symbol.
  4. Enable core dumps (ulimit -c unlimited) and open them in gdb with gdb ./binary core, then bt full. A stack trace beats speculation.
  5. For template errors, read the message from the bottom up. The final line is usually the real constraint that failed; everything above is instantiation context.

Tools worth reaching for

  • -fsanitize=address,undefined
  • valgrind
  • gdb / lldb
  • nm -C
  • ldd

Authoritative references

Primary documentation for this error, worth reading before applying any fix in production.

cmake.org cmake.org

Related C++ errors

See all 20 C++ errors →

Browse other categories

Something missing or wrong?

This entry is maintained by hand. If the fix is out of date, incomplete, or you have a better one, email a correction and it will be reviewed.