From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ffmpeg: fix build for xtensa
Date: Wed, 25 Dec 2013 10:07:15 +0100 [thread overview]
Message-ID: <20131225100715.6473dee2@skate> (raw)
In-Reply-To: <dbffcc9384caa8009093e59944182ddfaafbdb5c.1387910266.git.baruch@tkos.co.il>
Dear Baruch Siach,
On Tue, 24 Dec 2013 20:37:46 +0200, Baruch Siach wrote:
> The ffmpeg package generates libraries that are too large for the xtensa
> default placement of literals in a dedicated section. Use
> -mtext-section-literal to place literals in the text section.
>
> Fixes
> http://autobuild.buildroot.net/results/606/60670d35f16c3b8fe19debf7f8e40a046a579520/
>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> package/ffmpeg/ffmpeg.mk | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/package/ffmpeg/ffmpeg.mk b/package/ffmpeg/ffmpeg.mk
> index 6685110..11703e3 100644
> --- a/package/ffmpeg/ffmpeg.mk
> +++ b/package/ffmpeg/ffmpeg.mk
> @@ -21,6 +21,10 @@ FFMPEG_CONF_OPT = \
> --disable-avfilter \
> $(if $(BR2_HAVE_DOCUMENTATION),,--disable-doc)
>
> +ifeq ($(BR2_xtensa),y)
> +FFMPEG_CONF_ENV += CFLAGS="$(TARGET_CFLAGS) -mtext-section-literals"
> +endif
Thanks, but to prevent future mistakes, could you provide a slightly
different version that does:
FFMPEG_CFLAGS = $(TARGET_CFLAGS)
ifeq ($(BR2_xtensa),y)
FFMPEG_CFLAGS += -mtext-section-literals
endif
FFMPEG_CONF_ENV = CFLAGS="$(FFMPEG_CFLAGS)"
This is a little bit better than your version in that we can add things
to CFLAGS in other places in ffmpeg.mk.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-12-25 9:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-24 18:37 [Buildroot] [PATCH] ffmpeg: fix build for xtensa Baruch Siach
2013-12-25 9:07 ` Thomas Petazzoni [this message]
2013-12-25 9:12 ` Baruch Siach
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=20131225100715.6473dee2@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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