unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: jonas@bernoul.li, psainty@orcon.net.nz, wilde@sha-bang.de,
	Dario Gjorgjevski <dario.gjorgjevski@gmail.com>
Cc: 44128@debbugs.gnu.org, 47800@debbugs.gnu.org, akrl@sdf.org
Subject: bug#44128: [feature/native-comp] When invoking a symlink to the 'emacs' binary Emacs fails to start
Date: Sat, 17 Apr 2021 16:58:40 +0300	[thread overview]
Message-ID: <83a6pxvwq7.fsf@gnu.org> (raw)
In-Reply-To: <83sg3qw9m7.fsf@gnu.org> (message from Eli Zaretskii on Fri, 16 Apr 2021 18:08:00 +0300)

> Date: Fri, 16 Apr 2021 18:08:00 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: psainty@orcon.net.nz, akrl@sdf.org, 44128@debbugs.gnu.org, eli@gnu.org
> 
> > From: Jonas Bernoulli <jonas@bernoul.li>
> > Date: Fri, 16 Apr 2021 15:21:47 +0200
> > Cc: 44128@debbugs.gnu.org, eli@gnu.org
> > 
> > Andrea Corallo <akrl@sdf.org> writes:
> > 
> > > I've pushed 0c1fc9d581 that seams to work for me, please have a try.
> > 
> > Unfortunately this still doesn't work (as of f9c1008ced):
> > 
> >   $ emacs
> >   emacs: could not resolve realpath of "emacs": No such file or directory
> >   $ which emacs
> >   /usr/local/bin/emacs
> >   $ ls -l /usr/local/bin/emacs
> >   lrwxrwxrwx 1 root staff 55 Apr 16 14:51 /usr/local/bin/emacs -> /home/jonas/git/src/emacs/feature
> > 
> > But this works:
> > 
> >   $ /home/jonas/git/src/emacs/feature/native-comp/src/emacs
> > 
> > And so does:
> > 
> >   $ cat /usr/local/bin/emacs
> >   #!/bin/sh
> >   /home/jonas/git/src/emacs/feature/native-comp/src/emacs "$@"
> >   $ emacs
> 
> Thanks, I think I understand the issues, and I'm working on a fix.

Please try the latest native-comp branch.  If it still doesn't solve
the problem with installing Emacs via symlinks, or if there are some
adverse side-effects of the changes I made, please report the details.

In a nutshell, Emacs should now decide where to look for its pdumper
file and where to look for the *.eln files in a synchronized manner.
I hope I got all the varieties of the symlinks involved correctly (but
I couldn't test all the possible variants, only some of them).

Please be sure to test both installed and uninstalled binaries, and
please verify that comp-eln-load-path has the right value after Emacs
loads in both cases (the last element of the list should in each case
reflect where the *.eln files will be looked for).

TIA





  reply	other threads:[~2021-04-17 13:58 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-21 21:58 bug#44128: [feature/native-comp] Jonas Bernoulli
2020-10-22 20:51 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-14 13:48   ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-14 17:28     ` Johannes Grødem
2021-04-14 22:22     ` Phil Sainty
2021-04-15  6:52       ` Eli Zaretskii
2021-04-15 12:12         ` Phil Sainty
2021-04-15 12:29           ` Eli Zaretskii
2021-04-15 13:01           ` Phil Sainty
2021-04-15 13:52             ` Eli Zaretskii
2021-04-15 14:05               ` Phil Sainty
2021-04-15 14:42                 ` Eli Zaretskii
2021-04-15 21:52                   ` Phil Sainty
2021-04-16  6:50                     ` Eli Zaretskii
2021-04-16 12:04                       ` Phil Sainty
2021-04-16 12:20                         ` Eli Zaretskii
2021-04-16 12:59                           ` Phil Sainty
2021-04-16 13:21     ` Jonas Bernoulli
2021-04-16 15:08       ` Eli Zaretskii
2021-04-17 13:58         ` Eli Zaretskii [this message]
2021-04-17 14:13           ` bug#44128: bug#47800: bug#44128: [feature/native-comp] When invoking a symlink to the 'emacs' binary Emacs fails to start Phil Sainty
2021-04-17 14:29             ` Eli Zaretskii
2021-04-17 15:00               ` Phil Sainty
2021-04-17 15:12                 ` Eli Zaretskii
2021-04-17 15:39                   ` bug#44128: " Dario Gjorgjevski
2021-04-17 15:48                     ` Eli Zaretskii
2021-04-17 19:15                       ` wilde
2021-04-17 19:18                         ` Eli Zaretskii
2021-04-17 19:32                           ` wilde
2021-04-18  8:42                             ` Eli Zaretskii
2021-04-18  9:01                               ` Eli Zaretskii
2021-04-18 12:24                                 ` wilde
2021-04-18 13:00                                   ` Eli Zaretskii
2021-04-19 14:37                   ` Jonas Bernoulli
2021-04-19 14:52                     ` Eli Zaretskii
2021-04-18  7:40                 ` Phil Sainty
2021-04-18  8:09                   ` bug#44128: " Eli Zaretskii
2021-04-18  3:40           ` Richard Stallman
2021-04-18  6:58             ` Eli Zaretskii
2021-04-15 10:09 ` bug#44128: symlink problem after applying commit 0c1fc9d Kent Engström
2021-04-18  7:41   ` Kent Engström
2021-04-18 16:04     ` Eli Zaretskii

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=83a6pxvwq7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=44128@debbugs.gnu.org \
    --cc=47800@debbugs.gnu.org \
    --cc=akrl@sdf.org \
    --cc=dario.gjorgjevski@gmail.com \
    --cc=jonas@bernoul.li \
    --cc=psainty@orcon.net.nz \
    --cc=wilde@sha-bang.de \
    /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).