bug#44128: closed ([feature/native-comp]; When invoking a symlink to the 'emacs' binary Emacs fails to start)

[GNU bug Tracking System]

Your message dated Mon, 19 Apr 2021 17:52:02 +0300
with message-id <83im4is4x9.fsf@gnu.org>
and subject line Re: bug#47800: bug#44128: [feature/native-comp] When invoking 
a symlink to the 'emacs' binary Emacs fails to start
has caused the debbugs.gnu.org bug report #44128,
regarding [feature/native-comp]; When invoking a symlink to the 'emacs' binary 
Emacs fails to start
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
44128: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=44128
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> [feature/native-comp] 
>
>
>
>
> Date: 
>
> Wed, 21 Oct 2020 23:58:59 +0200
>
>
>
>
> Hello Andrea
>
> [We talked about this briefly on Twitter;
>  https://twitter.com/magit_emacs/status/1313534891506757635.]
>
> When running gccemacs from the git repository without installing but by
> using a symlink like e.g. /usr/local/bin/emacs -> ~/git/emacs/src/emacs,
> then that results in an error like:
>
>   emacs: /usr/local/bin/../native-lisp/<snip>.eln: cannot open shared
>   object file: No such file or directory
>
> You mentioned that this happens because code in pdump[er].c just relies
> on invocation-directory and that you are wonder whether symlinks should
> be followed to address this.
>
>   I think they should. :D
>   Please have a look.
>   Thanks!
>   Jonas
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#47800: bug#44128: [feature/native-comp] When invoking a symlink to the 'emacs' binary Emacs fails to start
>
>
>
>
> Date: 
>
> Mon, 19 Apr 2021 17:52:02 +0300
>
>
>
>
> > >> This time it compiled; but with the following warnings, and
> > >> when I run it from the installed location (whether using the
> > >> absolute path or a symlink) I get a seg fault / core dump:
> > >
> > > Sorry about that.  Next try, please.
> > 
> > Now it works for me too.
> > Thanks!
>
> Thanks, so I think we can close this issue now.  Thanks to everybody
> who reported their results and tried my buggy code.
>
>
> --- End Message ---