From: Manuel Uberti via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Andrea Corallo <akrl@sdf.org>, 53596@debbugs.gnu.org
Subject: bug#53596: 29.0.50; comp-trampoline-compile: Cannot find suitable directory for output in `native-comp-eln-load-path'
Date: Fri, 28 Jan 2022 11:32:46 +0100 [thread overview]
Message-ID: <74292753-93b6-abb1-4a3c-7e1d1f50724b@inventati.org> (raw)
In-Reply-To: <1a1c0d6c-1ec4-6283-053e-e9190a57316c@inventati.org>
On 28/01/22 11:22, Manuel Uberti wrote:
> I rebuilt Emacs, because I think I built it without the
> --with-native-compilation flag before to get it to work.
>
> Having it correctly build, from 'emacs -Q' the value of
> native-comp-eln-load-path is the following:
>
> ("/home/manuel/.emacs.d/eln-cache/" "/usr/local/lib/emacs/29.0.50/native-lisp/")
Since the value of native-comp-eln-load-path is correct when starting Emacs with
'emacs -Q', I bisected my init.el and I found out that when I comment out the
following lines:
(defun mu-delight-mode-line ()
"Hide minor modes in the mode-line."
(delight '((abbrev-mode nil abbrev)
(auto-fill-function nil t)
(auto-revert-mode nil autorevert)
(buffer-face-mode nil face-remap)
(eldoc-mode nil eldoc)
(envrc-mode nil envrc)
(flymake-mode nil flymake)
(flyspell-mode nil flyspell)
(subword-mode nil subword))))
(add-hook 'window-setup-hook #'mu-delight-mode-line)
And restart Emacs, the problem disappears and the value for
native-comp-eln-load-path is correctly set to:
("/home/manuel/.emacs.d/eln-cache/" "/usr/local/lib/emacs/29.0.50/native-lisp/")
The problem seems then to be related to the delight package[1] and/or how I set
it up.
[1] https://elpa.gnu.org/packages/delight.html
--
Manuel Uberti
www.manueluberti.eu
next prev parent reply other threads:[~2022-01-28 10:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 6:42 bug#53596: 29.0.50; comp-trampoline-compile: Cannot find suitable directory for output in `native-comp-eln-load-path' Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-28 9:50 ` Andrea Corallo
2022-01-28 9:52 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-28 9:57 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-28 10:06 ` Andrea Corallo
2022-01-28 10:09 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-28 10:10 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-28 10:22 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-28 10:32 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-01-28 13:00 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-28 13:33 ` Andrea Corallo
2022-01-28 13:49 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-28 13:55 ` Andrea Corallo
2022-01-28 14:03 ` Lars Ingebrigtsen
2022-01-28 14:18 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-28 14:27 ` Lars Ingebrigtsen
2022-01-28 16:53 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-28 19:07 ` Michael Heerdegen
2022-01-29 7:41 ` Andrea Corallo
2022-01-29 17:36 ` Michael Heerdegen
2022-01-29 17:55 ` Eli Zaretskii
2022-01-30 1:26 ` Michael Heerdegen
2022-01-30 6:45 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=74292753-93b6-abb1-4a3c-7e1d1f50724b@inventati.org \
--to=bug-gnu-emacs@gnu.org \
--cc=53596@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=manuel.uberti@inventati.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).