From: Thierry Volpiatto <thievol@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: psainty@orcon.net.nz, 46790@debbugs.gnu.org,
Andrea Corallo <akrl@sdf.org>
Subject: bug#46790: 28.0.50; make install with native-comp branch
Date: Sat, 24 Apr 2021 12:21:56 +0000 [thread overview]
Message-ID: <877dkreudx.fsf@posteo.net> (raw)
In-Reply-To: <83v98cm6en.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1837 bytes --]
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Sat, 24 Apr 2021 10:49:07 +0300
>> From: Eli Zaretskii <eliz@gnu.org>
>> Cc: psainty@orcon.net.nz, 46790@debbugs.gnu.org
>>
>> . where is the _real_ Emacs executable?
>> . where is the symlink to it?
>> . are you invoking the symlink explicitly or via PATH?
>> . where is the .pdmp file?
>> . where is the installed native-lisp/ directory?
>
> Also I've now tried to improve the diagnostics when Emacs fails to
> find the *.eln files, so please report what it says when it fails.
As I said before I found this bug when using dired-async-mode from
emacs-async package. When trying to copy a file nothing happened, no
child emacs process was made. As soon I symlinked the native-lisp/
directory in /usr/local/sbin dired-async started working, now it is no
more working symlink or not, I guess emacs --batch is not finding the
necessary libraries to start, but now unsure.
> In addition: you said earlier:
>
>> Emacs IS starting though but is not finding needed libraries.
>
> Maybe I misunderstand the problem. Your original report quoted error
> messages like these:
>
>> thierry <at> IPadS340:/usr/local/sbin/emacs-28.0.50$ ./emacs-28.0.50
>> emacs: /usr/local/sbin/emacs-28.0.50/../native-lisp/28.0.50-40158ec0/window-0d1b8b93-738411b0.eln: cannot open shared object file: No such file or directory
>> thierry <at> IPadS340:/usr/local/sbin/emacs-28.0.50$ ./emacs
>> emacs: /usr/local/sbin/emacs-28.0.50/../native-lisp/28.0.50-40158ec0/window-0d1b8b93-738411b0.eln: cannot open shared object file: No such file or directory
Yes I sent this because I thought it was a straight forward way to show
the problem, however the strange thing was emacs was starting with no
apparent errors from its symlink in /usr/local/bin/
--
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 686 bytes --]
next prev parent reply other threads:[~2021-04-24 12:21 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 7:35 bug#46790: 28.0.50; make install with native-comp branch Thierry Volpiatto
2021-04-09 18:56 ` Eli Zaretskii
2021-04-10 5:17 ` Thierry Volpiatto
2021-04-10 7:37 ` Eli Zaretskii
2021-04-10 6:57 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-10 7:50 ` Eli Zaretskii
2021-04-10 16:30 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-10 13:46 ` Thierry Volpiatto
2021-04-10 16:25 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-10 17:55 ` Thierry Volpiatto
2021-04-13 12:37 ` bug#46790: 28.0.50; [native-comp] Emacs doesn't start when run from a symlink Phil Sainty
2021-04-13 13:55 ` Eli Zaretskii
2021-04-14 9:50 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-20 9:33 ` bug#46790: 28.0.50; make install with native-comp branch Phil Sainty
2021-04-20 11:39 ` Eli Zaretskii
2021-04-24 6:48 ` Thierry Volpiatto
2021-04-24 7:49 ` Eli Zaretskii
2021-04-24 8:30 ` Eli Zaretskii
2021-04-24 12:21 ` Thierry Volpiatto [this message]
2021-04-24 12:40 ` Eli Zaretskii
2021-04-24 12:47 ` Thierry Volpiatto
2021-04-24 13:33 ` Eli Zaretskii
2021-04-24 13:39 ` Eli Zaretskii
2021-04-24 13:58 ` Thierry Volpiatto
2021-04-24 14:09 ` Eli Zaretskii
2021-04-24 15:22 ` Thierry Volpiatto
2021-04-24 16:00 ` Eli Zaretskii
2021-04-24 16:20 ` Thierry Volpiatto
2021-04-24 16:52 ` Eli Zaretskii
2021-04-24 17:35 ` Thierry Volpiatto
2021-04-25 13:14 ` Thierry Volpiatto
2021-04-25 13:28 ` Eli Zaretskii
2021-04-25 14:02 ` Thierry Volpiatto
2021-04-25 14:37 ` Eli Zaretskii
2021-04-25 14:28 ` Phil Sainty
2021-04-25 15:24 ` Eli Zaretskii
2021-04-25 18:21 ` Thierry Volpiatto
2021-04-25 18:38 ` Eli Zaretskii
2021-04-25 19:50 ` Thierry Volpiatto
2021-04-27 11:16 ` Thierry Volpiatto
2022-06-19 13:56 ` Lars Ingebrigtsen
2022-06-19 16:20 ` Thierry Volpiatto
2022-06-19 16:25 ` Lars Ingebrigtsen
2021-04-24 17:00 ` Eli Zaretskii
2021-04-24 17:39 ` Thierry Volpiatto
2021-04-24 17:47 ` Eli Zaretskii
2021-04-24 18:06 ` Thierry Volpiatto
2021-04-24 18:48 ` Eli Zaretskii
2021-04-25 4:29 ` Thierry Volpiatto
2021-04-25 8:21 ` Eli Zaretskii
2021-04-25 12:07 ` Thierry Volpiatto
2021-04-25 12:21 ` Eli Zaretskii
2021-04-25 15:19 ` Thierry Volpiatto
2021-04-24 13:03 ` Eli Zaretskii
2021-04-24 11:11 ` Thierry Volpiatto
2021-04-24 11:56 ` Eli Zaretskii
2021-04-24 12:04 ` Thierry Volpiatto
2021-04-24 12:29 ` Eli Zaretskii
2021-04-24 11:59 ` Phil Sainty
2021-04-24 6:40 ` Thierry Volpiatto
2022-06-26 5:39 ` bug#46790: 28.1; Bug#46790 reintroduced; Was make install with native-comp Thierry Volpiatto
2022-06-26 5:52 ` Eli Zaretskii
2022-06-26 9:30 ` Eli Zaretskii
2022-06-26 14:19 ` Thierry Volpiatto
2022-06-26 14:52 ` Eli Zaretskii
2022-06-27 10:14 ` Thierry Volpiatto
2022-06-27 11:19 ` Eli Zaretskii
2022-06-27 12:59 ` Eli Zaretskii
2022-06-27 13:46 ` Thierry Volpiatto
2022-06-26 14:10 ` Thierry Volpiatto
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=877dkreudx.fsf@posteo.net \
--to=thievol@posteo.net \
--cc=46790@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=eliz@gnu.org \
--cc=psainty@orcon.net.nz \
/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).