Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!killer!vector!chip
From: chip@vector.UUCP (Chip Rosenthal)
Newsgroups: comp.mail.elm
Subject: Re: Elm 2.3 nusiance
Keywords: Elm 2.3 MicroPort
Message-ID: <643@vector.UUCP>
Date: 20 Nov 88 18:54:18 GMT
References: <88@prapc2.UUCP> <7@dsinc.UUCP>
Reply-To: chip@vector.UUCP (Chip Rosenthal)
Distribution: na
Organization: Dallas Semiconductor
Lines: 23

In article <7@dsinc.UUCP> syd@dsinc.UUCP (Syd Weinstein) writes:
>In article <88@prapc2.UUCP> paulr@prapc2.UUCP (Paul Raulerson) writes:
>:[Elm barfed] Using Microport SysV/AT a fast '286 with lots of memory...
>:[...] Anyway, I cured all this by [saying] -UXENIX 
>Two comments.  XENIX define is only for XENIX systems, not Microport and
>definately not for 286's.  It relates to other items such as file
>placement.

Syd is absolutely right.  "XENIX" should be defined only if the target
system is XENIX.  Makes sense...

More specifically...Elm 2.1 was tested on SCO XENIX V2.2 on both 286 and
386 machines, and Configure knows about these systems, and will generate
Makefile's which define XENIX.  As far as I know, other flavors of XENIX
are untested.

As a side note...if you are running SCO XENIX and are planning to bring
up Elm whenever it makes it out of the queue...get in touch with SCO and
ask for the "crypt" disk.  Elm assumes that you have crpyt(S) available,
and your Makefile will be built with "-lcrypt".
-- 
Chip Rosenthal     chip@vector.UUCP    |      Choke me in the shallow water
Dallas Semiconductor   214-450-5337    |         before I get too deep.