From: Eli Zaretskii <eliz@gnu.org>
To: Andrea Corallo <akrl@sdf.org>
Cc: 47987@debbugs.gnu.org, tsdh@gnu.org
Subject: bug#47987: 28.0.50; [native-comp] Can't compile ELN if EL and ELC reside in different directories
Date: Tue, 27 Apr 2021 20:41:01 +0300 [thread overview]
Message-ID: <83sg3bhbgy.fsf@gnu.org> (raw)
In-Reply-To: <xjfbl9z3bo3.fsf@sdf.org> (bug-gnu-emacs@gnu.org)
> Cc: 47987@debbugs.gnu.org
> Date: Tue, 27 Apr 2021 17:00:28 +0000
> From: Andrea Corallo via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> The trouble is that given the bytecode being loaded Emacs needs to find
> the source file, both to native compile it (if necessary) both to hash
> it in order to the locate the correct .eln file to load.
>
> Now given the .elc file removing the final 'c' was the simple algo
> applied for this scope :) But is this is not sufficient we have to
> either provide a more sophisticate mechanism so that a package can
> register a new mapping or either disable eln load for some package.
We can either (a) look in all the directories in load-path, if the .el
file is not found in the same directory as the .elc; or (b) add a new
variable a-la load-path that is only searched if the current look up
fails.
I prefer the former, unless it has some downsides.
next prev parent reply other threads:[~2021-04-27 17:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-24 7:20 bug#47987: 28.0.50; [native-comp] Can't compile ELN if EL and ELC reside in different directories Tassilo Horn
2021-04-27 17:00 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-27 17:41 ` Eli Zaretskii [this message]
2022-11-06 9:33 ` Tassilo Horn
2022-11-06 10:17 ` 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=83sg3bhbgy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=47987@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=tsdh@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 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).