# CMAKE\_SYSTEM\_HOST\_PROCESSOR and CMAKE\_SYSTEM\_PROCESSOR wrong

**URL:** <https://discourse.cmake.org/t/cmake-system-host-processor-and-cmake-system-processor-wrong/8796>\
**Category:** Code\
**Created:** [August 21, 2023, 6:52pm UTC](https://discourse.cmake.org/t/cmake-system-host-processor-and-cmake-system-processor-wrong/8796 "2023-08-21T18:52:35Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jshanab](https://discourse.cmake.org/user_avatar/discourse.cmake.org/jshanab/32/2555_2.png) [@jshanab](https://discourse.cmake.org/u/jshanab)\
**Post date:** [August 21, 2023, 6:52pm UTC](https://discourse.cmake.org/t/cmake-system-host-processor-and-cmake-system-processor-wrong/8796/1 "2023-08-21T18:52:35Z")

</div>

I use this value to pull specific cross compiled artifacts from our artifactory server.

This time I am NOT cross compiling. I am compiling on a arm64 board. (aarch64)

uname -m returns “aarch64”

Both CMAKE\_SYSTEM\_HOST \_PROCESSOR and CMAKE\_SYSTEM\_PROCESSOR are just “Linux”

Building on a raspberrypi 4 with CMake version 3.27.1 built from source on the pi.

---

<div class="post-metadata">

**Author:** ![jshanab](https://discourse.cmake.org/user_avatar/discourse.cmake.org/jshanab/32/2555_2.png) [@jshanab](https://discourse.cmake.org/u/jshanab)\
**Post date:** [August 21, 2023, 7:20pm UTC](https://discourse.cmake.org/t/cmake-system-host-processor-and-cmake-system-processor-wrong/8796/2 "2023-08-21T19:20:57Z")

</div>

even after deleting CMAkeCache it persisted but then suddenly it started returning aarch64.

Working now. not sure what i was doing to confuse it.

---

<div class="post-metadata">

**Author:** ![ben.boeckel](https://discourse.cmake.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.cmake.org/u/ben.boeckel)\
**Post date:** [August 22, 2023, 10:50am UTC](https://discourse.cmake.org/t/cmake-system-host-processor-and-cmake-system-processor-wrong/8796/3 "2023-08-22T10:50:42Z")

</div>

Without a reproducer case, it’ll be hard to know what’s going on here. If it happens again, please try to grab exact commands and environment information so that it can be investigated.