Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!leah!itsgw!steinmetz!uunet!sco!rosso
From: rosso@sco.COM (Ross Oliver)
Newsgroups: comp.unix.xenix
Subject: Re: UNIX assemblers and SCO
Message-ID: <1703@viscous.sco.COM>
Date: 22 Feb 89 21:46:07 GMT
References: <13163@steinmetz.ge.com> <648@cimcor.mn.org>
Reply-To: uunet!sco!rosso (Ross Oliver)
Distribution: usa
Organization: SCO Technical Support
Lines: 25

Regarding the recent discussion of SCO's support of AT&T's 386
assembler, the SCO XENIX 3.2 Development System will contain almost
literally EVERYTHING that is in XENIX 2.3 and AT&T UNIX.

In this context it will contain:

	Microsoft 8086/286 C compiler generating OMF.
	Microsoft 386 C compiler generating either OMF or COFF
	Microsoft MASM generating 8086/80286 OMF and 386 OMF or COFF
	AT&T 386 assembler generating 386 COFF
	Microsoft linkers for generating 8086/286/386 x.out,
	   also DOS and OS/2 executable formats
	AT&T linker generating 386 COFF.

The net result is that the 3.2 Development System will let you generate
8086 / 286 code for XENIX, DOS and OS/2 and 386 code for XENIX and UNIX.

The current Develpment System, release 2.3 (confusing, eh?), does
not include the AT&T assembler, and cannot generate COFF object
modules.  However, the linker will accept COFF libraries and object
modules, and will generate XENIX x.out binaries from them.

Ross Oliver
Technical Support
The Santa Cruz Operation, Inc.