Xref: utzoo comp.unix.sysv386:71 comp.unix.xenix.sco:27
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uunet!indetech!fiver!palowoda
From: palowoda@fiver (Bob Palowoda)
Newsgroups: comp.unix.sysv386,comp.unix.xenix.sco
Subject: Re: Which 386 UNIX binaries run on which 386 UNIXs ?
Message-ID: <1990Sep4.013116.21214@fiver>
Date: 4 Sep 90 01:31:16 GMT
References: <1990Sep04.000727.17429@virtech.uucp>
Distribution: comp
Organization: Fiver Communications, Fremont, Ca
Lines: 32

From article <1990Sep04.000727.17429@virtech.uucp>, by cpcahil@virtech.uucp (Conor P. Cahill):

Hmm,

> 2ND IMPORTANT NOTE: While you can run Xenix executables on UNIX and
> vice-versa, you cannot use the standard debugging tools to view core
> files generated from executables for the other system.  You will also
> have a problem reading Xenix libraries on Unix systems and probably 
                         ^^^^^^^^^^^^^^^^^

  Just curious are there tools to create lib files on SCO UNIX that other
386 versions of UNIX will read. Or is this standard when you use 'rcc'.
Also is there a obj file conversion program to move to coff?

  With respect to debugging the corefile. I would assume that developers
distributing object files for other 386 version of UNIX would do so in
COFF format and therefor would have the problem with linking and useing
other 386 debugging tools. Or did I miss the boat somewhere?

> vice-versa.  By "reading" I mean using them to link with a program.  This
> important note does not apply to SCO UNIX, since it has the Xenix compiler
> and development tools.

  I don't understand why someone would want to do that anyways?

---Bob

-- 
Bob Palowoda   palowoda@fiver              |   *Home of Fiver BBS*
Home {sun}!ys2!fiver!palowoda              | 415-623-8809 1200/2400
     {pacbell}!indetech!fiver!palowoda     |     An XBBS System                
Work {sun,pyramid,decwrl}!megatest!palowoda| 415-623-8806 1200/2400/19.2k TB+