From: "Jay Carlson" <nop@nop.com>
To: "Kevin D. Kissell" <kevink@mips.com>,
"Jay Carlson" <nop@place.org>, <linux-mips@oss.sgi.com>,
<linuxce-devel@linuxce.org>
Subject: RE: snow, a statically linked shared library MIPS ABI
Date: Thu, 22 Mar 2001 10:28:41 -0500 [thread overview]
Message-ID: <KEEOIBGCMINLAHMMNDJNMEHDCAAA.nop@nop.com> (raw)
In-Reply-To: <013a01c0b2db$749249a0$0deca8c0@Ulysses>
Kevin D. Kissell [mailto:kevink@mips.com] writes:
> > Instead, we can build shared library images located at fixed locations
> > in memory, with the location configured at library creation time.
> > Stub libraries are generated that hold the absolute addresses of
> > functions and data within the library image; programs (and other
> > libraries) link with the stubs.
>
> In fact, this is exactly how shared libraries worked under
> UNIX System V. It is inelegant, but economical.
Yeah. I bet there are precedents back in the mainframe world too. But my
first encounter with it was Linux a.out libraries, so it's a sign that I'm
truly a Linux Weenie that I think of it that way :-)
Jay
WARNING: multiple messages have this Message-ID (diff)
From: "Jay Carlson" <nop@nop.com>
To: "Kevin D. Kissell" <kevink@mips.com>, Jay Carlson <nop@place.org>,
linux-mips@oss.sgi.com, linuxce-devel@linuxce.org
Subject: RE: snow, a statically linked shared library MIPS ABI
Date: Thu, 22 Mar 2001 10:28:41 -0500 [thread overview]
Message-ID: <KEEOIBGCMINLAHMMNDJNMEHDCAAA.nop@nop.com> (raw)
Message-ID: <20010322152841.FScZWPhUkGjjd6TC31VxCqOn2ry4M-kaouAjtlAC6gY@z> (raw)
In-Reply-To: <013a01c0b2db$749249a0$0deca8c0@Ulysses>
Kevin D. Kissell [mailto:kevink@mips.com] writes:
> > Instead, we can build shared library images located at fixed locations
> > in memory, with the location configured at library creation time.
> > Stub libraries are generated that hold the absolute addresses of
> > functions and data within the library image; programs (and other
> > libraries) link with the stubs.
>
> In fact, this is exactly how shared libraries worked under
> UNIX System V. It is inelegant, but economical.
Yeah. I bet there are precedents back in the mainframe world too. But my
first encounter with it was Linux a.out libraries, so it's a sign that I'm
truly a Linux Weenie that I think of it that way :-)
Jay
next prev parent reply other threads:[~2001-03-22 15:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-22 13:23 snow, a statically linked shared library MIPS ABI Jay Carlson
2001-03-22 13:23 ` Jay Carlson
2001-03-22 14:21 ` Kevin D. Kissell
2001-03-22 14:21 ` Kevin D. Kissell
2001-03-22 15:28 ` Jay Carlson [this message]
2001-03-22 15:28 ` Jay Carlson
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=KEEOIBGCMINLAHMMNDJNMEHDCAAA.nop@nop.com \
--to=nop@nop.com \
--cc=kevink@mips.com \
--cc=linux-mips@oss.sgi.com \
--cc=linuxce-devel@linuxce.org \
--cc=nop@place.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