From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 36369@debbugs.gnu.org
Subject: bug#36369: Master doesn't use its pdump
Date: Sat, 29 Jun 2019 23:15:27 -0400 [thread overview]
Message-ID: <E1hhQJL-0004oR-0K@fencepost.gnu.org> (raw)
In-Reply-To: <83d0iwhnhn.fsf@gnu.org> (message from Eli Zaretskii on Sat, 29 Jun 2019 10:14:28 +0300)
[[[ 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. ]]]
> > Makefile seems not to have a separate rule for the file
> > 'emacs.pdump'. It treats that as an aspect of 'emacs'. Thus, the
> > 'emacs' rule should write 'emacs.pdmp' correctly too.
> I think this is problematic because we still support the unexec build
> as well. That build doesn't produce emacs.pdmp at all.
I don't see that it would be problematic. In a pdump build,
it would write emacs.pdmp. In an unexec build, it would not.
> > Then I deleted 'alloc.o' and then 'make -k'.
> > It loaded up and dumped, writing 'boostrap-emacs.pdmp'.
> > Then it loaded up and dumped again, writing 'emacs.pdmp'.
> >
> > That was not necessary. Once should have been enough.
> It's enough when all the Lisp files are already byte-compiled. When
> some of them aren't, the two dumps are not identical, as the first one
> loads the uncompiled Lisp files, the second one loads the compiled
> ones.
Maybe make dependencies can discriminate that.
> If you don't want to compile Lisp files automatically, I think saying
> "make -k emacs.pdmp" should be your new paradigm.
I did not see an emacs.pdmp target. Is there one?
If so, where is it?
--
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-30 3:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 3:08 bug#36369: Master doesn't use its pdump Richard Stallman
2019-06-25 4:43 ` Eli Zaretskii
2019-06-25 5:37 ` Eli Zaretskii
2019-06-26 3:27 ` Richard Stallman
2019-06-26 14:34 ` Eli Zaretskii
2019-06-27 2:43 ` Richard Stallman
2019-06-27 13:12 ` Eli Zaretskii
2019-06-28 2:49 ` Richard Stallman
2019-06-28 6:49 ` Eli Zaretskii
2019-06-29 3:18 ` Richard Stallman
2019-06-29 7:14 ` Eli Zaretskii
2019-06-30 3:15 ` Richard Stallman [this message]
2019-06-30 3:38 ` Noam Postavsky
2022-02-15 10:11 ` Lars Ingebrigtsen
[not found] ` <E1nKpy3-0004rv-HP@fencepost.gnu.org>
[not found] ` <87h78wktj0.fsf@gnus.org>
2022-02-20 4:28 ` Richard Stallman
2022-02-20 6:40 ` Eli Zaretskii
2022-02-21 4:35 ` Richard Stallman
2022-02-21 12:17 ` Eli Zaretskii
2022-02-20 14:28 ` Stefan Monnier
2022-02-22 5:12 ` Richard Stallman
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=E1hhQJL-0004oR-0K@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=36369@debbugs.gnu.org \
--cc=eliz@gnu.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 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.