From: Richard Purdie <richard.purdie@linuxfoundation.org>
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 12:45:41 +0000 [thread overview]
Message-ID: <1360845941.11225.107.camel@ted> (raw)
In-Reply-To: <511CDA28.5040504@mlbassoc.com>
On Thu, 2013-02-14 at 05:35 -0700, Gary Thomas wrote:
> I imported libav from meta-oe into my build so I can have additional
> gstreamer support. Now I'm seeing these warnings:
>
> 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?
It means the linker has to perform relocations on the .text segment at
runtime. This slows down loads and means more memory usage if two
applications use the library since the kernel can't share the mappings.
It will work its just inefficient.
The fix us usually to compile as position independent code using the pic
compiler option.
Cheers,
Richard (far from an expert on this)
next prev parent reply other threads:[~2013-02-14 13:02 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 [this message]
2013-02-14 13:10 ` Phil Blundell
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=1360845941.11225.107.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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