# MacOS Sierra (10.12.6) dynamic linker errors

**URL:** <https://discourse.slicer.org/t/macos-sierra-10-12-6-dynamic-linker-errors/2339>\
**Category:** Development\
**Created:** [March 16, 2018, 7:54pm UTC](https://discourse.slicer.org/t/macos-sierra-10-12-6-dynamic-linker-errors/2339 "2018-03-16T19:54:15Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![hherhold](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/hherhold/32/12199_2.png) [@hherhold](https://discourse.slicer.org/u/hherhold)\
**Post date:** [March 16, 2018, 8:04pm UTC](https://discourse.slicer.org/t/macos-sierra-10-12-6-dynamic-linker-errors/2339/2 "2018-03-16T20:04:22Z")

</div>

This was the post that talked about it:

> [@Nightly build TESTS failing for extensions with dependencies to other scriptable modules](https://discourse.slicer.org/t/nightly-build-tests-failing-for-extensions-with-dependencies-to-other-scriptable-modules/1483/39):
>
> This error /Users/christian/sources/cpp/Builds/Slicer/Release/Slicer-build/lib/Slicer-4.9/qt-loadable-modules/./libvtkSlicerMarkupsModuleMRMLDisplayableManagerPythonD.dylib: malformed mach-o: load commands size (32840) \> 32768 seems to be due to the limit on total size of all the load commands in the dynamic library in the MacOS loader. I guess using a shorter build directory path would solve the issue. For example, instead of /Users/christian/sources/cpp/Builds/Slicer/Release, you could try…

I’m doing a build right now with a shorter path - we will see if that fixes it?

---

_[View the full topic](https://discourse.slicer.org/t/macos-sierra-10-12-6-dynamic-linker-errors/2339)._