Stefan Monnier <monn...@iro.umontreal.ca> writes: > Russ Allbery [2022-08-19 11:42:30] wrote: >> The 28.1 version of emacs-lucid fails on startup with a cryptic error >> message: >> >> % emacs >> Cannot find suitable directory for output in ‘comp-native-load-path’. >> >> Running emacs -q allows it to start, but it still reports the same error >> immediately during startup, and attempting to do someting as basic as >> M-x set-variable (to try to enable debug-on-error) fails with a similar >> error message: >> >> defalias: Cannot find suitable directory for output in >> ‘comp-native-load-path’. >> >> emacs -q --no-site-file avoids the error on startup, but M-x set-variable >> still immediately fails with the same error. > > This error is signaled by `comp-el-to-eln-filename` and it usually > indicates that that function was unable to find a writable directory in > which to put the auto-generated `.eln` native-compiled files. > > I don't know why it fails to find a writable directory. Maybe > > emacs --debug-init` would help > or > emacs -e '(message "%S" comp-native-load-path)' > > might help track down the origin of the problem. > > This said, Emacs shouldn't become unusable in such a circumstance, so we > should maybe use a patch along the lines of the one below (not sure if > it wraps the relevant invocation of `comp-el-to-eln-filename`, tho).
Agree Emacs should stay usable and I think the one you've identified should be the right invocation to be wrapped. Best Regards Andrea
