On Wed, Sep 05, 2018 at 03:39:20PM -0400, Ethan Dicks via cctalk wrote:
> Hi, All,
>
> I have a backup of some old code that I thought came from a Sun3
> machine, and indeed, there _are_ binaries on there, in a directory
> 'sun' that _do_ run on a Sun3, verified under emulation with "tme".
>
>
The other way to tell would be if they haven't had their symbols
stripped and look at the libaries they are compiled with. This
stuff predates shared libraries. There are probably vendor strings
in there.
On 9/5/18 2:26 PM, Al Kossow via cctalk wrote:
> anything that came from Unisoft Sys V or
anything that came from Unisoft Sys V or early Motorola Sys V
ftp://ftp.oreilly.co.jp/palm/Linux/gcc/gdb-4.16/bfd/coff-aux.c
for example.
On 9/5/18 12:39 PM, Ethan Dicks via cctalk wrote:
> Hi, All,
>
> I have a backup of some old code that I thought came from a Sun3
> machine, and indeed,
On Wed, 9/5/18, Ethan Dicks via cctalk wrote:
> The part that puzzles me is the collection of object files and
> binaries in the directory above that. 'file' tells me that they are
> "m68k COFF" files. From what I've read so far, COFF binaries are from
> System V Release 2-4. What I can't
On Wed, Sep 5, 2018 at 1:39 PM Ethan Dicks via cctalk
wrote:
> Additionally, I'm reading that FreeBSD has a binary compatibility
> layer for COFF but I wonder if that's for Intel binaries only or if it
> extends to m68k.
>
FreeBSD never ran on 68k, so I think that would be no.
NetBSD, however,
Hi, All,
I have a backup of some old code that I thought came from a Sun3
machine, and indeed, there _are_ binaries on there, in a directory
'sun' that _do_ run on a Sun3, verified under emulation with "tme".
The part that puzzles me is the collection of object files and
binaries in the
