all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Tue, 5 Mar 2019 15:08:37 -0500	[thread overview]
Message-ID: <20190305200837.GA14036@jasmine.lan> (raw)
In-Reply-To: <87y35tiaaa.fsf@web.de>

[-- Attachment #1: Type: text/plain, Size: 318 bytes --]

On Tue, Mar 05, 2019 at 04:57:33PM +0100, Arne Babenhauserheide wrote:
> It broke because ffmpeg-3.4 does not have the --enable-libaom configure
> flag.
> 
> What’s the exact patch you applied?

I'm seeing the build fail now. Auto-compilation of my Git tree must not
have been working previously. Testing...

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-03-05 20:09 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
2019-03-05 15:57       ` Arne Babenhauserheide
2019-03-05 20:08         ` Leo Famulari [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190305200837.GA14036@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

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.