All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] ffmpeg issue with MIPS
Date: Wed, 3 Jan 2018 22:50:57 +0100	[thread overview]
Message-ID: <20180103225057.79846679@windsurf.lan> (raw)
In-Reply-To: <CAMbDF3KbAxppKmMVLWduL6B1RSLPriuErWcVTOt2wx-=+TE7GQ@mail.gmail.com>

Hello,

On Wed, 3 Jan 2018 22:43:40 +0100, Johannes Schmitz wrote:
> Short summary of a MIPS (ci20) related bug:
> 
> In
> "package/ffmpeg/ffmpeg.mk"
> the decision is made to build ffmpeg with or without mipsfpu support:
> 
> ifeq ($(BR2_mips)$(BR2_mipsel)$(BR2_mips64)$(BR2_mips64el),y)
> ifeq ($(BR2_MIPS_SOFT_FLOAT),y)
> FFMPEG_CONF_OPTS += --disable-mipsfpu
> else
> FFMPEG_CONF_OPTS += --enable-mipsfpu
> endif
> endif # MIPS
> 
> This apparently goes wrong in a ci20 build.
> Result:
> squeezelite can not be executed.
> See:
> https://pastebin.com/nsseiAdV
> Error is at the end
> trying file=/usr/lib/libavcodec.so.57  -> needs FR1 mode

I guess this has been discussed on IRC, but the discussion has been
very long, and I didn't follow all of it. So here are some basic
questions:

 - What is your Buildroot configuration ?

 - What is the exact MIPS processor you're running this on ?

 - Does it work when --disable-mipsfpu is passed, or when
   --enable-mipsfpu is passed ?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2018-01-03 21:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-03 21:43 [Buildroot] ffmpeg issue with MIPS Johannes Schmitz
2018-01-03 21:50 ` Thomas Petazzoni [this message]
     [not found]   ` <CAMbDF3+pfHWMz1iYOxY-rnBJkBRhxw534dGacPbKMLF_+OQTHg@mail.gmail.com>
2018-01-03 22:05     ` Thomas Petazzoni
2018-01-03 22:13       ` Johannes Schmitz
2018-01-03 23:32         ` Johannes Schmitz

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=20180103225057.79846679@windsurf.lan \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.