From: "Tim Moloney" <moloney@mrsl.com>
To: <linuxppc-dev@lists.linuxppc.org>,
<yellowdog-devel@lists.yellowdoglinux.com>
Subject: Accessing global symbols from shared library
Date: Wed, 7 Feb 2001 14:16:35 -0500 [thread overview]
Message-ID: <00cc01c0913a$7d647480$6c125acf@mrsl.com> (raw)
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.
Tim Moloney
ManTech Real-time Systems Laboratory
2015 Cattlemen Road
Sarasota, FL 34232
(941) 377-6775 x208
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-02-07 19:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-07 19:16 Tim Moloney [this message]
2001-02-07 21:21 ` Accessing global symbols from shared library Daniel Jacobowitz
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='00cc01c0913a$7d647480$6c125acf@mrsl.com' \
--to=moloney@mrsl.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=yellowdog-devel@lists.yellowdoglinux.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.