From: Alan Third <alan@idiocy.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: bryan.m.obrien@gmail.com, 47558@debbugs.gnu.org
Subject: bug#47558: 28.0.50; dlopen 'image not found' gccemacs native-lisp macos
Date: Sat, 3 Apr 2021 15:01:20 +0100 [thread overview]
Message-ID: <YGh1MNuSVHfZSCw5@breton.holly.idiocy.org> (raw)
In-Reply-To: <83y2dzev4b.fsf@gnu.org>
On Sat, Apr 03, 2021 at 09:32:20AM +0300, Eli Zaretskii wrote:
> > Date: Fri, 2 Apr 2021 22:51:56 +0100
> > From: Alan Third <alan@idiocy.org>
> > Cc: bryan.m.obrien@gmail.com, 47558@debbugs.gnu.org
> >
> > I think I've figured that out, but there's actually another wrinkle.
> > 'make install' is installing the eln files in
> >
> > nextstep/Emacs.app/Contents/MacOS/lib/emacs/28.0.50/native-lisp/28.0.50-24e3df15
> >
> > but the emacs executable is looking for them in
> >
> > nextstep/Emacs.app/Contents/MacOS/../native-lisp/28.0.50-24e3df15/
>
> The above happens on all platforms, so it isn't macOS specific, right?
> Or are you saying there's something macOS specific in ${libdir}? in
> the latter case, what's the story there?
I think that is what happens on other platforms, but the issue here is
that the emacs executable is placed in an unusual position relative to
the other files because of the NS app bundle format. I'll try to
explain it below, but my knowledge is not deep.
> > And just to add the confusion I feel they should *actually* be
> > installed in
> >
> > nextstep/Emacs.app/Contents/Resources/native-lisp
> >
> > or similar.
>
> Why is that?
NS uses a special directory structure that appears to the system as an
application. It looks something like this:
Emacs.app
+ Contents
+ MacOS
| + Emacs <-- The executable
+ Resources
| + icons
| + etc
| + include
| + info
| + lisp
| + ...
+ Info.plist
+ ...
The layout is ever so slightly different under GNUstep.
As far as I can tell the only thing that should be in the
Contents/MacOS directory are executables, practically everything else
lives under Resources.
nsterm.m has three functions for finding the correct path for etc,
exec and the lisp load path. I imagine what we want to do is install
the eln files under Resources, then add a new function that returns the
location of them and use it to set the correct path at the point where
Emacs loads the files.
It's not entirely clear to me where the load path is set, is it
fixup_eln_load_path (Lisp_Object directory)
in comp.c?
--
Alan Third
next prev parent reply other threads:[~2021-04-03 14:01 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 1:36 bug#47558: 28.0.50; dlopen 'image not found' gccemacs native-lisp macos Bryan O'Brien
2021-04-02 5:46 ` Eli Zaretskii
2021-04-02 16:29 ` Alan Third
2021-04-02 18:39 ` Eli Zaretskii
2021-04-02 21:51 ` Alan Third
2021-04-03 6:32 ` Eli Zaretskii
2021-04-03 14:01 ` Alan Third [this message]
2021-04-03 14:17 ` Eli Zaretskii
2021-04-04 7:10 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-05 10:34 ` Alan Third
2021-04-05 20:21 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-05 21:14 ` Alan Third
2021-04-06 7:56 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-06 10:00 ` Alan Third
2021-04-06 14:51 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-06 17:36 ` Alan Third
2021-04-06 19:26 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-06 21:11 ` Alan Third
2021-04-06 21:22 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-06 21:33 ` Alan Third
2021-04-07 2:08 ` Bryan O'Brien
2021-04-07 7:53 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-07 8:18 ` Alan Third
2021-04-07 9:08 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-07 9:58 ` Alan Third
2021-04-07 10:31 ` Andreas Schwab
2021-04-07 10:35 ` Andreas Schwab
2021-04-07 10:48 ` Alan Third
2021-04-07 11:50 ` Eli Zaretskii
2021-04-07 12:15 ` Eli Zaretskii
2021-04-07 12:31 ` Alan Third
2021-04-07 11:45 ` Eli Zaretskii
2021-04-07 14:20 ` Alan Third
2021-04-07 14:25 ` Eli Zaretskii
2021-04-07 18:41 ` Bryan O'Brien
2021-04-07 18:45 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-07 16:46 ` Eli Zaretskii
2021-04-07 18:30 ` Bryan O'Brien
2021-04-07 18:43 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=YGh1MNuSVHfZSCw5@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--cc=47558@debbugs.gnu.org \
--cc=bryan.m.obrien@gmail.com \
--cc=eliz@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).