Compiler GCC errors after upgrading to 30.1? Try this. #807
Replies: 6 comments
-
Welcome to the beautiful world of native compilation. Sounds a bit sarcastic, but it is what it is. Maybe we need to provide a way to disable native compilation after all, or disable it by default 🤷 Let's keep this ticket to collect thoughts and issues. |
Beta Was this translation helpful? Give feedback.
-
How do you even get 30.1? |
Beta Was this translation helpful? Give feedback.
-
brew update simply updates brew and formulas, but not packages. You are looking for brew upgrade. Although my advice (as written in readme) - uninstall and install - brew abandoned support of custom options and upgrade/reinstall can result in strange state if you want to use options 😅 |
Beta Was this translation helpful? Give feedback.
-
If you're collecting thoughts, I was happy to see native compilation become the default both in Emacs upstream and Emacs-plus. It makes for a stuttery first few minutes while packages are being compiled, but then a speedier experience after then. Maybe addressable via note in the README that when first running, it'll be a few minutes or so before it finishes compiling? |
Beta Was this translation helpful? Give feedback.
-
I guess I must be using an old version because it was NOT default for me. im getting an error invoking gcc driver message. however emacs seems to be working fine. |
Beta Was this translation helpful? Give feedback.
-
You can always verify that by checking the latest commit message in emacs+ formula: $ cd $(brew --repository)/Library/Taps/d12frosted/homebrew-emacs-plus && git log -1 (adapt it it if you are using fish or another shell) |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi 👋
I upgraded to 30.1 🥳. No issues downloading after upgrading Brew from scratch. Then I launched Emacs and got a ton of libgccjit and gcc warnings which took about 3 minutes to scroll past the Warnings buffer. 😱
My Solution: run Emacs via CLI with emacs --debug-init. Normally I use an Alfred alias to launch it from /opt/homebrew/Cellar. But, for some reason, doing it via CLI with the flag allowed all the compiling to be done. It gave me all the compile messages for a minute or so. After that, launching it via the alias worked like a charm. Not sure why, but it worked for me. I hope this helps someone if they run into this problem. 😀
Beta Was this translation helpful? Give feedback.
All reactions