Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uwm.edu!uakari.primate.wisc.edu!samsung!think!snorkelwacker!spdcc!dyer
From: dyer@spdcc.COM (Steve Dyer)
Newsgroups: comp.protocols.kerberos
Subject: conf-aixps2.h
Message-ID: <939@ursa-major.SPDCC.COM>
Date: 19 Dec 89 22:19:47 GMT
References: <8912191532.AA16028@ATHENA.MIT.EDU> <8912191828.AA15605@jumbo>
Reply-To: dyer@ursa-major.spdcc.COM (Steve Dyer)
Organization: S.P. Dyer Computer Consulting, Cambridge MA
Lines: 33

In article <8912191828.AA15605@jumbo> saltzer@SRC.DEC.COM (Jerome H Saltzer) writes:
>I would guess that the problem is in the bit/byte order and word 
>length specifications.  I suppose that the 386 is more like a PC 
>than it is like an RT or a VAX, even if you run BSD Unix on it.

It has VAX byte order and 32-bit words.

>I believe that the appropriate architectural parameter settings for 
>the 8086 (and therefore they may also work on the 386) were:
>
>#define     BITS16
>#define     LSBFIRST
>#define     IBMPC

The defines for AIX PS/2, a 386 UNIX system are as follows:

% more conf-aixps2.h

#include <mit-copyright.h>

#define BITS32
#define BIG
#define LSBFIRST
[EOF]

Granted that the Sun 386i is a Berkeley-derived OS with its own
C compiler, but I wouldn't expect the architecture-specific defines
to differ between most 386 systems.

-- 
Steve Dyer
dyer@ursa-major.spdcc.com aka {ima,harvard,rayssd,linus,m2c}!spdcc!dyer
dyer@arktouros.mit.edu, dyer@hstbme.mit.edu