Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 4/4] package/x11r7/xlib_libXvMC: remove xlib_libXv dependency
Date: Sat, 26 Oct 2019 22:55:20 +0200	[thread overview]
Message-ID: <20191026225520.31a9dafa@windsurf.home> (raw)
In-Reply-To: <20191005094818.1956334-4-romain.naour@gmail.com>

On Sat,  5 Oct 2019 11:48:18 +0200
Romain Naour <romain.naour@gmail.com> wrote:

> Since libXvMC 1.0.12, xv was removed from xvmc.pc [1].
> 
> [1] https://lists.x.org/archives/xorg-announce/2019-September/003023.html

Seems like it disagrees:

  http://autobuild.buildroot.net/results/305/3051f4fbc1ab725de542a550e4f9eeb3cae385b8/build-end.log

checking for XVMC... no
configure: error: Package requirements (x11 >= 1.6 xext xv xextproto videoproto) were not met:

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2019-10-26 20:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-05  9:48 [Buildroot] [PATCH v2 1/4] package/llvm: add llvm RTTI option Romain Naour
2019-10-05  9:48 ` [Buildroot] [PATCH v2 2/4] package/mesa3d: enable llvm RTTI when needed Romain Naour
2019-10-05 14:18   ` Bernd Kuhls
2019-10-05  9:48 ` [Buildroot] [PATCH v2 3/4] package/mesa3d: add xlib_libXv dependency to mesa3d xvmc Romain Naour
2019-10-05 14:18   ` Bernd Kuhls
2019-10-12 14:04   ` Bernd Kuhls
2019-10-05  9:48 ` [Buildroot] [PATCH v2 4/4] package/x11r7/xlib_libXvMC: remove xlib_libXv dependency Romain Naour
2019-10-05 14:19   ` Bernd Kuhls
2019-10-26 20:55   ` Thomas Petazzoni [this message]
2019-10-26 21:10     ` Romain Naour
2019-10-05 14:18 ` [Buildroot] [PATCH v2 1/4] package/llvm: add llvm RTTI option Bernd Kuhls
2019-10-25 19:41 ` Thomas Petazzoni

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=20191026225520.31a9dafa@windsurf.home \
    --to=thomas.petazzoni@bootlin.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