From: "Thorbjørn Ravn Andersen" <tra@biobase.dk>
Cc: emacs-devel@gnu.org
Subject: Re: Mac OS X: Rebuild Require after Security Update 2002-11-21
Date: Mon, 25 Nov 2002 08:40:12 +0100 [thread overview]
Message-ID: <3DE1D3DC.8030905@biobase.dk> (raw)
In-Reply-To: m2bs4g9srx.fsf@owlbear.local
Andrew Choi wrote:
>The 2002-11-21 Security Update seems to cause Emacs executables built
>before the update to fail. Rebuilding will make them work again. I
>realize this is an annoying problem. But I must admit currently I have
>no idea how to solve it.
>
Thank you for this information.
As I have understood it from this list, the problem is with a library
call that exists solely for Emacs to be able to unexec, which is to
avoid a lengthy elisp initialization at each startup.
Is this still so complicated that it is almost impossible to do
"manually" by dumping and restoring the contents of the elisp engine
similar to what TeX does?
--
Thorbjørn Ravn Andersen Scandiatransplant
Skejby Sygehus, indgang 3
+45 89 49 53 01 DK-8200 Århus N
http://biobase.dk/~tra
next prev parent reply other threads:[~2002-11-25 7:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m2bs4g9srx.fsf@owlbear.local>
2002-11-23 23:49 ` Mac OS X: Rebuild Require after Security Update 2002-11-21 Jason Rumney
2002-11-24 19:58 ` Andrew Choi
2002-11-24 21:03 ` Jason Rumney
2002-11-25 23:56 ` Steven Tamm
2002-11-26 0:18 ` Jason Rumney
2002-11-26 1:19 ` Andrew Choi
2002-11-26 14:53 ` Stefan Monnier
2002-11-26 16:31 ` Steven Tamm
2002-11-26 17:29 ` Andrew Choi
2002-11-26 17:45 ` fork v vfork (was Re: Mac OS X: Rebuild Require after Security Update 2002-11-21) Steven Tamm
2002-11-24 20:37 ` Mac OS X: Rebuild Require after Security Update 2002-11-21 Steven Tamm
2002-11-24 21:58 ` Andrew Choi
2002-11-24 23:06 ` Steven Tamm
2002-11-25 7:40 ` Thorbjørn Ravn Andersen [this message]
2002-11-25 8:10 ` Andrew Choi
2002-11-26 11:15 ` 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=3DE1D3DC.8030905@biobase.dk \
--to=tra@biobase.dk \
--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).