From: "Peter O'Gorman" <pogma@thewrittenword.com>
To: Dan Nicolaescu <dann@gnu.org>
Cc: 6811@debbugs.gnu.org
Subject: bug#6811: [PATCH] emacs-23.2 on hpux
Date: Mon, 9 Aug 2010 15:42:02 -0500 [thread overview]
Message-ID: <20100809204202.GQ7715@tw.local> (raw)
In-Reply-To: <yxqy6cgm81d.fsf@fencepost.gnu.org>
On Mon, Aug 09, 2010 at 05:47:58AM -0400, Dan Nicolaescu wrote:
> > + ia64*-hp-hpux1[1-9]* )
> > + machine=hp800 opsys=hpux11
>
> I think new ports need to be approved by the maintainers.
> This looks a bit odd.
> Shouldn't the machine file be ia64? Or a new file with ia64 in the name?
At least for 23.2 ia64.h doesn't work. We'll try again on the next
release.
>
> > /* Tested in getloadavg.c. */
> > +#ifndef HAVE_PSTAT_GETDYNAMIC
> > #define HAVE_PSTAT_GETDYNAMIC
> > +#endif
>
> If autoconf sets HAVE_PSTAT_GETDYNAMIC, then it seems that it's better
> to just remove the #define.
Sure, autoconf does set it.
> >
> > +#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.
> >
> > #else /* USE_LISP_UNION_TYPE */
>
> There's some code that does DATA_SEG_BITS further down in the file,
> maybe some untangling is needed in lisp.h...
That would be nice, it gave me a headache :-)
Peter
--
Peter O'Gorman
pogma@thewrittenword.com
next prev parent reply other threads:[~2010-08-09 20:42 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 [this message]
2010-08-09 23:13 ` Dan Nicolaescu
2010-08-10 9:08 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100809204202.GQ7715@tw.local \
--to=pogma@thewrittenword.com \
--cc=6811@debbugs.gnu.org \
--cc=dann@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.