From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Dan Nicolaescu <dann@gnu.org>
Cc: 6811@debbugs.gnu.org, Peter O'Gorman <pogma@thewrittenword.com>
Subject: bug#6811: [PATCH] emacs-23.2 on hpux
Date: Tue, 10 Aug 2010 11:08:20 +0200 [thread overview]
Message-ID: <jwv7hjylu18.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <yxqr5i71ism.fsf@fencepost.gnu.org> (Dan Nicolaescu's message of "Mon, 09 Aug 2010 19:13:29 -0400")
>>> > + ia64*-hp-hpux1[1-9]* )
>>> > + machine=hp800 opsys=hpux11
>>> I think new ports need to be approved by the maintainers.
That's OK.
>>> This looks a bit odd. Shouldn't the machine file be ia64? Or a new
>>> file with ia64 in the name?
hp800.h is the only hp*.h we have, so it seems to apply to all hp machines.
I don't think we need to worry too much about the presence/absence of
ia64 in the name: most of the stuff in hp800.h (the one from emacs-23,
I mean) is OS-dependent rather than machine dependent, as is almost
always the case nowadays.
>>> > +#if __ia64
>>> > +#define CANNOT_DUMP 1
>>> > +#endif
>>> This looks bad, we don't have any port in the tree that does CANNOT_DUMP.
>>> Does it work if you dump using unexelf.o?
>> No.
> Bummer, then, IMVHO, this is not ready to be included...
It's not ready for real use, but that doesn't mean we can't include it.
Stefan
next prev parent reply other threads:[~2010-08-10 9:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-06 16:16 bug#6811: [PATCH] emacs-23.2 on hpux Peter O'Gorman
2010-08-09 9:47 ` Dan Nicolaescu
2010-08-09 11:05 ` Jan Djärv
2010-08-09 16:22 ` Dan Nicolaescu
2010-08-09 20:42 ` Dan Nicolaescu
2010-08-10 14:14 ` Jan Djärv
2010-08-09 19:37 ` Andreas Schwab
2010-08-09 20:42 ` Peter O'Gorman
2010-08-09 23:13 ` Dan Nicolaescu
2010-08-10 9:08 ` Stefan Monnier [this message]
2010-08-10 10:04 ` Andreas Schwab
2010-08-10 12:33 ` Stefan Monnier
2011-01-23 23:03 ` Chong Yidong
2011-01-24 14:00 ` bug#6811: " Andy Moreton
2011-01-28 17:05 ` Chong Yidong
2019-09-06 0:42 ` Glenn Morris
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=jwv7hjylu18.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=6811@debbugs.gnu.org \
--cc=dann@gnu.org \
--cc=pogma@thewrittenword.com \
/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).