From: Richard Stallman <rms@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 34707@debbugs.gnu.org
Subject: bug#34707: Failure to find the associated pdump file
Date: Mon, 17 Jun 2019 23:07:32 -0400 [thread overview]
Message-ID: <E1hd4T6-00079B-Cr@fencepost.gnu.org> (raw)
In-Reply-To: <m3fto8ca7m.fsf@gnus.org> (message from Lars Ingebrigtsen on Mon, 17 Jun 2019 20:56:13 +0200)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> Running ~/src/emacs/trunk/src/emacs directly works, but it's not
> uncommon to have symlinks to the binary (somebody else just complained
> to me about this)... When Emacs is able to find the rest of itself,
> it's odd that it's not finding the pdump file, surely?
The code to find the Lisp files handles the symlink case,
and it still works just as it has worked for years.
However, finding the pdump file uses new code,
and that code doesn't try to handle this symlink case.
--
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2019-06-18 3:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-02 3:27 bug#34707: Failure to find the associated pdump file Richard Stallman
2019-03-02 7:11 ` Eli Zaretskii
2019-03-03 2:58 ` Richard Stallman
2019-03-03 3:45 ` Eli Zaretskii
2019-03-04 3:28 ` Richard Stallman
2019-03-03 2:58 ` Richard Stallman
2019-03-03 3:41 ` Eli Zaretskii
2019-03-03 17:08 ` Eli Zaretskii
2019-03-04 3:26 ` Richard Stallman
2019-03-04 3:36 ` Eli Zaretskii
2019-03-03 17:06 ` Eli Zaretskii
2019-06-17 18:56 ` Lars Ingebrigtsen
2019-06-17 19:23 ` Eli Zaretskii
2019-06-18 3:07 ` Richard Stallman [this message]
2019-06-28 6:42 ` 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=E1hd4T6-00079B-Cr@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=34707@debbugs.gnu.org \
--cc=larsi@gnus.org \
/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).