Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!bin
From: bin@primate.wisc.edu (Brain in Neutral)
Newsgroups: comp.windows.x
Subject: Re: Mips config file for X R4 wanted
Message-ID: <1608@uakari.primate.wisc.edu>
Date: 16 Feb 90 17:30:47 GMT
References: <KEITH.90Feb15114346@osage.csc.ti.com>
Sender: bin@primate.wisc.edu
Reply-To: bin@primate.wisc.edu
Distribution: comp
Lines: 32

From article <KEITH.90Feb15114346@osage.csc.ti.com>, by keith@osage.csc.ti.com (Keith Sparacin):
> I am looking for a Mips config file (i.e. mit/config/mips.cf) used to
> build X release 4 on a Mips M2000 running RISC 4.0.  I only need the
> client side.  Has anyone already done it?

I think this brings up the question of what the right name would be for
a config file for MIPS computers.  mips.cf, perhaps, but I propose that
that is somewhat confusing, since MipsArchitecture gets defined for systems
other than those by MIPS (e.g., DS3100).  How about riscos.cf, since nobody
but MIPS uses an OS called RISC/os?  The control block I use in Imake.tmpl
looks like this:


#ifdef riscos
/* RISC/os cpp has no unique symbol:  build imake with BOOTSTRAPCFLAGS=-Driscos */
#define MacroIncludeFile <riscos.cf>
#define MacroFile riscos.cf
#undef riscos
#undef mips
#define RiscosArchitecture	/* for OS type */
#define MipsArchitecture	/* for chipset type */
#endif /* riscos */

Is this reasonable?

Note that the ambiguity about MipsArchitecture (i.e., not being able to tell
from it alone whether you're running on a MIPS) also applies to the symbol
"mips".  Unfortunately a certain amount of source code contains #ifdef's
to just that symbol.  Argh.

Paul DuBois
dubois@primate.wisc.edu