Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!BU-CS.BU.EDU!composer
From: composer@BU-CS.BU.EDU (Jeff Kellem)
Newsgroups: gnu.bash.bug
Subject: ISI68K (and also UMAX)
Message-ID: <8906140401.AA28629@bu-cs.BU.EDU>
Date: 14 Jun 89 04:01:53 GMT
References: <8906140341.AA21800@gibbs.physics.purdue.edu>
Sender: daemon@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 29

|   Date: Tue, 13 Jun 89 22:41:47 EST
|   From: ray@gibbs.physics.purdue.edu (Ray Moody)
|
|       Bash gives off "billiyons and billiyons" of compiler warnings as
|   it compiles, but it works anyway.  I plan to fix this someday.

Actually, I believe that James Van Artsdalen is doing a good amount of
work towards cleaning up that aspect.  So, you may not have to worry
about it.  (Actually, with gcc 1.34 and 1.35 straight [no -Wall], bash
0.99 compiles fine with no errors whatsoever.  It's just when you get
to "standard" vendor compilers that you have trouble.   :)

|       Also, if someone is working on a port to a UMAX machine, please
|   use "#ifdef UMAX" only inside "#ifndef ISI68K" because <sys/param.h>
|   defines a macro called UMAX.  Yes, I know, this is gross, but I didn't
|   write this OS, I just make it go.

Well, I've had bash running on an Encore Multimax running UMAX 3.3 since
version 0.95.  So far, no machine specific changes need to be made.  :)
Out of curiosity, what is the UMAX macro on the ISI68K for?  Thanks for
the info, though.

|								   Ray

				-jeff

Jeff Kellem
INTERNET: composer@bu-cs.bu.edu  (or composer%bu-cs.bu.edu@bu-it.bu.edu)
UUCP: ...!harvard!bu-cs!composer