From: Phil Blundell <philb@gnu.org>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: Missing GLIBC_<version> tags on binaries
Date: Wed, 02 Mar 2011 15:41:26 +0000 [thread overview]
Message-ID: <1299080486.23547.230.camel@phil-desktop> (raw)
In-Reply-To: <AANLkTimk6cXCRROwcD5cOkfarJuMkvg=A0cM_Um6oOSZ@mail.gmail.com>
On Tue, 2011-03-01 at 11:47 +0000, Otavio Salvador wrote:
> On Tue, Mar 1, 2011 at 11:35, Phil Blundell <philb@gnu.org> wrote:
> > On Mon, 2011-02-28 at 19:33 +0000, Otavio Salvador wrote:
> >> On Mon, Feb 28, 2011 at 17:17, Phil Blundell <philb@gnu.org> wrote:
> > I just tried linking xfreerdp by hand with gold and the resulting binary
> > seemed to come out fine. So I think this is indeed a bug in GNU ld.
>
> Personally I think we need to trace it down (we as project) since it
> can lead to broken and difficult to trace behaviour. It took 3 days
> until I managed to identify the symbol failure.
Yeah, that might be true. Or we could maybe just switch the default
linker to be gold, at least on targets that it supports.
> I am far from an expert on linking and GNU ld. For debugging it I'd
> need guidance.
I think the place to start looking would be _bfd_elf_merge_symbol(),
which is in bfd/elflink.c. This gets called by
elf_link_add_object_symbols() to record the syms that it finds and I
suspect that one or other of those functions is probably doing the wrong
thing.
Or, if you don't want to debug it yourself, you could try to create a
testcase that shows the problem and then file a bug report with binutils
upstream.
p.
next prev parent reply other threads:[~2011-03-02 15:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 19:03 Missing GLIBC_<version> tags on binaries Otavio Salvador
2011-02-25 20:00 ` Phil Blundell
2011-02-25 20:14 ` Otavio Salvador
2011-02-25 20:40 ` Phil Blundell
2011-02-25 20:58 ` Otavio Salvador
2011-02-25 21:34 ` Phil Blundell
2011-02-26 13:43 ` Otavio Salvador
2011-02-28 15:08 ` Phil Blundell
2011-02-28 16:49 ` Otavio Salvador
2011-02-28 17:17 ` Phil Blundell
2011-02-28 19:33 ` Otavio Salvador
2011-02-28 22:19 ` Khem Raj
2011-02-28 22:27 ` Otavio Salvador
2011-02-28 22:43 ` Khem Raj
2011-02-28 22:47 ` Otavio Salvador
2011-03-01 11:35 ` Phil Blundell
2011-03-01 11:47 ` Otavio Salvador
2011-03-02 15:41 ` Phil Blundell [this message]
2011-03-03 4:18 ` Khem Raj
2011-03-04 16:09 ` Phil Blundell
2011-03-04 16:54 ` Khem Raj
2011-03-04 21:47 ` Phil Blundell
2011-03-04 23:48 ` Khem Raj
2011-02-28 18:01 ` Kernel Module Compilation Nick Lee
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=1299080486.23547.230.camel@phil-desktop \
--to=philb@gnu.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.