From: Alan Modra <amodra@bigpond.net.au>
To: "Peter S. Mazinger" <ps.m@gmx.net>
Cc: "Peter S. Mazinger" <mps@bridge.intra>, binutils@sourceware.org
Subject: Re: weak and strong aliases for global data fail
Date: Wed, 24 May 2006 17:05:00 -0000 [thread overview]
Message-ID: <20060524141351.GA25824@bubble.grove.modra.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0605241443230.26077-100000@lnx.bridge.intra>
On Wed, May 24, 2006 at 03:16:26PM +0200, Peter S. Mazinger wrote:
> I have only renamed the internally
> used opt* to __opt* and provided a weak resp. strong alias to the
> externally visible version
Symbol aliases in ELF shared libs don't work as you think they should.
This is not a bug in the compiler, linker, or ld.so.
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next prev parent reply other threads:[~2006-05-24 14:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-17 17:02 Peter S. Mazinger
2006-05-23 0:12 ` Peter S. Mazinger
2006-05-23 9:35 ` Alan Modra
2006-05-24 15:06 ` Peter S. Mazinger
2006-05-24 17:05 ` Alan Modra [this message]
2006-05-23 10:29 ` Mike Frysinger
2006-05-24 15:34 ` Peter S. Mazinger
2006-05-26 2:44 ` Mike Frysinger
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=20060524141351.GA25824@bubble.grove.modra.org \
--to=amodra@bigpond.net.au \
--cc=binutils@sourceware.org \
--cc=mps@bridge.intra \
--cc=ps.m@gmx.net \
/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).