Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!ll-xn!mit-eddie!killer!wnp
From: wnp@killer.UUCP (Wolf Paul)
Newsgroups: comp.unix.microport
Subject: Re: uPort 386
Message-ID: <3679@killer.UUCP>
Date: 14 Mar 88 02:16:11 GMT
References: <929@xn.LL.MIT.EDU> <7602@agate.BERKELEY.EDU>
Reply-To: wnp@killer.UUCP (Wolf Paul)
Organization: The Unix(R) Connection BBS, Dallas, Tx
Lines: 26

In article <7602@agate.BERKELEY.EDU> ewv@violet.berkeley.edu (Eric Varsanyi) writes:
>In article <929@xn.LL.MIT.EDU> singer@XN.LL.MIT.EDU (Matthew R. Singer) writes:
>>1)  Can the 386 system compile for a 286 machine (Large model)?
>No, the supplied compiler cannot produces 286 executables. The system does
>seem to be able to run COFF 286 executables.
>
>>    If not, since I need the system for product development,
>>    can V/AT and V/386 reside on the same machine?
>I've heard gripes here that people cannot get the 286 product up on a 386,
>theoretically it should work, the 386 is downward compatible.
>

Well, if the 386 compiler will not compile 286 code, but the 386 UNIX will run
286 COFF binaries, you might be able to run the 286 Development System under
your 386 UNIX kernel. Of course you'd have to use not only the 286 compiler,
assembler & linker, but the 286 libraries and include files as well.

It should even be possible to set up a shell script which does a "chroot"
to a separate "286 directory hierarchy" to automatically access a
286-specific /usr/lib/, /usr/include/, etc.

Has anybody tried this?
-- 
Wolf N. Paul * 3387 Sam Rayburn Run * Carrollton TX 75007 * (214) 306-9101
UUCP:  ihnp4!killer!dcs!wnp                    ESL: 62832882
INTERNET: wnp@EESDES.DAS.NET or wnp@dcs.UUCP   TLX: 910-280-0585 EES PLANO UD
                One Austrian's Opinion:  Waldheim must go!