linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: Accessing global symbols from shared library
Date: Wed, 7 Feb 2001 16:21:33 -0500	[thread overview]
Message-ID: <20010207162133.A17743@drow.them.org> (raw)
In-Reply-To: <00cc01c0913a$7d647480$6c125acf@mrsl.com>; from moloney@mrsl.com on Wed, Feb 07, 2001 at 02:16:35PM -0500


On Wed, Feb 07, 2001 at 02:16:35PM -0500, Tim Moloney wrote:
>
> I am currently trying to port a Solaris application to Linux.  The
> Solaris application dynamically loads custom shared libraries which
> can access symbols in the main executable.  This is not a clean
> design, but it works.  From what I've seen so far, the Linux
> runtime loader does not allow a shared library to access symbols in
> the main executable.
>
> If someone knows of a linker switch or something that allows shared
> libraries to access global symbols, please let me know.

You're probably looking for -rdynamic...

Dan

/--------------------------------\  /--------------------------------\
|       Daniel Jacobowitz        |__|        SCS Class of 2002       |
|   Debian GNU/Linux Developer    __    Carnegie Mellon University   |
|         dan@debian.org         |  |       dmj+@andrew.cmu.edu      |
\--------------------------------/  \--------------------------------/

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-02-07 21:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-07 19:16 Accessing global symbols from shared library Tim Moloney
2001-02-07 21:21 ` Daniel Jacobowitz [this message]
2001-02-08  7:45 ` William Blew
2001-02-08 14:49   ` [solved] " Tim Moloney

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=20010207162133.A17743@drow.them.org \
    --to=dmj+@andrew.cmu.edu \
    --cc=linuxppc-dev@lists.linuxppc.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).