From: "H . J . Lu" <hjl@lucon.org>
To: "Zagorodnev, Grigory" <Grigory_Zagorodnev@stl.sarov.ru>
Cc: "'binutils@sources.redhat.com'" <binutils@sources.redhat.com>
Subject: Re: Shared library question
Date: Wed, 19 Jun 2002 07:08:00 -0000 [thread overview]
Message-ID: <20020619070856.A24023@lucon.org> (raw)
In-Reply-To: <51524B6C689ED4118D4F0090273ACE32928844@odyssey.stl.sarov.ru>; from Grigory_Zagorodnev@stl.sarov.ru on Wed, Jun 19, 2002 at 05:58:06PM +0400
On Wed, Jun 19, 2002 at 05:58:06PM +0400, Zagorodnev, Grigory wrote:
> There is a little question about...
>
> I have a shared library contaning some symbol 'foo'. This symbol has no any
> version defined.
>
> Is there a way to keep symbol accessible at run-time but hide it at build
> time?
> So any application previously built with (linked against) that library stay
> workable but any new application will not see this symbol i.e. linker will
> not resolve symbol foo from that library.
You didn't say if you could rebuild the shared library from source.
H.J.
next prev parent reply other threads:[~2002-06-19 14:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-19 6:56 Zagorodnev, Grigory
2002-06-19 7:08 ` H . J . Lu [this message]
2002-06-19 7:29 ` Daniel Jacobowitz
2002-06-19 7:39 ` H . J . Lu
2002-06-19 7:22 Zagorodnev, Grigory
2002-06-19 7:27 ` H . J . Lu
2002-06-19 7:45 Zagorodnev, Grigory
2002-06-19 7:54 ` H . J . Lu
2002-06-19 7:57 ` Jakub Jelinek
2002-06-19 7:55 Zagorodnev, Grigory
2002-06-19 21:42 Zagorodnev, Grigory
2002-06-20 0:05 ` Jakub Jelinek
2002-06-20 4:33 Zagorodnev, Grigory
2002-06-20 4:40 ` Jakub Jelinek
2002-07-17 5:40 Zagorodnev, Grigory
2002-07-17 7:58 ` H. J. Lu
2002-07-18 7:55 Zagorodnev, Grigory
2002-07-18 8:43 ` H. J. Lu
2002-07-18 10:46 Zagorodnev, Grigory
2002-07-18 12:01 ` H. J. Lu
2002-07-19 1:36 Zagorodnev, Grigory
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=20020619070856.A24023@lucon.org \
--to=hjl@lucon.org \
--cc=Grigory_Zagorodnev@stl.sarov.ru \
--cc=binutils@sources.redhat.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 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).