From: Dan Nicolaescu <dann@ics.uci.edu>
To: Glenn Morris <rgm@gnu.org>
Cc: Sascha Wilde <wilde@sha-bang.de>, emacs-devel@gnu.org
Subject: Re: Building Emacs on SGI mips/netbsd
Date: Fri, 26 Jun 2009 23:17:53 -0700 (PDT) [thread overview]
Message-ID: <200906270617.n5R6Hr1B013814@godzilla.ics.uci.edu> (raw)
In-Reply-To: <oeab3ubdl4.fsf@fencepost.gnu.org> (Glenn Morris's message of "Fri, 26 Jun 2009 22:44:07 -0400")
Glenn Morris <rgm@gnu.org> writes:
> Sascha Wilde wrote:
>
> > 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.
>
> I have restored the mips netbsd support that was in Emacs 22.
The above seems to say that mips.h is good enough, why add again another
file for the same architecture (we already have 2 for mips: mips.h and
iris4d.h)?
Also, quite a bit of effort has been made to remove unused stuff in the
m/* files, is there anything interesting remaining in that pmax.h file
after removing #defines that are not used anymore?
next prev parent reply other threads:[~2009-06-27 6:17 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
2009-06-27 2:44 ` Glenn Morris
2009-06-27 6:17 ` Dan Nicolaescu [this message]
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
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=200906270617.n5R6Hr1B013814@godzilla.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=rgm@gnu.org \
--cc=wilde@sha-bang.de \
/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).