From: "H. J. Lu" <hjl@lucon.org>
To: "Zagorodnev, Grigory" <Grigory_Zagorodnev@stl.sarov.ru>
Cc: 'Jakub Jelinek' <jakub@redhat.com>,
"'binutils@sources.redhat.com'" <binutils@sources.redhat.com>
Subject: Re: Shared library question
Date: Wed, 17 Jul 2002 07:58:00 -0000 [thread overview]
Message-ID: <20020717075030.A10176@lucon.org> (raw)
In-Reply-To: <51524B6C689ED4118D4F0090273ACE329288B6@odyssey.stl.sarov.ru>; from Grigory_Zagorodnev@stl.sarov.ru on Wed, Jul 17, 2002 at 03:03:28PM +0400
On Wed, Jul 17, 2002 at 03:03:28PM +0400, Zagorodnev, Grigory wrote:
> >If you'll do:
> >VER_1.0 { global: foo; bar; baz; local: *; };
> >VER_1.1 { } VER_1.0;
> >and .symver __real_foo, foo@VER_1.0
> >then program/libs linked against non-versioned foo will resolve to
> >foo@VER_1.0, while ld won't use foo.
>
> Well...
> This solution works fine for small test-cases. But I have problems running
> huge real application. Same conditions, same library, same symbol
> information in the application but ld.so does not resolve reference to
> foo@VER_1.0.
>
It should work. You need to provide more info.
H.J.
next prev parent reply other threads:[~2002-07-17 14:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-17 5:40 Zagorodnev, Grigory
2002-07-17 7:58 ` H. J. Lu [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-19 1:36 Zagorodnev, Grigory
2002-07-18 10:46 Zagorodnev, Grigory
2002-07-18 12:01 ` H. J. Lu
2002-07-18 7:55 Zagorodnev, Grigory
2002-07-18 8:43 ` H. J. Lu
2002-06-20 4:33 Zagorodnev, Grigory
2002-06-20 4:40 ` Jakub Jelinek
2002-06-19 21:42 Zagorodnev, Grigory
2002-06-20 0:05 ` Jakub Jelinek
2002-06-19 7:55 Zagorodnev, Grigory
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:22 Zagorodnev, Grigory
2002-06-19 7:27 ` H . J . Lu
2002-06-19 6:56 Zagorodnev, Grigory
2002-06-19 7:08 ` H . J . Lu
2002-06-19 7:29 ` Daniel Jacobowitz
2002-06-19 7:39 ` H . J . Lu
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=20020717075030.A10176@lucon.org \
--to=hjl@lucon.org \
--cc=Grigory_Zagorodnev@stl.sarov.ru \
--cc=binutils@sources.redhat.com \
--cc=jakub@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).