From: Phil Blundell <pb@pbcl.net>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: What do these warnings mean?
Date: Thu, 14 Feb 2013 13:10:36 +0000 [thread overview]
Message-ID: <1360847436.4246.122.camel@phil-desktop.brightsign> (raw)
In-Reply-To: <511CDA28.5040504@mlbassoc.com>
On Thu, 2013-02-14 at 05:35 -0700, Gary Thomas wrote:
> WARNING: QA Issue: ELF binary
> '/home/local/p82_soft/tmp/work/cortexa9-vfp-neon-amltd-linux-gnueabi/gst-plugins-bad/0.10.23-r3.ti1.6.4.3/packages-split/gst-plugins-bad-vp8/usr/lib/gstreamer-0.10/libgstvp8.so'
> has relocations in .text
> WARNING: QA Issue: ELF binary '/home/local/p82_soft/tmp/work/cortexa9-vfp-neon-amltd-linux-gnueabi/libav/0.8.3-r0/packages-split/libavcodec/usr/lib/libavcodec.so.53.35.0' has
> relocations in .text
>
> Exactly what do these mean? What do I do to get rid of them?
Generally they mean that some non-PIC code has leaked into a shared
library. The most common way for that to happen is for a DSO final link
to accidentally pull in some members from a static library. There are a
few other possible causes as well, mostly toolchain bugs or limitations
(you used to get this under some circumstances when enabling full unwind
tables on MIPS for example), but non-PIC code is the most likely one.
You can use readelf or objdump to inspect the relocation table for the
files in question. In most cases there is a fairly obvious culprit,
e.g. an R_ARM_PC24 reloc with an incriminating function name.
Having relocations in .text is undesirable because it wastes memory and
slows down program startup. They can occasionally cause more severe
problems: for example, if were using SELinux then you might find that
your security policy didn't allow those binaries to be run at all.
(This was the default policy on Fedora for a while; I've no idea if it
still is.)
p.
prev parent reply other threads:[~2013-02-14 13:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 12:35 What do these warnings mean? Gary Thomas
2013-02-14 12:45 ` Richard Purdie
2013-02-14 13:10 ` Phil Blundell [this message]
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=1360847436.4246.122.camel@phil-desktop.brightsign \
--to=pb@pbcl.net \
--cc=gary@mlbassoc.com \
--cc=openembedded-core@lists.openembedded.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