# Toolchain with shipped older cmake conflicts with outer newer one

**URL:** <https://discourse.cmake.org/t/toolchain-with-shipped-older-cmake-conflicts-with-outer-newer-one/13825>\
**Category:** Code\
**Created:** [March 26, 2025, 12:11pm UTC](https://discourse.cmake.org/t/toolchain-with-shipped-older-cmake-conflicts-with-outer-newer-one/13825 "2025-03-26T12:11:08Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![eriols](https://discourse.cmake.org/user_avatar/discourse.cmake.org/eriols/32/945_2.png) [@eriols](https://discourse.cmake.org/u/eriols)\
**Post date:** [March 26, 2025, 12:11pm UTC](https://discourse.cmake.org/t/toolchain-with-shipped-older-cmake-conflicts-with-outer-newer-one/13825/1 "2025-03-26T12:11:09Z")

</div>

Upgrading my cmake I have a few old (Yocto for instance) toolchains now blowing up as there is an older cmake within the toolchain that takes precedence. I.e the mininum required version is not met.  
Is there a setting to make so that I want everything _but_ cmake from the toolchain sysroots?’  
I encountered it once before but then I just took out the sledge hammer and had a script that deleted the cmake binary from the extracted toolchain before using it. But that is not ideal of course.