From: Leo Famulari <leo@famulari.name>
To: Arne Babenhauserheide <arne_bab@web.de>
Cc: 34050@debbugs.gnu.org
Subject: [bug#34050] [PATCH] gnu: Add libaom and activate AV1 support in ffmpeg. updated
Date: Mon, 4 Mar 2019 22:18:10 -0500 [thread overview]
Message-ID: <20190305031810.GA14749@jasmine.lan> (raw)
In-Reply-To: <87va2l4l02.fsf@web.de>
[-- Attachment #1: Type: text/plain, Size: 993 bytes --]
On Sat, Jan 19, 2019 at 12:13:49AM +0100, Arne Babenhauserheide wrote:
> The following patch now avoids breaking ffmpeg-3.4.
>
> From f4406df33f1ed6dd64757f43ea7354fd5a88d2d3 Mon Sep 17 00:00:00 2001
> From: Arne Babenhauserheide <arne_bab@web.de>
> Date: Sat, 12 Jan 2019 01:24:58 +0100
> Subject: [PATCH] gnu: Add libaom and activate AV1 support in ffmpeg.
>
> * gnu/packages/video.scm (libaom): New variable.
> * gnu/packages/video.scm (ffmpeg): Add libaom support.
> [inputs] new input libaom.
> [arguments] new configure-flag --enable-libaom.
> * gnu/packages/video.scm (ffmpeg-3.4): filter out libaom.
> [inputs] remove inherited libaom
> [arguments] remove inherited configure-flag --enable-libaom
Sorry, this fell through the cracks.
I noticed that ffmpeg-for-stepmania (FFmpeg 2) isn't addressed by this
patch.
So, I built ffmpeg-3.4 without filtering out the libaom stuff and it
does build, so I'm wondering how it breaks?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-03-05 3:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-12 0:24 [bug#34050] [PATCH] gnu: Add libaom and activate AV1 support in ffmpeg Arne Babenhauserheide
[not found] ` <handler.34050.B.154725368427570.ack@debbugs.gnu.org>
2019-01-12 12:13 ` [bug#34050] Aw: bug#34050: Acknowledgement ([PATCH] gnu: Add libaom and activate AV1 support in ffmpeg.) Arne Babenhauserheide
2019-01-12 23:33 ` Leo Famulari
2019-01-13 22:19 ` Ludovic Courtès
2019-01-18 23:13 ` [bug#34050] [PATCH] gnu: Add libaom and activate AV1 support in ffmpeg. updated Arne Babenhauserheide
2019-03-05 3:18 ` Leo Famulari [this message]
2019-03-05 15:57 ` Arne Babenhauserheide
2019-03-05 20:08 ` Leo Famulari
2019-03-05 20:12 ` Leo Famulari
2019-03-05 23:30 ` bug#34050: " Leo Famulari
2019-03-06 19:24 ` [bug#34050] " Arne Babenhauserheide
2019-03-06 20:02 ` Leo Famulari
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=20190305031810.GA14749@jasmine.lan \
--to=leo@famulari.name \
--cc=34050@debbugs.gnu.org \
--cc=arne_bab@web.de \
/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).