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 19:26:16 +0000 [thread overview]
Message-ID: <xjf35w3i59j.fsf@sdf.org> (raw)
In-Reply-To: <YGycD2m1fXHR8ua6@breton.holly.idiocy.org> (Alan Third's message of "Tue, 6 Apr 2021 18:36:15 +0100")
[-- Attachment #1: Type: text/plain, Size: 1780 bytes --]
Alan Third <alan@idiocy.org> writes:
> On Tue, Apr 06, 2021 at 02:51:46PM +0000, Andrea Corallo wrote:
>> Alan Third <alan@idiocy.org> writes:
>>
>> > On Tue, Apr 06, 2021 at 07:56:46AM +0000, Andrea Corallo wrote:
>> >> Alan Third <alan@idiocy.org> writes:
>> >> > 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?
>> >
>> > Yes, I've tried 'make bootstrap' to no avail.
>>
>> could you share the output of like "make bootstrap V=1"? (go parallel if
>> you like)
>
> Attached.
Okay the log looks good AFAICT.
We are suggesting the eln to go in:
/Users/alan/src/emacs/native/nextstep/Emacs.app/Contents/MacOS/bin/
and the eln in:
/Users/alan/src/emacs/native/nextstep/Emacs.app/Contents/Resources/
For each compilation unit being dumped we modify the filename in a pair
in the form of (rel-filename-from-install-bin
. rel-filename-from-local-bin) in loadup.el:467 so we'll be able to
locate those compilation units when resurecting.
So either we compute wrongly the 'rel-filename-from-install-bin' there
or something goes wrong in pdumper.c:5277 (where we use it to to
identify if Emacs was installed or not).
On this subject I just realized that there we used concat in place of
`expand-file-name' and fixed that with 6568198213.
If this does not help I suggest we apply the attached and re-bootstrap
to see if the 'rel-filename-from-install-bin' we are constructing is
correct.
Thanks!
Andrea
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: loadup.patch --]
[-- Type: text/x-diff, Size: 1562 bytes --]
diff --git a/lisp/loadup.el b/lisp/loadup.el
index 650288f9f8..3331445ff8 100644
--- a/lisp/loadup.el
+++ b/lisp/loadup.el
@@ -475,15 +475,17 @@
eln-dest-dir)))
(native-comp-unit-set-file
cu
- (cons
- ;; Relative filename from the installed binary.
- (file-relative-name (expand-file-name
- (file-name-nondirectory
- file)
- eln-dest-dir-eff)
- bin-dest-dir)
- ;; Relative filename from the built uninstalled binary.
- (file-relative-name file invocation-directory)))))
+ (let ((tmp (cons
+ ;; Relative filename from the installed binary.
+ (file-relative-name (expand-file-name
+ (file-name-nondirectory
+ file)
+ eln-dest-dir-eff)
+ bin-dest-dir)
+ ;; Relative filename from the built uninstalled binary.
+ (file-relative-name file invocation-directory))))
+ (print tmp)
+ tmp))))
h))))
(when (hash-table-p purify-flag)
next prev parent reply other threads:[~2021-04-06 19:26 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
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 [this message]
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=xjf35w3i59j.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).