public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "H . J . Lu" <hjl@lucon.org>
To: Alejandro Arredondo <babaji@letodesigns.every1.net>
Cc: gcc@gcc.gnu.org
Subject: Re: Question: dynamic libraries?
Date: Thu, 21 Sep 2000 15:21:00 -0000	[thread overview]
Message-ID: <20000921152142.A6676@lucon.org> (raw)
In-Reply-To: <20000921215720.4C4782740@sitemail.everyone.net>

On Thu, Sep 21, 2000 at 02:57:20PM -0700, Alejandro Arredondo wrote:
> Hello,
> 
>    I don't know if this is the right place to ask for
> this question, but I would like to know how can I 
> compile a dynamic library in Linux? or where can I get
> information about dynamic libraries for Linux?

I have a very old paper:

http://ftp.valinux.com/pub/support/hjl/doc/elf.ps.gz

Some contents are out of date, like libc 5 vs glibc 2. But it may be
still useful to you.


H.J.

  reply	other threads:[~2000-09-21 15:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-21 14:57 Alejandro Arredondo
2000-09-21 15:21 ` H . J . Lu [this message]
2000-09-21 17:08   ` Paul Schulz

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=20000921152142.A6676@lucon.org \
    --to=hjl@lucon.org \
    --cc=babaji@letodesigns.every1.net \
    --cc=gcc@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).