Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ffmpeg: disable for mips64r2 and mips64r6
Date: Thu, 26 May 2016 16:55:51 +0100	[thread overview]
Message-ID: <57471C87.2080100@imgtec.com> (raw)
In-Reply-To: <20160526164803.39a58695@free-electrons.com>

Hello Thomas,

On 26/05/16 15:48, Thomas Petazzoni wrote:
> Hello,
> 
> On Thu, 26 May 2016 07:26:26 +0200, Bernd Kuhls wrote:
> 
>>> +	# 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:
> 
> ffmpeg already has an architecture exception for nios2. So we could
> also replace that with a BR2_PACKAGE_FFMPEG_ARCH_SUPPORTS option, and
> therefore easily add the exception for mips64r2/r6.

Done and marked this patch as superseded.

Regards,

Vincent.

> We're down to very few build failures per day, so I would really like
> to get this issue out of the way, and see what other failures we have.
> ffmpeg on mips64r2/r6 is now the #1 failure.
> 
> Thomas
> 

      reply	other threads:[~2016-05-26 15:55 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
2016-05-26  9:36   ` Vicente Olivert Riera
2016-05-26 14:48   ` Thomas Petazzoni
2016-05-26 15:55     ` Vicente Olivert Riera [this message]

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=57471C87.2080100@imgtec.com \
    --to=vincent.riera@imgtec.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