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 10:57:36 +0100 [thread overview]
Message-ID: <f8365254-d3f6-4aad-71f4-8efa08c9ffe6@inventati.org> (raw)
In-Reply-To: <baf2ed47-c403-b7ed-1ccc-3d4ed2329aa5@inventati.org>
On 28/01/22 10:52, Manuel Uberti wrote:
> On 28/01/22 10:50, Andrea Corallo wrote:
>> Hi Manuel,
>
> Hi Andrea, thank you for the quick reply.
>
>> in `native-comp-eln-load-path' you should have a directory where emacs
>> can create and depose files in order to work correctly.
>>
>> Your `native-comp-eln-load-path' should look more something like:
>>
>> ("/home/manuel/.emacs.d/eln-cache/"
>> "/usr/local/libexec/emacs/29.0.50/x86_64-pc-linux-gnu/../../../../bin/../lib/emacs/29.0.50/native-lisp/")
>>
>>
>> Are you modifying `native-comp-eln-load-path' in your configuration?
One more thing: the directory '/home/manuel/.emacs.d/eln-cache' exists and it's
content are many '28.0.50-*' and '29.0.50-*' directories.
--
Manuel Uberti
www.manueluberti.eu
next prev parent reply other threads:[~2022-01-28 9:57 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 [this message]
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
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=f8365254-d3f6-4aad-71f4-8efa08c9ffe6@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).