Need to set LIBRARY_PATH for emacs-plus@28 with --with-native-comp

[poldy]

I ran brew install emacs-plus@28 --with-native-comp and it completed successfully. However, when I tried to run Emacs although the editor worked, there were loads of native compilation warnings.

The solution was to create a one-line ~/.emacs.d/early-init.el, with the following contents:

(setenv "LIBRARY_PATH" "/opt/homebrew/lib/gcc/11:/opt/homebrew/lib/gcc/11/gcc/aarch64-apple-darwin20/11.1.0")

I'd suggest adding this to the "gccemacs" section of the README.

This is on an M1 iMac, it works great now.

[jilen]

Start emacs from the Terminal instead of click the emacs icon works for me.

[kommen]

EDIT

Don't set LIBRARY_PATH as I originally suggested in this post, it is just fighting symptoms, not the root cause, see other comments below.

Original comment below
------------------------

I can confirm setting LIBRARY_PATH as @poldy suggests as an env in my bash/zsh config fixes native-comp errors. Without it set I got this (a bit redacted)

Native compiler error: (lambda (&optional arg6) (let ((f #'kill-emacs)) (funcall f arg6))), Compiling <home>/.emacs.d/eln-cache/28.0.50-b1d099bb/subr--trampoline-6b696c6c2d656d616373_kill_emacs_0.eln...
ld: library not found for -lgcc_s.1.1
libgccjit.so: error: error invoking gcc driver
Debugger entered--Lisp error: (native-ice "failed to compile" "<home>/emacs.d/eln-cache/28.0.50-b1d099bb/..." "error invoking gcc driver")

[d12frosted]

See this message. If you have to set LIBRARY_PATH that probably just means something is wrong with your environment. Works for me without any hacks like this. Though I must admit, never tested on M1.

[kommen]

@d12frosted thanks!

After reinstalling gcc and libgccjit (also from source) with no success, I poked around in my env:

It seems the issue was Spacemacs caching the env variables (including PATH) in the .spacemacs.env file. After adjusting the PATH there to include my newish homebrew M1 setup's /opt/homebrew/bin:/opt/homebrew/sbin: it looks I only get one native comp error regarding cl-lib, the other files now seem to compile fine.

[d12frosted]

it looks I only get one native comp error regarding cl-lib

Do you mean an error saying that it's obsolete/deprecated? 😄

the other files now seem to compile fine.

This sounds great.

[kommen]

Do you mean an error saying that it's obsolete/deprecated? 😄

Unfortunately no 😅. Still some native-comp error:

Compiling /opt/homebrew/Cellar/emacs-plus@28/28.0.50/share/emacs/28.0.50/lisp/emacs-lisp/cl-lib.el.gz...
uncompressing cl-lib.el.gz...
uncompressing cl-lib.el.gz...done
ld: library not found for -lgcc_s.1.1
libgccjit.so: error: error invoking gcc driver
/opt/homebrew/Cellar/emacs-plus@28/28.0.50/share/emacs/28.0.50/lisp/emacs-lisp/cl-lib.el.gz: Error: Internal native compiler error failed to compile

The others following immediately after it seemingly work:

Compiling /opt/homebrew/Cellar/emacs-plus@28/28.0.50/share/emacs/28.0.50/lisp/emacs-lisp/seq.el.gz...
uncompressing seq.el.gz...
uncompressing seq.el.gz...done
Compiling /opt/homebrew/Cellar/emacs-plus@28/28.0.50/share/emacs/28.0.50/lisp/emacs-lisp/gv.el.gz...
uncompressing gv.el.gz...
uncompressing gv.el.gz...done
...

[kommen]

I also got that last error fixed: it was because the compilation was kicked off by spacemacs before loading the .spacemacs.env file. This happens because when starting Emacs.app from the macOS Finder or Dock, the env vars are different then when launching from the command line (where I have my .zshrc). Launching Emacs from the commandline (executing /Applications/Emacs.app/Contents/MacOS/Emacs directly) so it inherits the env vars from there fixed it.

So I can confirm that these errors were entirely due to my environment Emacs runs in not being set up properly, especially that PATH is set correctly for Emacs when running with homebrew on an M1 Mac. I hope this helps other folks running into this.

[d12frosted]

People say that null pointers are billion dollars issue, but I'd rather say that it's PATH. I actually wonder if it's a good idea to patch info.plist file when emacs-plus is built so it includes PATH value during the build. That way it will automatically get the right (though possible out of date) PATH value without the need to resort to things like exec-path-from-shell or env from Spacemacs.

[elken]

People say that null pointers are billion dollars issue, but I'd rather say that it's PATH. I actually wonder if it's a good idea to patch info.plist file when emacs-plus is built so it includes PATH value during the build. That way it will automatically get the right (though possible out of date) PATH value without the need to resort to things like exec-path-from-shell or env from Spacemacs.

This is probably a better solution IMO than relying on users having correct environments. When built with native-comp, add the path during build so on startup the compiler can find libgccjit.

[eltone]

I had the same error after brew reinstall emacs-plus@28 --with-native-comp. I was able to fix it with:

brew unlink emacs-plus@28 && brew link emacs-plus@28

[d12frosted]

General advise - never use reinstall, especially with emacs-plus. See readme section for this. Cheers, ***@***.***

…

On Fri, Sep 3, 2021 at 12:08, Anthony Hobbs ***@***.***> wrote: I had the same error after brew reinstall ***@***.*** --with-native-comp. I was able to fix it with: brew unlink ***@***.*** && brew link ***@***.*** — You are receiving this because you were mentioned. Reply to this email directly, [view it on GitHub](#378 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ABRU3CNYJS2H4V7HAKTIZOTUACGBTANCNFSM5BR7Y3FA).

[AthenaEryma]

In case anyone else finds this wants to change Info.plist fix manually after compiling, I found details on how to do so on this EmacsWiki page. Note that after editing Info.plist, you need to run /System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -f <path_to_your_Emacs.app> or MacOS won't pick up on the fact that the plist has been updated and won't get the changed environment variables.

(That last bit had me pulling my hair out for a while)

[yuezhu]

On macOS 10.15 I was getting the same error while launching the Emacs application from the LaunchPad/Dock. It turned out the PATH environment variable isn't set correctly in this case. And I was able to work it around by adding the PATH into /usr/local/opt/emacs-plus@28/Emacs.app/Contents/Info.plist as follows:

# /usr/libexec/PlistBuddy -c "Add :LSEnvironment dict" /usr/local/opt/emacs-plus@28/Emacs.app/Contents/Info.plist
# /usr/libexec/PlistBuddy -c "Add :LSEnvironment:PATH string" /usr/local/opt/emacs-plus@28/Emacs.app/Contents/Info.plist
# /usr/libexec/PlistBuddy -c "Set :LSEnvironment:PATH $(echo "$PATH")" /usr/local/opt/emacs-plus@28/Emacs.app/Contents/Info.plist
# /usr/libexec/PlistBuddy -c "Print :LSEnvironment" /usr/local/opt/emacs-plus@28/Emacs.app/Contents/Info.plist
# touch /usr/local/opt/emacs-plus@28/Emacs.app

Make sure that the PATH environment variable is set correctly in your shell.