From: Ken Raeburn <raeburn@raeburn.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Emacs Development <emacs-devel@gnu.org>
Subject: Re: bootstrap error in c-mode with CANNOT_DUMP
Date: Sat, 13 Jun 2009 03:10:25 -0400 [thread overview]
Message-ID: <12EE68A1-C526-47EE-813C-4B2C05227DB3@raeburn.org> (raw)
In-Reply-To: <jwv1vppf84v.fsf-monnier+emacs@gnu.org>
On Jun 12, 2009, at 17:37, Stefan Monnier wrote:
> This is a known problem since it plagued the GNUStep port as well
> (when
> it couldn't dump). Right now the use of CANNOT_DUMP leads to all
> kinds
> of problems (IIRC even things like ~/.emacs don't get processed
> correctly). But it's not very high on the todo-list, so if you can
> find
> a fix for it, it would probably be welcome, but otherwise don't hold
> your breath. A better path might be to try and find a way to do the
> unexec.
Working on it, but Guile's initialization is a little complicated in
places. In the (much) longer term, I think finding some solution for
Emacs other than unexec would be better, if we want to permit
extensions in general, because unexec-ability seems like a pretty
onerous demand to make of all libraries one might want to use.
(Luckily, I suspect most such libraries don't need to have *any* code
run before the unexec step, so loading fresh versions in the new
process isn't a problem; that just doesn't work in my case.) But
that's a whole other matter...
I was kind of hoping CANNOT_DUMP might give me a shortcut to something
I could actually run. :-(
Actually, it kind of does, if I avoid bootstrapping; I just have to
figure out if each bug is in my work or in the Emacs code base I'm
starting with....
Ken
next prev parent reply other threads:[~2009-06-13 7:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 6:25 bootstrap error in c-mode with CANNOT_DUMP Ken Raeburn
2009-06-12 21:37 ` Stefan Monnier
2009-06-13 7:10 ` Ken Raeburn [this message]
2009-06-13 9:43 ` Eli Zaretskii
2009-06-14 4:56 ` Richard Stallman
2009-06-14 5:01 ` Ken Raeburn
2009-06-15 1:53 ` Richard Stallman
2009-06-13 2:41 ` Eli Zaretskii
2009-06-13 7:10 ` Ken Raeburn
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=12EE68A1-C526-47EE-813C-4B2C05227DB3@raeburn.org \
--to=raeburn@raeburn.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 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).