From: Sascha Wilde <wilde@sha-bang.de>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Building Emacs on SGI mips/netbsd
Date: Fri, 26 Jun 2009 10:01:26 +0200 [thread overview]
Message-ID: <m21vp7o23t.fsf@sha-bang.de> (raw)
In-Reply-To: <h91vp9se41.fsf@fencepost.gnu.org> (Glenn Morris's message of "Wed, 24 Jun 2009 14:03:58 -0400")
Glenn Morris <rgm@gnu.org> wrote:
> Sascha Wilde wrote:
>
>> + mips-*-netbsd* | mipseb-*-netbsd* \
>> + | mips64-*-netbsd* | mips64eb-*-netbsd* )
>> + machine=mips ;;
>> +
>
> In Emacs 22, mips-*-netbsd*, mipsel-*-netbsd* and mipseb-*-netbsd*
> used "machine=pmax". As far as I can tell, mips64* was not supported.
>
> The file src/m/pmax.h has since been deleted. It does seem quite
> important to me to fix this, but I could not say if mips.h is "good
> enough" or if pmax.h should be restored.
Well, from my current experience I would say mips.h is good enough at
least for non-mips64 R4000 systems (and afaik there is no mips64 netbsd at the
moment). I don't have anything else to test, so people with different
hardware or more theoretical knowledge should probably verify this. But
I'd suggest to re-enable mips/netbsd support asap, so that it can get some
wider testing.
cheers
sascha
--
Sascha Wilde
"Structure is _nothing_ if it is all you got. Skeletons _spook_ people if
thwy try to walk around on their own. I really wonder why XML does
not." -- Erik Naggum <erik@naggum.net> in comp.lang.lisp
next prev parent reply other threads:[~2009-06-26 8:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 12:33 Building Emacs on SGI mips/netbsd Sascha Wilde
2009-06-17 16:18 ` Glenn Morris
2009-06-24 8:38 ` Stefan Monnier
2009-06-24 8:58 ` Miles Bader
2009-06-26 7:46 ` Sascha Wilde
2009-06-24 18:03 ` Glenn Morris
2009-06-26 8:01 ` Sascha Wilde [this message]
2009-06-27 2:44 ` Glenn Morris
2009-06-27 6:17 ` Dan Nicolaescu
2009-06-28 0:55 ` Glenn Morris
2009-07-03 13:19 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m21vp7o23t.fsf@sha-bang.de \
--to=wilde@sha-bang.de \
--cc=emacs-devel@gnu.org \
--cc=rgm@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.