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: Mon, 28 Feb 2011 17:17:02 +0000 [thread overview]
Message-ID: <1298913422.23547.20.camel@phil-desktop> (raw)
In-Reply-To: <AANLkTimyU4bSm9tM2LO5bMoqiFQqZXxt5Js7fg0B_HhJ@mail.gmail.com>
On Mon, 2011-02-28 at 16:49 +0000, Otavio Salvador wrote:
> On Mon, Feb 28, 2011 at 15:08, Phil Blundell <philb@gnu.org> wrote:
> ...
> > It looks at first inspection as though this might be a linker bug,
> > though I can't immediately see anything very special about freerdp that
> > looks like it would be causing things to go wrong. Some further
> > debugging needed, though it'd be interesting to know whether it works
> > any better with gold for example.
>
> How could I make it to use gold? I am stuck on that issue since it is
> block us to advance on the development of a product :-(
Good question. For local testing, I think it might be sufficient to
add:
EXTRA_OECONF += "--enable-gold=default"
to your binutils-cross recipe. You can verify whether it's worked by
running "i586-oe-linux-ld --version" and checking to see whether it
claims to be gold or not.
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.
p.
next prev parent reply other threads:[~2011-02-28 17:13 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 [this message]
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
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=1298913422.23547.20.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.