From: Eli Zaretskii <eliz@gnu.org>
To: akrl@sdf.org
Cc: 51999@debbugs.gnu.org
Subject: bug#51999: 28.0.60; temacs with native-compilation fails unless invoked from src
Date: Sat, 20 Nov 2021 17:12:03 +0200 [thread overview]
Message-ID: <83k0h2svy4.fsf@gnu.org> (raw)
In-Reply-To: <83o86esxs9.fsf@gnu.org> (message from Eli Zaretskii on Sat, 20 Nov 2021 16:32:22 +0200)
> . On GNU/Linux:
>
> - cd src && ./temacs -Q -nw works as expected
> - ./src/temacs -Q -nw fails with this error message:
>
> Symbol's function definition is void: internal-echo-keystrokes-prefix
>
> . On MS-Windows:
>
> - cd src && ./temacs -Q -nw works as expected
> - ./src/temacs -Q -nw works, but loads *.elc files instead of *.eln
>
> In all the cases, temacs was invoked from the build directory. I
> don't understand why the different behavior. Any ideas?
Answering myself: here's the reason:
DEFVAR_LISP ("native-comp-eln-load-path", Vnative_comp_eln_load_path,
doc: /* List of eln cache directories.
If a directory is non absolute is assumed to be relative to
`invocation-directory'.
`comp-native-version-dir' value is used as a sub-folder name inside
each eln cache directory.
The last directory of this list is assumed to be the system one. */);
/* 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);
So invoking temacs from any directory that is not a sibling of
native-lisp will fail to find the *.eln files.
next prev parent reply other threads:[~2021-11-20 15:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-20 14:32 bug#51999: 28.0.60; temacs with native-compilation fails unless invoked from src Eli Zaretskii
2021-11-20 15:12 ` Eli Zaretskii [this message]
2021-11-20 16:26 ` 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=83k0h2svy4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=51999@debbugs.gnu.org \
--cc=akrl@sdf.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).