2bf7fac176
This is to make sure duplicate libomp/libiomp5 runtime conflicts are detected as soon as a second runtime is initialized. Otherwise, it may not crash until Blender's OpenMP runtime is initialized by a feature that uses it, making such issues possibly go unnoticed. Such a conflict can happen when an add-on has a native module that uses OpenMP and links to a different libomp runtime, as was the case in #125255. Currently Blender only ships with libomp on MacOS. --- When libomp detects such an issue it should abort and print the following message: ``` OMP: Error #15: Initializing libomp.a, but found libomp.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 http://openmp.llvm.org/ ``` Pull Request: https://projects.blender.org/blender/blender/pulls/130407
Blender
Blender is the free and open source 3D creation suite. It supports the entirety of the 3D pipeline-modeling, rigging, animation, simulation, rendering, compositing, motion tracking and video editing.
Project Pages
Development
License
Blender as a whole is licensed under the GNU General Public License, Version 3. Individual files may have a different, but compatible license.
See blender.org/about/license for details.