public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: James E Wilson <wilson@specifixinc.com>
To: fromfast@rainbarrel.com
Cc: gcc@gcc.gnu.org
Subject: Re: dynamic linking question
Date: Sat, 04 Sep 2004 00:42:00 -0000	[thread overview]
Message-ID: <41390F84.80206@specifixinc.com> (raw)
In-Reply-To: <49443.64.107.161.130.1094229426.squirrel@64.107.161.130>

Jim Norris wrote:
> I'm trying to find documentation on how to dynamically link to a shared
> object at run time. I found something that describes how to do it in C
> using gcc but that's not exactly what I need.

GCC doesn't do any of this stuff.  Try looking at the static linker 
(binutils) and the dynamic linker (glibc for linux).

Also, you might want to look at the target ABI documentation, but since 
you didn't mention the target, I can't point you at it.  Every target 
does this differently.  Assuming this is linux, you might start at
   http://www.linuxbase.org
-- 
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com

      parent reply	other threads:[~2004-09-04  0:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-03 16:37 Jim Norris
2004-09-03 18:14 ` Joe Buck
2004-09-04  0:42 ` James E Wilson [this message]

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=41390F84.80206@specifixinc.com \
    --to=wilson@specifixinc.com \
    --cc=fromfast@rainbarrel.com \
    --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).