From: Drew Adams <drew.adams@oracle.com>
To: Paul Eggert <eggert@cs.ucla.edu>, Daniel Colascione <dancol@dancol.org>
Cc: Tom Tromey <tom@tromey.com>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: RE: pdumping "into" the executable
Date: Mon, 26 Feb 2018 16:09:18 -0800 (PST) [thread overview]
Message-ID: <f746c1c0-a364-419c-ac57-e18ac9d71b99@default> (raw)
In-Reply-To: <41ac3ca1-a850-2c8a-0ad4-6b410b3932aa@cs.ucla.edu>
> > I thought we had this argument back when we were talking about
> > modules. I think it's unacceptable to require a C compiler and the
> > presence of Emacs unlinked objects for the proper operation of an
> > end-user feature.
>
> Although using a dumped Emacs is an end-user feature, dumping and
> redumping are not. Dumping and/or redumping are techniques used to build
> Emacs, and in practice they should be part of a software build system;
> for such a thing it's reasonable to assume a C compiler.
>
> We already assume a C compiler (or equivalent) when building modules; we
> don't assume a C compiler only when people are using the modules.
> Dumping is similar.
This probably doesn't help, but I remember dumping Emacs with my
Lisp customizations back in the 80s, as an end user, to get quick
start-up. I didn't build Emacs myself, and I had no C compiler
and didn't need one. No, I don't recall more than that, except
that this was with GNU Emacs (probably version 18?) on Unix.
I don't recall how I (and others) did it.
So if possible, I think it would be good for end users (with no C
compiler) to be able to take advantage of this new, portable dumper.
next prev parent reply other threads:[~2018-02-27 0:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 13:38 pdumping "into" the executable Stefan Monnier
2018-02-26 17:00 ` Daniel Colascione
2018-02-26 21:10 ` Tom Tromey
2018-02-26 21:18 ` dancol
2018-02-26 22:07 ` Paul Eggert
2018-02-26 22:22 ` Daniel Colascione
2018-02-26 23:17 ` Paul Eggert
2018-02-26 23:34 ` dancol
2018-02-26 23:41 ` dancol
2018-02-27 0:09 ` Drew Adams [this message]
2018-02-27 0:16 ` dancol
2018-02-27 7:55 ` John Wiegley
2018-02-27 13:47 ` Dmitry Gutov
2018-02-27 14:47 ` Stefan Monnier
2018-02-27 18:32 ` John Wiegley
2018-02-26 22:34 ` Clément Pit-Claudel
2018-02-26 22:47 ` Daniel Colascione
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=f746c1c0-a364-419c-ac57-e18ac9d71b99@default \
--to=drew.adams@oracle.com \
--cc=dancol@dancol.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=tom@tromey.com \
/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).