https://gcc.gnu.org/bugzilla/show_bug.cgi?id=123976
--- Comment #40 from Peter Dyballa <Peter_Dyballa at web dot de> --- (In reply to Sergey Fedorov from comment #38) > > Why though? Habits. Being installed prepared to return to "daily work" or such. > I can't really think of a reason why gcc build should need all that, on any > system. Yes, it should be OK to leave X11 and work in Terminal – with Apple's GNU Emacs. It's a week or more that I cannot do anything else. In GNU Emacs' *compilation* buffer I can search forward or backward much better than in Terminal, or switch to a *shell* buffer to check something on the command line, or open some directory in *dired* mode to examine files more efficiently than with vi that needs the complete path name of a file. Or copy&paste regions containing a failure. Anyway, it there is nothing else for me to perform after GCC 16 built, I would try a "clean build".
