bug#47825: closed (Bug calling emacs from terminal)

[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 #47800,
regarding Bug calling emacs from terminal
to be marked as done.

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


-- 
47800: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=47800
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

--- Begin Message --- Subject: Bug calling emacs from terminal Date: Fri, 16 Apr 2021 11:08:54 +0000

I am having this problem:

jorge@debian:~$ emacs

emacs: could not resolve realpath of "emacs": No such file or directory

My tests run without issue

jorge@debian:~$ echo $PATH
/home/jorge/.local/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games

jorge@debian:~$ /usr/local/bin/emacs --version       
GNU Emacs 28.0.50
Copyright (C) 2021 Free Software Foundation, Inc.
GNU Emacs comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of GNU Emacs
under the terms of the GNU General Public License.
For more information about these matters, see the file named COPYING.

Emacs has been compiled from source and installed the last version in emacs-mirror https://github.com/emacs-mirror/emacs using --feature-comp and --with-x-toolkit=lucid as configure flags.

Thanks.

--- 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 ---