From: "Chris Hall" <chris@web.workinglinux.com>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
Emacs devel <emacs-devel@gnu.org>
Subject: Re: CANNOT_DUMP support
Date: Mon, 11 Feb 2008 09:18:41 -1000 [thread overview]
Message-ID: <033e133313f724a1896d8077e2f73d0d@lagorda> (raw)
In-Reply-To: <200802110433.m1B4XrXw017599@sallyv1.ics.uci.edu>
On 2008-02-10 18:33:53 -1000 Dan Nicolaescu <dann@ics.uci.edu> wrote:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
> > >> > > I know that GNUstep is a CANNOT_DUMP platform, and I
> have been
> > >> > > informed that there aren't many others left. Is there a
> list
> > >> > > somewhere that I could view?
> > >> >
> > >> > No list, just grep emacs/src/m/*
> > >> > >> Ah. Thanks.
> > >> > >> Hmm. System/390, amdx86-64, ia-64, m68k. > > > Nope,
> look
> again, all those are either commented out or inside #if 0.
> > > > The only remaining one is in ibmrs6000.h when using sysV. I
> don't know
> > > of any such system in current use ...
> > > Yup: CANNOT_DUMP is not on the way out, but it's only ever
> seriously
> > used for targets that are "in development".
> > We need to get dumping to work on GNUstep before we can consider
> it as
> > "ready for prime time" (tho I don't consider it as a prerequisite
> for
> > being on the trunk).
>
> Has there been any decision about merging that code? It would
> probably
> be better to merge it sooner rather than later...
>
Well, its been a long time since I've worked at the level unexec
operates at, and even then it was on System/360 and Series/1, but it
looks like an interesting problem.
At first glance I imagine dealing with late-binding in Objective C is
one of the challenges in dumping on GNUstep platforms?
Anyway, at the moment I'm more interested in getting the GNUstep
Emacs.app working a bit better, so I'm trying to get my mind around
the multi-tty stuff.
I've found http://lorentey.hu/project/emacs.html.hu very useful in
getting started on that.
Thanks for all the useful responses, everybody.
next prev parent reply other threads:[~2008-02-11 19:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 6:35 CANNOT_DUMP support Chris Hall
2008-02-10 17:07 ` Dan Nicolaescu
2008-02-11 1:36 ` Chris Hall
2008-02-11 1:48 ` Dan Nicolaescu
2008-02-11 3:04 ` Stefan Monnier
2008-02-11 4:33 ` Dan Nicolaescu
2008-02-11 19:18 ` Chris Hall [this message]
2008-02-12 22:30 ` Stephen J. Turnbull
2008-02-13 16:33 ` Richard Stallman
2008-02-13 19:46 ` Stephen J. Turnbull
2008-02-14 4:42 ` Richard Stallman
2008-02-14 6:47 ` Stephen J. Turnbull
2008-02-14 7:44 ` Chris Hall
2008-02-14 8:13 ` Kenichi Handa
2008-02-15 0:03 ` Richard Stallman
2008-02-23 5:07 ` Stefan Monnier
2008-02-23 6:33 ` Kenichi Handa
2008-02-11 4:26 ` Eli Zaretskii
2008-02-11 0:16 ` 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=033e133313f724a1896d8077e2f73d0d@lagorda \
--to=chris@web.workinglinux.com \
--cc=dann@ics.uci.edu \
--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).