From: Michael Welsh Duggan <mwd@md5i.com>
To: emacs-devel@gnu.org
Subject: Re: Handling of links with portable dumper
Date: Mon, 08 Apr 2019 00:04:40 -0400 [thread overview]
Message-ID: <87tvf9ywfb.fsf@md5i.com> (raw)
In-Reply-To: <ca511bc9-3eba-b679-460b-539394493cbd@gmail.com> ("Clément Pit-Claudel"'s message of "Sun, 7 Apr 2019 18:07:59 -0400")
Clément Pit-Claudel <cpitclaudel@gmail.com> writes:
> On 2019-04-07 13:44, Paul Eggert wrote:
>> I still think it'd be better to put the dump into the executable
>> itself, which can be done portably simply by linking a big C
>> character array into the executable. in the long run this will be
>> better for users (and for us) than fiddling with portability
>> minefields like set_program_name_and_installdir.
>
> Does that mean also rewriting the full binary when we rewrite the dump?
I would assume that when the executable was built it would be dumped
with the dump file created at that time, but that that emacs could load
a different dump file than the one built into it. I don't see a good
portable way to re-make the executable after the fact absent going back
to the source build, though.
--
Michael Welsh Duggan
(md5i@md5i.com)
next prev parent reply other threads:[~2019-04-08 4:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 22:39 Handling of links with portable dumper Richard Stallman
2019-04-05 5:42 ` Eli Zaretskii
2019-04-05 22:32 ` Richard Stallman
2019-04-06 6:30 ` Eli Zaretskii
2019-04-06 23:24 ` Richard Stallman
2019-04-07 2:41 ` Eli Zaretskii
2019-04-07 17:04 ` Daniel Colascione
2019-04-07 17:44 ` Paul Eggert
2019-04-07 22:07 ` Clément Pit-Claudel
2019-04-08 4:04 ` Michael Welsh Duggan [this message]
2019-04-08 4:08 ` Paul Eggert
2019-04-07 18:15 ` Eli Zaretskii
2019-04-08 22:00 ` Richard Stallman
2019-04-06 22:29 ` Stefan Monnier
2019-04-07 21:58 ` 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
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=87tvf9ywfb.fsf@md5i.com \
--to=mwd@md5i.com \
--cc=emacs-devel@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 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).