From: Leo Famulari <leo@famulari.name>
To: rain1@openmailbox.org
Cc: guix-devel@gnu.org
Subject: Re: ffmpeg package update
Date: Thu, 24 Mar 2016 13:42:04 -0400 [thread overview]
Message-ID: <20160324174204.GB29843@jasmine> (raw)
In-Reply-To: <77beba44ab232a32670c6c1dce4ef56c@openmailbox.org>
On Thu, Mar 24, 2016 at 04:58:43PM +0000, rain1@openmailbox.org wrote:
> Hello,
>
> Our ffmpeg package is old (version 2.8.6 but 3.0 is available now).
>
> I noticed this because I found a segfault in a program that uses mpv: mkdir
> -p a ; mpv a. Updating ffmpeg fixes this.
So, passing an empty directory to mpv causes a segmentation fault? Do
you know if it was fixed "deliberately" by ffmpeg (or mpv, not sure
which program is responsible here), or just as a side effect of some
other change? If the latter, they may be interested to know about the
bug.
>
> Removed libquvi from it as that has been removed from mpv and is not being
> updated.
We like to commit unrelated changes separately. So, unless the removal
of libquvi is required to build version 3.0 of ffmpeg, I think it should
be done in a separate commit. Can you revise your patches?
Also, is libquvi causing some problem with our ffmpeg package? I don't
understand the reason for removing it; I'm not familiar with quvi at
all.
>
> Changed a configure flag --disable-mipsdspr1 to --disable-mipsdsp - this is
> just a rename. You can read about this here
> <https://ffmpeg.org/pipermail/ffmpeg-devel/2015-November/183375.html> since
> it's just a rename I do not think this will break ffmpeg on MIPS.
Okay, thanks for the info.
next prev parent reply other threads:[~2016-03-24 17:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 16:58 ffmpeg package update rain1
2016-03-24 17:42 ` Leo Famulari [this message]
2016-03-27 23:20 ` Leo Famulari
2016-03-28 6:18 ` Efraim Flashner
2016-03-28 6:34 ` Efraim Flashner
2016-04-03 16:55 ` Efraim Flashner
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160324174204.GB29843@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=rain1@openmailbox.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).