From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ffmpeg: fix coldfire compile issue
Date: Sat, 29 Apr 2017 14:03:03 +0200 [thread overview]
Message-ID: <20170429140303.3433bcf3@free-electrons.com> (raw)
In-Reply-To: <20170429073019.GA22285@waldemar-brodkorb.de>
Hello,
On Sat, 29 Apr 2017 09:30:19 +0200, Waldemar Brodkorb wrote:
> Fixes:
> http://autobuild.buildroot.net/results/7e95ac6d78bc1732127bea084b4f791e52637abd
>
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
> ...llow-to-directly-use-pthreads-atomics-com.patch | 65 ++++++++++++++++++++++
> package/ffmpeg/ffmpeg.mk | 6 ++
> 2 files changed, 71 insertions(+)
> create mode 100644 package/ffmpeg/0002-configure-allow-to-directly-use-pthreads-atomics-com.patch
I'm hesitating: do we apply this fix, or simply adjust
BR2_PACKAGE_FFMPEG_ARCH_SUPPORTS do disallow using ffmpeg on
BR2_m68k_cf ? After all, who is realistically going to use ffmpeg on
m68k_cf ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-04-29 12:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-29 7:30 [Buildroot] [PATCH] ffmpeg: fix coldfire compile issue Waldemar Brodkorb
2017-04-29 12:03 ` Thomas Petazzoni [this message]
2017-05-29 21:39 ` Thomas Petazzoni
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=20170429140303.3433bcf3@free-electrons.com \
--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