Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!mtune!mtuni!aaa
From: aaa@mtuni.UUCP
Newsgroups: comp.emacs
Subject: Re: Free Software Foundation (was: Re: Mach, the new standard?)
Message-ID: <296@mtuni.ATT.COM>
Date: Mon, 31-Aug-87 10:27:23 EDT
Article-I.D.: mtuni.296
Posted: Mon Aug 31 10:27:23 1987
Date-Received: Tue, 1-Sep-87 04:36:38 EDT
References: <7919@think.UUCP>
Organization: AT&T ISL Middletown NJ USA
Lines: 21
In-reply-to: rlk@think.COM's message of 28 Aug 87 17:44:20 GMT
Posting-Front-End: GNU Emacs 18.37.4 of Wed Mar  4 1987 on mtuni (usg-unix-v)

For the record:

*]The FSF/GNU people pretend their programs install with the proper m-machine.h
*]files.  This does not appear to be true.  After looking at 18.47 for too long
*]I gave up trying to second-guess bad code and removed it.  The only cpu types
*]supported were 68000 and VAX.  

*I wonder what Karl Kleinpaste would have to say to that?  I don't use
*3B's, but he's evidently done a good job porting emacs to that
*architecture.  As for machine support, a quick ls -l m-*|wc shows that
*approximately 36 machines are supported right now, and I can think of
*other architectures whose m- files haven't made it back in yet.  Only
*one of these is a VAX, and there are lots of non-68K architectures in
*there.

I've had no trouble at all porting to the 3B2, the VAX, and to the
UNIX PC.  As far as doing "a good job porting emacs" to the 3B2--it is
not much harder than typing "make" (a little, but not much).
-- 

Aaron, mtuni!aaa, 201-957-2751