![]() ![]() The new native-compilation feature will churn through your startup Elisp and probably spew a ton of warnings, but eventually you'll notice that Emacs feels much zippier. If all goes well you should be able to start Emacs and (emacs-version) will report 28.1. The above steps will update your /Applications/Emacs.app in place, so if you had emacsclient in a different subdirectory (as I did) you may want to replace any symbolic links to the newly build version at /Applications/Emacs.app/Contents/Resources/bin/emacsclient. prefix=/Applications/Emacs.app/Contents/ResourcesĬonfirm your emacsclient is linked to the right place These steps also apply the (optional) multi-tty patch that I've written about before. Sudo rm -rf /Library/Developer/CommandLineToolsĪgain, something was wedged in the subsequent build process until I took this step, as recommeded in this GitHub thread. opt/homebrew/opt/texinfo/bin Install/re-install Xcode command-line tools ![]() Add makeinfo to pathĪdd this to your shell path (necessary so that the makeinfo provided by texinfo is seen before the older macOS-provided version). Also texinfo provides an updated makeinfo which is now no longer optional in the Emacs build process. I'm not sure why it was necessary to reinstall gcc (maybe an architecture issue?), but it seemed to help with a build error in a subsequent step. Overall the process seems much smoother than the pre-release build experience but as always YMMV. BREW MACVIM CANNOT ALLOCATE COLOR INSTALLThe Emacs Mac Port has been updated for Emacs 28.1 and here are the steps I used to build and install it on my M1 MacBook Air. This is an update of sorts to my previous Emacs build recipe and late-night Emacs-on-M1 twitter thread. Upgrading to Emacs 28.1 on Apple Silicon (M1) Macs ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |