Hi, Yes, it's on the same machine. I've tried copying the dylib to MacOS/Plugins directory and it doesn't fix it. Weirdly, if I start the Pharo executable from the command line, where I've set the DYLD_LIBRARY_PATH for the dylib in the shell environment, it works. So it seems to be something to do with how OSX Applications have their DYLD_LIBRARY_PATH set. I know there used to be a file in /etc/ on older versions of OS X where you could set it where it did get picked up by applications, but that no longer seems to be the case with the latest version of OSX. Thanks