From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Thierry Volpiatto <thievol@posteo.net>
Cc: 46790@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#46790: 28.0.50; make install with native-comp branch
Date: Sat, 10 Apr 2021 16:25:28 +0000 [thread overview]
Message-ID: <xjf1rbif6o7.fsf@sdf.org> (raw)
In-Reply-To: <87y2dqb67z.fsf@posteo.net> (Thierry Volpiatto's message of "Sat, 10 Apr 2021 15:46:18 +0200")
Thierry Volpiatto <thievol@posteo.net> writes:
> Andrea Corallo <akrl@sdf.org> writes:
>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>>>> From: Thierry Volpiatto <thievol@posteo.net>
>>>> Date: Fri, 26 Feb 2021 08:35:30 +0100
>>>>
>>>> giving a try to native-comp branch.
>>>>
>>>> I install Emacs generaly with:
>>>>
>>>> make install bindir=/usr/local/sbin/emacs-28.0.50 infodir=/usr/local/share/info-28.0.50
>>>>
>>>> This always worked fine. However with native-comp branch, I have to
>>>> manually add a symlink of "/usr/local/lib/emacs/28.0.50/native-lisp/" to
>>>> "/usr/local/sbin" otherwise I endup with an error:
>>>>
>>>> thierry@IPadS340:/usr/local/sbin/emacs-28.0.50$ ls
>>>> ctags ebrowse emacs emacs-28.0.50 emacsclient etags
>>>> thierry@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@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
>>>
>>> Hmm... I'm not sure we can resolve this in any other way, although we
>>> should try. What worked for you with previous versions was just a
>>> side effect of the implementation detail: how Emacs finds the files it
>>> needs when it starts. The *.eln files bring more restrictions to the
>>> table, and it could very well be that the symlink trick will be the
>>> only practical solution to such a non-standard installation.
>>>
>>> A possible solution is to set EMACSNATIVELOADPATH in the environment.
>>
>> As the error is while resurrecting from dump I think acting on the load
>> path will not help as in this phase we relocate elns simply by filename.
>>
>> Thierry, are you specifying your custom bindir only when installing or
>> also while building?
>
> Only when installing.
>
>> If the case is the first could you please try again setting bindir
>> also while building?
>
> How, is this allowed or even possible?
make bootstrap bindir=/xxx
I think ATM this should work (would be nice if you could check this),
reading Eli's opinion we may change it tho.
>> Sorry for not responding earlier, I've been in round robin on the issues
>> I had the feeling were higher priority but was still in my todo list :)
>
> No problems, congrats for the huge work.
Thanks
Andrea
next prev parent reply other threads:[~2021-04-10 16:25 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 [this message]
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
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=xjf1rbif6o7.fsf@sdf.org \
--to=bug-gnu-emacs@gnu.org \
--cc=46790@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=eliz@gnu.org \
--cc=thievol@posteo.net \
/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).