Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!crdgw1!uakari.primate.wisc.edu!samsung!umich!umeecs!msi.umn.edu!cs.umn.edu!kksys!com50!rosevax!uci!clay
From: clay@uci.com (Clayton Haapala)
Newsgroups: comp.unix.xenix.sco
Subject: Re: Sys V386 binaries working under SCO Xenix 2.3.2 ???
Keywords: sysv36 sco groff
Message-ID: <1991Feb15.233116.26501@uci.com>
Date: 15 Feb 91 23:31:16 GMT
References: <453@lccinc.UUCP>
Organization: Unified Communications, Inc.
Lines: 25

In article <453@lccinc.UUCP> bent@lccinc.UUCP (Ben Taylor) writes:
>Hello world,
>  are 386 Coff format.  I wasn't aware that Unix 3.2 binaries would
>  run under Xenix.  I knew they would go the other way tho?  Any one
>  care to comment on this.  Maybe this is an isolated incident, however
Not isolated, at all.  XENIX could do COFF before the SysV vendors could do
XENIX -- but it all comes from the binary compatibility agreements made
between the major players a couple of years ago.  One Gate's major smart moves,
in my estimation.

Limitations?  You can't do COFF 387 fpp emulation under XENIX, but it all
works great if you have a co-processor.  Shared-libs (libc libnsl) are
provided under /shlib for XENIX, just like you'd expect on a COFF machine,
so these work, too.

I run Microport's old DWB package and used to run Green Hill's C under XENIX.
I replaced GCC with GNU GCC, and I may replace the DWB with Groff, now that
it's out.

Cheers.
-- 
Clayton Haapala                (clay@uci.com)
Unified Communications Inc.    "Every morning I get in the Queue.
3001 Metro Drive - Suite 500    'n get on the Bus that takes me to you."
Bloomington, MN  55425             -- the Who