all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Daniel Colascione <dancol@dancol.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: pdumping "into" the executable
Date: Mon, 26 Feb 2018 14:10:27 -0700	[thread overview]
Message-ID: <87d10rpid8.fsf@tromey.com> (raw)
In-Reply-To: <bfdb1420-440e-b589-6938-edf97fd2a0be@dancol.org> (Daniel Colascione's message of "Mon, 26 Feb 2018 09:00:34 -0800")

>>>>> "Daniel" == Daniel Colascione <dancol@dancol.org> writes:

Daniel> I don't think strip-robustness is all that important, and I'd
Daniel> hope we could re-sign binaries as needed.

Distros usually build everything with debuginfo and then strip off the
debuginfo.  So, building this way would require special build hacks for
the distros.

Maybe instead you could use objcopy to stuff the data into some section
in the executable.  Or, just turn the dump to a C file, then compile it
and do a second link.  Aside from (maybe hypothetical) C compiler
limits, that would be very portable.

Tom



  reply	other threads:[~2018-02-26 21:10 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d10rpid8.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=dancol@dancol.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.