-
-
Notifications
You must be signed in to change notification settings - Fork 187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[General]: libgccjit error "no such file or directory: 'HOST=mymacbook'" #736
Comments
This looks like an upstream issue, the MacPorts build of emacs-app-devel has the same problem on my machine. I have not been able to find if it's an Emacs or libgccjit issue. |
I have made the same error after upgrade to macOS 15 |
I had also the same issue after upgrading to Sequoia, but in my case it is related to #720, and the messages go away when I start Emacs from Terminal.app (or via the integrated scripts that also launch Emacs from the shell, but leave another window open). |
No, I can't build with 'native-comp' brew install emacs-plus@30 --with-xwidgets --with-native-comp --with-modern-black-gnu-head-icon
|
If you add the exec-path-from-shell package it will fix it for now. Eventually the bug will be fixed upstream and you can remove exec-path-from-shell. I can confirm it's still a problem on macOS Sequoia 15.1 official release version. |
I have the same error after upgrading to Sequoia 15.1. exec-path-from-shell doesn't fix the issue. Only |
It's really frustrating that I can't trace what the heck is spewing these errors. It feels like somewhere the invocation of clang went from a shell exec to a direct exec.
But I don't know where to report this or how to bisect it. |
Issue description
I recently upgraded to Mac OS 14.7 on this machine (actual hostname replaced with
mymacbook
below).After the upgrade I started to get the errors at the end. I've ensured that gcc, libgccjit, and emacs-plus have been uninstalled and installed again.
[Update 2024-11-19: after upgrading to Mac OS 15.1, the problem persists]
I've verified that
(getenv "PATH")
is correct so I don't think it's #720 (and I'm on Sonoma anyway).and in Emacs-plus
The only way I've been able to start Emacs-plus has been by setting this in early-init.el:
So this seems like perhaps an error in the way
comp.el
does the compilation invocation but I haven't been able to find the issue. I hope you'll have some clue. Thank you for your kind time and help.Sample compilation errors during startup and after:
The text was updated successfully, but these errors were encountered: