Warning: arch-dependent data dir ‘/Users/build/workspace/Emacs-Multi-Build/label/macos10.14/emacs-source/nextstep/Emacs.app/Contents/MacOS/libexec/’: No such file or directory pdmp procedure after installing 27.1 via Homebrew. If you’ve been plagued by these problems, I hope this post helped.ĭoes anyone know how to avoid this error when executing /usr/local/bin/emacs (symbolic link to /Applications/Emacs.app/Contents/MacOS/Emacs), which is created by Homebrew automatically? I followed the procedure in the original post and additional. In future versions of Emacs, it’s possible that the correct binary might be something other than Emacs-x86_64-10_14. One final caveat: This works for me using homebrew-cask-installed Emacs version 26.3. If you can’t launch Emacs after running these commands, try following the steps in this document from Apple. The last command above removes the code signature from the Emacs binary. Note that, because we have been performing surgery on the Emacs app, its code signature is no longer valid. At the Terminal, just run these commands: % cd /Applications/Emacs.app/Contents/MacOSĪnd, with that, Emacs should correctly receive its Full Disk Access permission, and Spotlight will correctly bring it to front (n.b., it’s still required to add Emacs to the Full Disk Access section of the security system preferences). So, if you simply move it in place of the Emacs launcher script, everything starts working as normal. On Catalina, the Ruby script will always choose to launch the bundled binary Emacs-x86_64-10_14.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |