From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ffmpeg: disable for mips64r2 and mips64r6
Date: Thu, 26 May 2016 07:26:26 +0200 [thread overview]
Message-ID: <21ei1dxhr9.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: 1464192852-53397-1-git-send-email-Vincent.Riera@imgtec.com
Hi,
Am Wed, 25 May 2016 17:14:12 +0100 schrieb Vicente Olivert Riera:
> This commit can be reverted in the next ffmpeg's version bump.
[...]
> + # MIPS architecture detection is not accurate for 64-bit
> + # variants. This has been already fixed upstream, so please
> + # remove it in the next version bump.
> + depends on !BR2_mips_64r2 && !BR2_mips_64r6
you need to propagate this exception as reverse dependency to the following packages:
- gst1-libav
- kodi
- minidlna
- mpd
- mpv
- opencv
- opencv3
- squeezelite
- tovid
Imho this is too much work, we should live with the build error and
bump ffmpeg to 3.0.2 after the next buildroot release to fix the
problem. On github you can test my patch series already:
https://github.com/bkuhls/buildroot/tree/ffmpeg3
The main problem is that vlc 2.2.x is incompatible with ffmpeg3, only
vlc master branch works, this branch will be released as vlc 3.0
sometime in the future. We would carry a pre-released version of vlc
in buildroot, which is something we want to avoid if possible.
Before the ffmpeg 3 vs. vlc problem arose I thought we could remove
the vlc warning in its Config.in:
https://git.busybox.net/buildroot/tree/package/vlc/Config.in#n2
When bumping to a pre-release version we should keep it ;)
Regards, Bernd
next prev parent reply other threads:[~2016-05-26 5:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 16:14 [Buildroot] [PATCH] ffmpeg: disable for mips64r2 and mips64r6 Vicente Olivert Riera
2016-05-26 5:26 ` Bernd Kuhls [this message]
2016-05-26 9:36 ` Vicente Olivert Riera
2016-05-26 14:48 ` Thomas Petazzoni
2016-05-26 15:55 ` Vicente Olivert Riera
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=21ei1dxhr9.ln2@ID-313208.user.individual.net \
--to=bernd.kuhls@t-online.de \
--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