From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] libvpx: force arm mode to be able to link with ffmpeg where arm mode already is forced
Date: Mon, 24 Jan 2011 11:24:41 +0100 [thread overview]
Message-ID: <20110124102441.GA3616@jama> (raw)
In-Reply-To: <4D2FBF32.30402@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2535 bytes --]
On Thu, Jan 13, 2011 at 07:12:50PM -0800, Khem Raj wrote:
> On 1/12/2011 11:31 PM, Martin Jansa wrote:
> > On Wed, Jan 12, 2011 at 10:28:10AM -0800, Khem Raj wrote:
> >> On 1/12/2011 3:48 AM, Martin Jansa wrote:
> >>> Signed-off-by: Martin Jansa<Martin.Jansa@gmail.com>
> >>
> >> hmmm what issues do u see if you build it with thumb mode.
> >
> > +# ffmpeg links with this and fails
> > +# sysroots/armv4t-oe-linux-gnueabi/usr/lib/libvpx.a(vpx_encoder.c.o)(.text+0xc4): unresolvable R_ARM_THM_CALL relocation against symbol `memcpy@@GLIBC_2.4'
> >
> > and full log is here
> > http://tinderbox.openembedded.org/packages/1398033/
>
> Its not clear in the logs but is libvpx using -fPIE compiler option ? if
> yes then you should remove it and then it will work.
only -fPIC and even with added -fno-PIE it still fails here (only with
binutils-2.21, haven't seen it with 2.20)
> >
> >>> ---
> >>> recipes/webm/libvpx.inc | 6 +++++-
> >>> 1 files changed, 5 insertions(+), 1 deletions(-)
> >>>
> >>> diff --git a/recipes/webm/libvpx.inc b/recipes/webm/libvpx.inc
> >>> index 9913d5b..9d40945 100644
> >>> --- a/recipes/webm/libvpx.inc
> >>> +++ b/recipes/webm/libvpx.inc
> >>> @@ -1,11 +1,15 @@
> >>> DESCRIPTION = "vpx Multi-Format Codec SDK"
> >>> LICENSE = "BSD"
> >>>
> >>> -INC_PR = "r5"
> >>> +INC_PR = "r6"
> >>>
> >>> SRC_URI = "git://review.webmproject.org/libvpx.git;protocol=git;tag=v${PV}"
> >>> S = "${WORKDIR}/git"
> >>>
> >>> +# ffmpeg links with this and fails
> >>> +# sysroots/armv4t-oe-linux-gnueabi/usr/lib/libvpx.a(vpx_encoder.c.o)(.text+0xc4): unresolvable R_ARM_THM_CALL relocation against symbol `memcpy@@GLIBC_2.4'
> >>> +ARM_INSTRUCTION_SET = "arm"
> >>> +
> >>> CFLAGS += "-fPIC"
> >>>
> >>> export CC
> >>
> >>
> >> _______________________________________________
> >> Openembedded-devel mailing list
> >> Openembedded-devel@lists.openembedded.org
> >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> >
> >
> >
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2011-01-24 10:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 11:48 [PATCH] libvpx: force arm mode to be able to link with ffmpeg where arm mode already is forced Martin Jansa
2011-01-12 18:28 ` Khem Raj
2011-01-13 7:31 ` Martin Jansa
2011-01-14 3:12 ` Khem Raj
2011-01-24 10:24 ` Martin Jansa [this message]
2011-01-24 15:44 ` Khem Raj
2011-03-01 8:37 ` [PATCHv2] " Martin Jansa
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=20110124102441.GA3616@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@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