From: Eli Zaretskii <eliz@gnu.org>
To: Spencer Baugh <sbaugh@janestreet.com>
Cc: 73318@debbugs.gnu.org, larsi@gnus.org, acorallo@gnu.org,
schwab@linux-m68k.org, shipmints@gmail.com
Subject: bug#73318: 31.0.50; with-native-compilation=aot breaks exec -a emacs
Date: Fri, 04 Oct 2024 22:16:57 +0300 [thread overview]
Message-ID: <86a5fjy8ye.fsf@gnu.org> (raw)
In-Reply-To: <ieriku7zu8g.fsf@janestreet.com> (message from Spencer Baugh on Fri, 04 Oct 2024 12:51:59 -0400)
> From: Spencer Baugh <sbaugh@janestreet.com>
> Cc: 73318@debbugs.gnu.org, larsi@gnus.org, acorallo@gnu.org,
> schwab@linux-m68k.org, shipmints@gmail.com
> Date: Fri, 04 Oct 2024 12:51:59 -0400
>
> Yes. I suggest that if installation_state == INSTALLED, and we fail to
> find an eln file in emacs_execdir, we fall back to look in PATH_EXEC (or
> some other path compiled into the Emacs binary).
Btw, this is a misunderstanding of the code's logic: you must do this
when installation_state == UNKNOWN. When it's INSTALLED, it means we
already found the first .eln file we needed to load in the
installation tree.
next prev parent reply other threads:[~2024-10-04 19:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 15:18 bug#73318: 31.0.50; with-native-compilation=aot breaks exec -a emacs Spencer Baugh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-17 15:40 ` Spencer Baugh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-17 17:47 ` Eli Zaretskii
2024-09-17 18:14 ` Ship Mints
2024-09-17 19:07 ` Eli Zaretskii
2024-09-17 19:22 ` Ship Mints
2024-09-17 19:31 ` Eli Zaretskii
2024-09-17 22:31 ` Spencer Baugh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-17 22:45 ` Ship Mints
2024-09-18 13:11 ` Eli Zaretskii
2024-09-19 3:09 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-19 12:54 ` Ship Mints
2024-09-19 13:44 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-19 13:51 ` Ship Mints
2024-09-19 15:45 ` Eli Zaretskii
2024-10-04 12:09 ` Spencer Baugh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-04 12:51 ` Eli Zaretskii
2024-10-04 13:22 ` Spencer Baugh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-04 13:57 ` Eli Zaretskii
2024-10-04 14:02 ` shipmints
2024-10-04 16:51 ` Spencer Baugh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-04 19:09 ` Eli Zaretskii
2024-10-07 14:18 ` Spencer Baugh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-07 18:44 ` Eli Zaretskii
2024-10-07 20:16 ` Spencer Baugh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-08 11:47 ` Eli Zaretskii
2024-10-08 12:16 ` Eli Zaretskii
2024-10-04 19:16 ` Eli Zaretskii [this message]
2024-10-08 23:35 ` Stefan Kangas
2024-10-09 12:13 ` 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=86a5fjy8ye.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=73318@debbugs.gnu.org \
--cc=acorallo@gnu.org \
--cc=larsi@gnus.org \
--cc=sbaugh@janestreet.com \
--cc=schwab@linux-m68k.org \
--cc=shipmints@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).