Skip to content

Instantly share code, notes, and snippets.

Created August 14, 2022 23:19
Show Gist options
  • Save CINJ/6e6dbd0eefad11a69dd1c7308b36359c to your computer and use it in GitHub Desktop.
Save CINJ/6e6dbd0eefad11a69dd1c7308b36359c to your computer and use it in GitHub Desktop.

With a somewhat complex set of data science related dependencies (matplotlib, scikitlearn, and pytorch amongst others) I initially I came across this error: 

Error #15: Initializing libiomp5.dylib, but found libiomp5.dylib already initialized OMP: Hint: This means that multiple copies of the OpenMP runtime have been linked into the program. That is dangerous, since it can degrade performance or cause incorrect results. The best thing to do is to ensure that only a single OpenMP runtime is linked into the process, e.g. by avoiding static linking of the OpenMP runtime in any library. As an unsafe, unsupported, undocumented workaround you can set the environment variable KMP_DUPLICATE_LIB_OK=TRUE to allow the program to continue to execute, but that may cause crashes or silently produce incorrect results. For more information, please see

The solutions I found to this problem when searching was primarily around forcing the Conda environment to use X86 (basically Rosetta2 emulation). Upon doing this I found issues with MKL as per the error below:

Intel MKL FATAL ERROR: This system does not meet the minimum requirements for use of the Intel(R) Math Kernel Library. The processor must support the Intel(R) Supplemental Streaming SIMD Extensions 3 (Intel(R) SSSE3) instructions. The processor must support the Intel(R) Streaming SIMD Extensions 4.2 (Intel(R) SSE4.2) instructions. The processor must support the Intel(R) Advanced Vector Extensions (Intel(R) AVX) instructions.

Bottom line is that while all the solutions were focused on ensuring there was a single architecture being used, it still did not resolve my issues. As more versions of the common data science libraries have been migrated to Apple silicon, it seems like more platform specific optimisations have also been added to the mix including Intel architectures. Bottom line is that I realised the best solution was not to use compatibility, rather, force the Conda installation to use M1 specific builds for everything. It has been nearly two years since M1 was introduced, so we should be safe in doing this (I hoped) - using the bash script below I was proven correct.

You can easily modify the script below to:

  • use plain Conda instead of (the vastly superior) Mamba
  • change where the yml file is expected to be
  • change your 'forced' architecture (I can't think of other environments where this emulation problem would be an issue so I only made the script support M1)

The expectation is that you understand the format of Conda dependency YML files. See for more details.

# (C)2022 J.Cincotta
# Version 5.2
# Usage:
# Create conda environment
# <environment_name>
# Update conda environment
# -u <environment_name>
# Delete conda environment
# -d <environment_name>
# Assumes that there is a yml file in the same directory as the script
# this file should be named the same as the environment. For example, if my
# environment name is "my_environment" then it expects "my_environment.yml"
# works with Linux for x86 and ARM and MacOS x86 and M1
DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" >/dev/null 2>&1 && pwd )"
# ARCH Values:
# aarch64 : Linux ARM
# arm64 : M1
# x86_64 : X86 Linux or Mac
# OS Values:
# Linux : Linux
# Darwin : Mac
# Available Conda Architecture Dependency Paths:
# linux-64
# linux-aarch64
# linux-ppc64le
# osx-64
# osx-arm64
# win-64
# Force Conda to use M1 ARM builds for everything
if [ "$ARCH" == "arm64" ] && [ "$OS" == "Darwin" ];
echo "Compatability mode enabled for M1 Mac"
if [ "$1" == "-delete" ] || [ "$1" == "-d" ];
conda remove --name $2 --all
exit 0
if [ "$1" == "-update" ] || [ "$1" == "-u" ];
eval "$(conda shell.bash hook)"
conda activate ${CONDENV}
if [ "$COMPAT" == "1" ];
conda config --env --set subdir $COMARCH
CONDA_SUBDIR=$COMARCH mamba env update -f "${DIR}/${CONDENV}.yml"
mamba env update -f "${DIR}/${CONDENV}.yml"
echo "Install Mamba"
conda install -y mamba -n base -c conda-forge
echo "Create ${CONDENV}"
if [ "$COMPAT" == "1" ];
CONDA_SUBDIR=$COMARCH mamba env create -f "${DIR}/${CONDENV}.yml"
eval "$(conda shell.bash hook)"
conda activate ${CONDENV}
conda config --env --set subdir $COMARCH
mamba env create -f "${DIR}/${CONDENV}.yml"
eval "$(conda shell.bash hook)"
conda activate ${CONDENV}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment