From: "Peter S. Mazinger" <ps.m@gmx.net>
To: Daniel Jacobowitz <drow@false.org>
Cc: binutils@sourceware.org
Subject: Re: objcopy --weaken
Date: Wed, 12 Apr 2006 04:37:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0604120149310.4366-100000@lnx.bridge.intra> (raw)
In-Reply-To: <20060411230829.GA7671@nevyn.them.org>
On Tue, 11 Apr 2006, Daniel Jacobowitz wrote:
> On Wed, Apr 12, 2006 at 01:05:48AM +0200, Peter S. Mazinger wrote:
> > Hello!
> >
> > The objcopy --weaken command suggests that it is able to change all
> > (global) symbols to weak. Running it against an object file it does it,
> > but running it against a shared lib does not change anything.
>
> What do you expect it to do?
I would have expected to change all global(strong) to weak.
> In modern shared library lookup, dynamic exported symbols are the same
> whether they are strong or weak.
That is true if modern=glibc (there is though some compat
option/environment setting to disable this behaviour).
At link time if libpthread.so and libc.so provide the same symbol (could
happen w/ any other 2 libs, the example is "real-life", the linker fails,
if one of them is not weak.
Peter
--
Peter S. Mazinger <ps dot m at gmx dot net> ID: 0xA5F059F2
Key fingerprint = 92A4 31E1 56BC 3D5A 2D08 BB6E C389 975E A5F0 59F2
next prev parent reply other threads:[~2006-04-11 23:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1144794193.13900.ezmlm@sourceware.org>
2006-04-11 23:08 ` Peter S. Mazinger
2006-04-11 23:12 ` Daniel Jacobowitz
2006-04-12 4:37 ` Peter S. Mazinger [this message]
2006-04-12 4:37 ` Daniel Jacobowitz
2006-04-12 10:47 ` Peter S. Mazinger
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=Pine.LNX.4.44.0604120149310.4366-100000@lnx.bridge.intra \
--to=ps.m@gmx.net \
--cc=binutils@sourceware.org \
--cc=drow@false.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 read-only IMAP folder(s) and NNTP newsgroup(s).