# \[SOLVED\] OSError incompatible architecture

**URL:** <https://openmc.discourse.group/t/solved-oserror-incompatible-architecture/3570>\
**Category:** User Support\
**Created:** [October 26, 2023, 11:12pm UTC](https://openmc.discourse.group/t/solved-oserror-incompatible-architecture/3570 "2023-10-26T23:12:18Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![josephhall](https://avatars.discourse-cdn.com/v4/letter/j/5fc32e/32.png) [@josephhall](https://openmc.discourse.group/u/josephhall)\
**Post date:** [December 1, 2023, 4:42pm UTC](https://openmc.discourse.group/t/solved-oserror-incompatible-architecture/3570/4 "2023-12-01T16:42:42Z")

</div>

I have run into the same error, this post wasn’t very clear so I wanted to add in more detail how I fixed the problem. To my understanding, in order to install openmc using conda, you need to explicitly tell conda that you are emulating x86\_64 architecture because the mamba version of openmc is not yet compatible with Apple arm64 chips. I had created such a conda environment in my post [here](https://openmc.discourse.group/t/openmc-installation-using-mamba/3130). The drawbacks to installing in this way are that, on apple chips, you tend to get crazy segmentation fault errors when doing things like plotting geometries, and all of those errors told me to install from source, which I did. Once you install from source, your openmc executable will be compatible with arm64 and you then need to create a REGULAR conda environment before pip installing. Then it all seemed to work out. In conclusion, installing from source eliminates a ton of headache down the road.

---

_[View the full topic](https://openmc.discourse.group/t/solved-oserror-incompatible-architecture/3570)._