From: Alan Third <alan@idiocy.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 48994@debbugs.gnu.org, Matthew Bauer <mjbauer95@gmail.com>, akrl@sdf.org
Subject: bug#48994: 28.0.50; [PATCH] 28.0.50; Native compilation unnecessarily recompiles .eln (macOS)
Date: Sun, 13 Jun 2021 17:37:55 +0100 [thread overview]
Message-ID: <YMY0Y6VQzPGXURPD@idiocy.org> (raw)
In-Reply-To: <83y2be6zj8.fsf@gnu.org>
On Sun, Jun 13, 2021 at 09:37:15AM +0300, Eli Zaretskii wrote:
> > From: Matthew Bauer <mjbauer95@gmail.com>
> > Date: Sat, 12 Jun 2021 22:13:13 -0500
> > Cc: Andrea Corallo <akrl@sdf.org>
> >
> > This is similar to bug#48497, but appears to still happen even after
> > commit 3f207753a0.
> >
> > The basic problem is that the installed lisp path does not match either
> > of the search expressions in comp-el-to-eln-rel-filename, meaning that
> > native lisp needs to be recompiled needlessly.
> >
> > The problem seems to come from PATH_REL_LOADSEARCH being set for me (on
> > macOS) to Contents/Resources/lisp, but the lisp files actually being
> > installed to
> > /nix/store/...-emacs-gcc-20210612.0/share/emacs/28.0.50/lisp (path
> > generated by Nix). As a result, comp-el-to-eln-rel-filename used the
> > filename comp-034d3699-516ce4bf.eln for comp.el.gz where 516ce4bf is the
> > md5sum of the contents of comp.el and 034d3699 is the md5sum of the full
> > path of comp.el, not of //emacs-lisp/comp.el (7672a6ed), which is what
> > Emacs installs.
> >
> > To fix this, I propose using PATH_LOADSEARCH in addition to
> > PATH_REL_LOADSEARCH so that we can catch both types of macOS installs
> > (.app and unix). I’ve attached a patch which implements this, adding
> > relative and absolute loadsearch resolution.
>
> Thanks.
>
> Alan, any comments?
I suggested previously we handle this like we do the other install
paths (see ns_etc_path, ns_exec_path and ns_load_path in nsterm.m),
but Andrea didn't like that solution.
> And could you explain to this macOS-illiterate why this mess happens
> on macOS?
It's because we support both a relocatable application format and a
normal unix style install. In the .app case the path to the installed
files has to be configured at run-time (although I think Andrea used a
directory relative to the executable), but in the unix case it's
hard-coded.
FWIW, we will have exactly the same problems with GNUstep builds,
because they use the same .app format.
--
Alan Third
next prev parent reply other threads:[~2021-06-13 16:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-13 3:13 bug#48994: 28.0.50; [PATCH] 28.0.50; Native compilation unnecessarily recompiles .eln (macOS) Matthew Bauer
2021-06-13 6:37 ` Eli Zaretskii
2021-06-13 16:37 ` Alan Third [this message]
2021-06-13 17:21 ` Eli Zaretskii
2021-06-13 19:30 ` Alan Third
2021-06-14 12:42 ` Eli Zaretskii
2021-06-14 18:32 ` Alan Third
2021-06-14 19:19 ` Eli Zaretskii
2021-06-16 18:25 ` Alan Third
2021-06-16 18:45 ` Eli Zaretskii
2021-06-19 17:04 ` Alan Third
2021-06-22 3:55 ` Matthew Bauer
2021-06-22 8:32 ` Alan Third
2021-06-22 16:51 ` Matthew Bauer
2021-06-22 16:59 ` Alan Third
2021-06-22 17:24 ` Alan Third
2021-06-22 23:01 ` Matthew Bauer
2021-06-23 15:59 ` Alan Third
2021-06-23 20:46 ` Matthew Bauer
2021-06-23 20:48 ` Alan Third
2021-06-26 9:38 ` Alan Third
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=YMY0Y6VQzPGXURPD@idiocy.org \
--to=alan@idiocy.org \
--cc=48994@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=eliz@gnu.org \
--cc=mjbauer95@gmail.com \
/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).