If you're familiar with macOS and Emacs, you might know what I'm talking about when I say that I do use the exec-path-from-shell Emacs package, but I assume that it does its thing too late in the start-up process to help me. However, I suspect that Emacs still doesn't see the correct GCC when it starts up. Since my $PATH has my ports directory prepended, running gcc from a shell does in fact call the correct, true, GCC. ![]() So, I suspected that I needed to install the real GCC from MacPorts. You might also want to run port -nR upgrade -force foo to rebuild ports depending upon port foo. The following ports will be rebuilt: paq8 8p. If so, try a port uninstall foo and then reinstall. I pretty quickly realized that macOS's clang is aliased (or soft-linked, or something- I didn't investigate) to gcc. Found 4 broken ports, determining rebuild order You can always run port rev-upgrade again to fix errors. The Homebrew crowd just installs some specific GCC package and all is well for them. Ports that display this error are no more broken than they were before: the mismatch always existed, but MacPorts wasnt checking for it before. Now, this is totally normal when GCC and/or libgccjit are not present, and a web search of these errors will find several forums posts and bug reports, etc. ![]() Warning (comp): /Applications/MacPorts/Emacs.app/Contents/Resources/lisp/outline.el.gz: Error: Internal native compiler error failed to compile Disable showing Disable logging Warning (comp): libgccjit.so: error: error invoking gcc driver Disable showing Disable logging Warning (comp): collect2: error: ld returned 1 exit status Disable showing Disable logging TransGaming has handled the Mac ports of numerous. If this isnt sufficient, you can keep an old copy of the port in a local portfile repository 1, but please dont forget about that if you do it. When I install any of the usual suspect Emacs packages in MacPorts (emacs-app, emacs-mac-app, etc), I get the same issue when Emacs starts up: it floods the *Warnings* buffer with stuff like: The gameplay is broken up with fully voiced, animated cutscenes, which tell a strikingly dark tale. So if you have the current version of the broken port installed but inactive, sudo port upgrade outdated will ignore it (unless it is a dependency of some port you are installing or upgrading). ![]() There are plenty of guides/posts online about installing libgccjit with Homebrew to get it to work.īut, I've been using MacPorts for a long time and really don't have any desire to use both MacPorts and Homebrew. I apologize for the possibly annoying question, but I'm struggling to get Emacs 28's nativecomp to work.
0 Comments
Leave a Reply. |