all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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:22:04 +0100	[thread overview]
Message-ID: <1a1c0d6c-1ec4-6283-053e-e9190a57316c@inventati.org> (raw)
In-Reply-To: <1dfc7af5-7fba-1147-982a-a9fe688a40d6@inventati.org>

On 28/01/22 11:10, Manuel Uberti wrote:
> On 28/01/22 11:09, Manuel Uberti wrote:
>> On 28/01/22 11:06, Andrea Corallo wrote:
>>> Interesting, could you verify that with emacs -Q
>>> `native-comp-eln-load-path' is what we expect?
>>
>> I did:
>>
>> - emacs -Q
>> - C-h v native-comp-eln-load-path RET
>> - I got "Descrive varibable: native-comp-eln-load-path [No match]
>>
>>> The next question would be what is causing it to change or not to be
>>> set.
>>
>> I don't know how to answer that question, though. :)
>>
> 
> Sorry for the spelling mistakes in the previous message.
> 

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/")

-- 
Manuel Uberti
www.manueluberti.eu





  reply	other threads:[~2022-01-28 10:22 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1a1c0d6c-1ec4-6283-053e-e9190a57316c@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.