Xref: utzoo comp.unix.xenix:5277 comp.sys.ibm.pc:25931 comp.lang.lisp:1538
Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!cwjcc!tut.cis.ohio-state.edu!osu-cis!att!cbnews!mjs
From: mjs@cbnews.ATT.COM (martin.j.shannon)
Newsgroups: comp.unix.xenix,comp.sys.ibm.pc,comp.lang.lisp
Subject: Re: Internals Question about SCO Xenix 2.3
Summary: Works AOK on AT&T SVR3.1 on WGS6386E
Keywords: xenix 2.3, kcl, segments, incremental compilation
Message-ID: <4665@cbnews.ATT.COM>
Date: 10 Mar 89 15:27:54 GMT
References: <201@spt.entity.com>
Reply-To: mjs@cbnews.ATT.COM (martin.j.shannon)
Followup-To: comp.lang.lisp
Organization: AT&T Bell Laboratories
Lines: 34

In article <201@spt.entity.com> mdc@spt.entity.com (Marty Connor) writes:
>I wish to run KCL (Kyoto Common Lisp) on my Xenix box, but have not
>been able to.  As described to me:  "There are two segments:  TEXT and
>DATA, each with attributes.  The TEXT segment (usually code) has attribute
>READ-ONLY, and the DATA segment has attribute "NON-EXECUTABLE".
>
>This makes using KCL hard if not impossible because it wants to load
>object files that it compiles into the text segment of the process.

Actually, it intends to execute in the DATA segment, but you'll see the same
result: it doesn't work, and probably generates a core dump.

>My question is, has anything changed in 2.3 that will allow this to
>happen more easily?

I don't know about Xenix, but....

>Barring 2.3, is there ANY 386 Unix that you know of that will run KCL
>as it is intended?

Yes, I have successfully run KCL & AKCL on an AT&T SVR3.1 running on an AT&T
WGS6386E (20 MHz tower).  In the next several weeks, I intend to verify that
it continues to work on AT&T's SVR3.2, and that it builds & runs on ISC's
386/ix 2.0.1 (I have no reason to doubt that either will work flawlessly).

>-- 
>Marty Connor
>Director of Innovation, The Entity
>mdc@entity.com, ...{harvard|uunet}!mit-eddie!spt!mdc


-- 
Marty Shannon; AT&T Bell Labs; Liberty Corner, NJ
(Affiliation given for identification only.)