All of lore.kernel.org
 help / color / mirror / Atom feed
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: Tue, 01 Mar 2011 11:35:08 +0000	[thread overview]
Message-ID: <1298979308.23547.67.camel@phil-desktop> (raw)
In-Reply-To: <AANLkTimomznky1rBn5QTqzS16O6Lk3VxHUx1pG+ULe3v@mail.gmail.com>

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:
> ...
> > That's definitely not a patch that you ought to check in, though.  For
> > wider consumption I guess there ought to be some kind of knob that
> > DISTROs can tweak to select the linker of their choice.  As far as I
> > know there isn't any such mechanism at present.
> 
> One interesting way to "fix" the issue is to explicitly link against
> -lpthread however it seems *wrong*.
> 
> It seems to be a gcc bug since -pthread is suppose to handle all the
> needed background for it to work and seems to be doing it wrong.

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.

It does seem to be sensitive to the order in which things are mentioned
in the command line: if you put -lpthread first then GNU ld gets it
right.  But if -lpthread is at the end then it seems to fail to pick up
the versioning information for symbols which are also mentioned (even as
SHT_UNDEF) in other objects.  Clearly that can't be the whole story
though because if it was that simple then it would be failing with
everything.  I guess you need to either debug this further or switch to
using gold for your own builds.

p.





  parent reply	other threads:[~2011-03-01 11:31 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 [this message]
2011-03-01 11:47                       ` Otavio Salvador
2011-03-02 15:41                         ` Phil Blundell
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=1298979308.23547.67.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.