From: Henry Bent <henry.r.bent@gmail.com>
To: Paul Winalski <paul.winalski@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>,
Rico Pajarola <rp@servium.ch>
Subject: Re: [TUHS] History of symbol preemption
Date: Mon, 13 Jan 2020 17:53:48 -0500 [thread overview]
Message-ID: <CAEdTPBcTHyJ+7k9RhyeYo4XrZ1SORdPLDTJobL-szThGS7mU3g@mail.gmail.com> (raw)
In-Reply-To: <CABH=_VSie4JQkr4Bs0GDbeByBkcP1qALBwOcQFH7q_5rtWhbqA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1348 bytes --]
On Mon, 13 Jan 2020 at 16:43, Paul Winalski <paul.winalski@gmail.com> wrote:
>
> > Now my memory is a little hazy... I think OSF/1-386 used MachO
> originally,
> > but I've forgotten. Switching the kernel to use ELF was one of the
> > differences between OSF1 and Tru64 IIRC.
>
> GEM never had to support Mach-O on any of its target platforms. DEC's
> Unix on MIPS used COFF. Tru64 used ELF exclusively. I don't know
> what Apple used for object files before OS X. IIRC NeXT was based on
> the CMU MACH microkernel and hence used Mach-O. OS X is
> FreeBSD-based, but it uses Mach-O.
>
OSF/1 on MIPS used ECOFF by default, but at least some versions could also
create and run ELF executables. That was all early to mid 1992, I
believe. I don't have my DECstation up right now to check but I'm sure
that the OSF/1 2.0 beta can do it, and I wouldn't be surprised if the
versions of 1.0 with the v3.0 compiler could also do it. I remember trying
to do ELF shared libraries but I think that support wasn't ready yet, which
is a shame because the ECOFF shared libraries on that platform are not fun
to deal with. Not as bad as SGI's ECOFF shared libraries on IRIX 4
though. I'm not sure if anyone outside of SGI ever bothered to put in the
work required to make one.
Wasn't OSF's original intent to use the OSF/ROSE object format?
-Henry
[-- Attachment #2: Type: text/html, Size: 1783 bytes --]
next prev parent reply other threads:[~2020-01-13 22:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 19:58 Paul Winalski
2020-01-13 20:46 ` Rico Pajarola
2020-01-13 21:04 ` Clem Cole
2020-01-13 21:40 ` Rico Pajarola
2020-01-13 21:44 ` Paul Winalski
2020-01-13 21:45 ` Rico Pajarola
2020-01-13 22:20 ` Larry McVoy
2020-01-13 21:42 ` Paul Winalski
2020-01-13 22:53 ` Henry Bent [this message]
2020-01-14 0:31 ` Clem Cole
2020-01-14 2:53 ` Rob Gingell
2020-01-14 19:21 ` [TUHS] two AIX items [was " Charles H Sauer
2020-01-14 20:31 ` Clem Cole
2020-01-14 23:22 ` Kevin Bowling
2020-01-15 16:41 ` Paul Winalski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEdTPBcTHyJ+7k9RhyeYo4XrZ1SORdPLDTJobL-szThGS7mU3g@mail.gmail.com \
--to=henry.r.bent@gmail.com \
--cc=paul.winalski@gmail.com \
--cc=rp@servium.ch \
--cc=tuhs@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).