From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Alan Third <alan@idiocy.org>
Cc: bryan.m.obrien@gmail.com, Eli Zaretskii <eliz@gnu.org>,
47558@debbugs.gnu.org
Subject: bug#47558: 28.0.50; dlopen 'image not found' gccemacs native-lisp macos
Date: Tue, 06 Apr 2021 07:56:46 +0000 [thread overview]
Message-ID: <xjfsg43j16p.fsf@sdf.org> (raw)
In-Reply-To: <YGt9muDKR3kwwFWd@breton.holly.idiocy.org> (Alan Third's message of "Mon, 5 Apr 2021 22:14:02 +0100")
Alan Third <alan@idiocy.org> writes:
> On Mon, Apr 05, 2021 at 08:21:25PM +0000, Andrea Corallo wrote:
>> Alan Third <alan@idiocy.org> writes:
>>
>> > On Sun, Apr 04, 2021 at 07:10:50AM +0000, Andrea Corallo wrote:
>> >> Eli Zaretskii <eliz@gnu.org> writes:
>> >>
>> >> >> Date: Sat, 3 Apr 2021 15:01:20 +0100
>> >> >> From: Alan Third <alan@idiocy.org>
>> >> >> Cc: bryan.m.obrien@gmail.com, 47558@debbugs.gnu.org
>> >> >>
>> >> >> 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?
>> >> >
>> >> > I hope Andrea (CC'ed) will be able to answer that.
>> >>
>> >> Okay, as window is loaded and dumped during the build
>> >> `comp-eln-load-path' here doesn't come into play.
>> >>
>> >> While resurrecting from dump we locate preloaded eln files by filename
>> >> (relative to the emacs executable position). Indeed the complication is
>> >> that we have to support both uninstalled but also installed builds.
>> >>
>> >> To do that before dumping we inform Emacs of where will have to search
>> >> the eln files if installed. We do that using ELN_DESTDIR defined
>> >> Makefile.in:326.
>> >>
>> >> If the directory structure on MacOS is different I guess we have to add
>> >> the correct information there.
>> >
>> > No matter what I set ELN_DESTDIR to, emacs still looks in
>> >
>> > /Users/alan/src/emacs/native/nextstep/Emacs.app/Contents/MacOS/../native-lisp/28.0.50-24e3df15
>> >
>> > so something isn't being updated, I guess?
>>
>> That's possible, could you specify the full procedure you've used to
>> reach this point?
>
> ./autogen.sh
> ./configure --with-ns --with-native-compilation
> make
> make install
>
> Note: make install fails, I've had to apply this patch
>
>
> @@ -749,7 +753,8 @@ install-etc:
> ### Install native compiled Lisp files.
> install-eln:
> ifeq ($(HAVE_NATIVE_COMP),yes)
> - find native-lisp -type f -exec ${INSTALL_DATA} -D "{}" "$(ELN_DESTDIR){}" \;
> + find native-lisp -type d -exec $(MKDIR_P) "$(ELN_DESTDIR){}" \; ; \
> + find native-lisp -type f -exec ${INSTALL_DATA} "{}" "$(ELN_DESTDIR){}" \;
> endif
>
>
> but if you were to try this with GNUstep I suspect that wouldn't be
> needed.
>
> And I've tried modifying ELN_DESTDIR with this
>
>
> @@ -323,7 +323,11 @@ CONFIG_STATUS_FILES_IN =
> COPYDIR = ${srcdir}/etc ${srcdir}/lisp
> COPYDESTS = "$(DESTDIR)${etcdir}" "$(DESTDIR)${lispdir}"
>
> -ELN_DESTDIR = $(DESTDIR)${libdir}/emacs/${version}/
> +ifeq (${ns_self_contained},no)
> + ELN_DESTDIR = $(DESTDIR)${libdir}/emacs/${version}/
> +else
> + ELN_DESTDIR = ${ns_appresdir}/
> +endif
>
> all: ${SUBDIR} info
>
>
> which results in the .eln files being installed where I want, but
> running the installed Emacs (nextstep/Emacs.app/MacOS/Emacs) still
> gives the error
>
> emacs:
> dlopen(/Users/alan/src/emacs/native/nextstep/Emacs.app/Contents/MacOS/../native-lisp/28.0.50-24e3df15/window-0d1b8b93-513ac8ca.eln,
> 1): image not found
Hi Alan,
Okay the value of ELN_DESTDIR is used during dump to inform Emacs where
the eln will be located (src/Makefile.in:570) so redumping is necessary.
Have you tried redumping or rebuilding from scratch?
Thanks!
Andrea
next prev parent reply other threads:[~2021-04-06 7:56 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
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 [this message]
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=xjfsg43j16p.fsf@sdf.org \
--to=bug-gnu-emacs@gnu.org \
--cc=47558@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=alan@idiocy.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).