From: "Tim Moloney" <moloney@mrsl•com>
To: "William Blew" <wblew@home•com>
Cc: <linuxppc-dev@lists•linuxppc.org>,
<yellowdog-devel@lists•yellowdoglinux.com>
Subject: Re: [solved] Accessing global symbols from shared library
Date: Thu, 8 Feb 2001 09:49:12 -0500 [thread overview]
Message-ID: <003d01c091de$4d504f90$6c125acf@mrsl.com> (raw)
In-Reply-To: Pine.LNX.4.30.0102072345240.5464-100000@apollo.kulian.net
Thanks for the response.
After rereading the ld man page, I discovered the -export-dynamic
switch which does exactly what I want. I was either blind or
confused the first time I read the ld man page.
Thanks again.
Tim Moloney
ManTech Real-time Systems Laboratory
2015 Cattlemen Road
Sarasota, FL 34232
(941) 377-6775 x208
----- Original Message -----
From: "William Blew" <wblew@home•com>
To: "Tim Moloney" <moloney@mrsl•com>
Cc: <linuxppc-dev@lists•linuxppc.org>;
<yellowdog-devel@lists•yellowdoglinux.com>
Sent: Thursday, February 08, 2001 2:45 AM
Subject: Re: Accessing global symbols from shared library
> On Wed, 7 Feb 2001, Tim Moloney wrote:
>
> I suggest taking a look at the implementation of the X server. It
achieves
> such a feat routinely.
>
> > 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.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-02-08 14:49 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
2001-02-08 7:45 ` William Blew
2001-02-08 14:49 ` Tim Moloney [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='003d01c091de$4d504f90$6c125acf@mrsl.com' \
--to=moloney@mrsl$(echo .)com \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
--cc=wblew@home$(echo .)com \
--cc=yellowdog-devel@lists$(echo .)yellowdoglinux.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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