unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
Cc: Yavor Doganov <yavor@gnu.org>, rms <rms@gnu.org>,
	richardeng <richardeng@foxmail.com>,
	emacs-devel <emacs-devel@gnu.org>
Subject: Re: Emacs on GNUstep
Date: Mon, 04 May 2009 09:45:40 -0400	[thread overview]
Message-ID: <jwvzldtnfw4.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <wlhc01qo3y.wl%mituharu@math.s.chiba-u.ac.jp> (YAMAMOTO Mitsuharu's message of "Mon, 04 May 2009 17:16:49 +0900")

> We can't simply remove CANNOT_DUMP because dumping requires unexelf.c
> currently.  The macro __ELF__ cannot be used here because it doesn't
> necessarily imply the use of unexelf.c (e.g., Solaris 10).

I think it's OK to say that the GNUStep port currently only "works" with
ELF systems.  In any case, experience has shown that CANNOT_DUMP doesn't
really work, so if people want to use GNUStep under Solaris, they're
just going to have to debug the corresponding dump process.  In this
context, it's worthwhile to keep/put the "#ifdef NS_IMPL_GNUSTEP" in
unexelf.c as a document that can be useful for hackers trying to make it
work on other unex*.c.


        Stefan




  reply	other threads:[~2009-05-04 13:45 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-02  2:43 Release update Chong Yidong
2008-12-04 17:08 ` Yavor Doganov
2008-12-04 18:50   ` Ted Zlatanov
2008-12-04 19:29     ` Chong Yidong
2008-12-04 19:46       ` Ted Zlatanov
2008-12-04 22:55       ` Adrian Robert
2008-12-08 16:42         ` Ted Zlatanov
2008-12-05  2:12     ` Randal L. Schwartz
2008-12-05  2:44       ` Randal L. Schwartz
2008-12-04 19:43   ` Stefan Monnier
2008-12-04 19:45   ` Dan Nicolaescu
2008-12-05 12:08   ` Richard M Stallman
2008-12-05 12:44   ` richardeng
2008-12-05 15:49     ` Emacs on GNUstep (was: Release update) Stefan Monnier
2008-12-06  4:44       ` Stephen J. Turnbull
2008-12-06  6:59       ` richardeng
2008-12-06  7:54         ` Stephen J. Turnbull
2008-12-06 16:05         ` richardeng
2008-12-06 17:22           ` Emacs on GNUstep Chong Yidong
2009-05-02  6:28       ` Emacs on GNUstep (was: Release update) YAMAMOTO Mitsuharu
2009-05-03 19:38         ` Emacs on GNUstep Stefan Monnier
2009-05-04  8:16           ` YAMAMOTO Mitsuharu
2009-05-04 13:45             ` Stefan Monnier [this message]
2009-05-06  2:36               ` YAMAMOTO Mitsuharu
2009-05-06 14:18                 ` Stefan Monnier
2009-05-03 22:45         ` Emacs on GNUstep (was: Release update) Yavor Doganov
2009-05-04  8:47           ` YAMAMOTO Mitsuharu
2008-12-04 19:51 ` Release update Dan Nicolaescu
2008-12-04 21:43   ` Chong Yidong
2008-12-04 22:27     ` Dan Nicolaescu

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=jwvzldtnfw4.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=mituharu@math.s.chiba-u.ac.jp \
    --cc=richardeng@foxmail.com \
    --cc=rms@gnu.org \
    --cc=yavor@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).