From: Lele Gaifax <lele@metapensiero.it>
To: emacs-devel@gnu.org
Subject: Re: Default value of native-comp-eln-load-path
Date: Thu, 13 Jan 2022 14:49:51 +0100 [thread overview]
Message-ID: <87a6fzd9ts.fsf@metapensiero.it> (raw)
In-Reply-To: 83zgo02ds1.fsf@gnu.org
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Lele Gaifax <lele@metapensiero.it>
>> Date: Thu, 13 Jan 2022 08:52:21 +0100
>>
>> on a self-compiled one-week old GNU/Emacs (commit 808f69bf), I see
>> the following:
>>
>> $ cd $HOME; emacs --batch --execute "(print native-comp-eln-load-path)"
>>
>> ("/home/lele/.emacs.d/eln-cache/" "/home/native-lisp/")
>>
>> $ cd /tmp; emacs --batch --execute "(print native-comp-eln-load-path)"
>>
>> ("/home/lele/.emacs.d/eln-cache/" "/native-lisp/")
>
> Is this an installed Emacs, i.e. did you "make install" after building
> it?
Yes, sure.
>> Indeed, that variable is defined in src/comp.c as
>>
>> /* Temporary value in use for bootstrap. We can't do better as
>> `invocation-directory' is still unset, will be fixed up during
>> dump reload. */
>> Vnative_comp_eln_load_path = Fcons (build_string ("../native-lisp/"), Qnil);
>>
>> What is the purpose of that relative "native-lisp" entry?
>
> It's complicated to explain (but the reasons are valid). In any case,
> as the comment says, the value is supposed to be resolved when Emacs
> loads the .pdmp file. Why it didn't happen in your case requires more
> investigation.
I will try to understand why it doesn't happen in my case, first of all
locating where that resolution should happen.
Thanks&bye, lele.
--
nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri
real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia.
lele@metapensiero.it | -- Fortunato Depero, 1929.
next prev parent reply other threads:[~2022-01-13 13:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 7:52 Default value of native-comp-eln-load-path Lele Gaifax
2022-01-13 9:19 ` Eli Zaretskii
2022-01-13 13:49 ` Lele Gaifax [this message]
2022-01-13 14:05 ` 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=87a6fzd9ts.fsf@metapensiero.it \
--to=lele@metapensiero.it \
--cc=emacs-devel@gnu.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.