From: Eli Zaretskii <eliz@gnu.org>
To: Thierry Volpiatto <thievol@posteo.net>
Cc: psainty@orcon.net.nz, 46790@debbugs.gnu.org, akrl@sdf.org
Subject: bug#46790: 28.0.50; make install with native-comp branch
Date: Sat, 24 Apr 2021 20:00:29 +0300 [thread overview]
Message-ID: <83a6pnmxci.fsf@gnu.org> (raw)
In-Reply-To: <87im4br6ei.fsf@posteo.net> (message from Thierry Volpiatto on Sat, 24 Apr 2021 16:20:41 +0000)
Earlier you said:
> >> > . where is the .pdmp file?
> >>
> >> Didn't find such file.
> >
> > It should be under /usr/local/libexec, please try finding it.
>
> Got it.
>
> /usr/local/libexec/emacs/28.0.50/x86_64-pc-linux-gnu/emacs.pdmp
Is that the only place where you have the emacs.pdmp file that
corresponds to that Emacs binary? Or do you have another copy
somewhere else?
next prev parent reply other threads:[~2021-04-24 17:00 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83a6pnmxci.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=46790@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=psainty@orcon.net.nz \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.