From: Danny Milosavljevic <dannym@scratchpost.org>
To: 34439@debbugs.gnu.org
Subject: bug#34439: vlc build fails on guix master
Date: Mon, 11 Feb 2019 18:38:45 +0100 [thread overview]
Message-ID: <20190211183845.363091fc@scratchpost.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1653 bytes --]
codec/vpx.c:119:23: error: ‘VPX_IMG_FMT_444A’ undeclared here (not in a function)
{ VLC_CODEC_YUVA, VPX_IMG_FMT_444A, 8, 0 },
^
codec/vpx.c:120:23: error: ‘VPX_IMG_FMT_YUY2’ undeclared here (not in a function)
{ VLC_CODEC_YUYV, VPX_IMG_FMT_YUY2, 8, 0 },
^
codec/vpx.c:121:23: error: ‘VPX_IMG_FMT_UYVY’ undeclared here (not in a function)
{ VLC_CODEC_UYVY, VPX_IMG_FMT_UYVY, 8, 0 },
^
codec/vpx.c:122:23: error: ‘VPX_IMG_FMT_YVYU’ undeclared here (not in a function)
{ VLC_CODEC_YVYU, VPX_IMG_FMT_YVYU, 8, 0 },
codec/vpx.c:124:24: error: ‘VPX_IMG_FMT_RGB555’ undeclared here (not in a function)
{ VLC_CODEC_RGB15, VPX_IMG_FMT_RGB555, 8, 0 },
^
codec/vpx.c:125:24: error: ‘VPX_IMG_FMT_RGB565’ undeclared here (not in a function)
{ VLC_CODEC_RGB16, VPX_IMG_FMT_RGB565, 8, 0 },
^
codec/vpx.c:126:24: error: ‘VPX_IMG_FMT_RGB24’ undeclared here (not in a function)
{ VLC_CODEC_RGB24, VPX_IMG_FMT_RGB24, 8, 0 },
codec/vpx.c:127:24: error: ‘VPX_IMG_FMT_RGB32’ undeclared here (not in a function)
{ VLC_CODEC_RGB32, VPX_IMG_FMT_RGB32, 8, 0 },
^
codec/vpx.c:129:23: error: ‘VPX_IMG_FMT_ARGB’ undeclared here (not in a function)
{ VLC_CODEC_ARGB, VPX_IMG_FMT_ARGB, 8, 0 },
^
codec/vpx.c:130:23: error: ‘VPX_IMG_FMT_ARGB_LE’ undeclared here (not in a function)
{ VLC_CODEC_BGRA, VPX_IMG_FMT_ARGB_LE, 8, 0 },
make[4]: *** [Makefile:23666: codec/libvpx_plugin_la-vpx.lo] Error 1
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-02-11 17:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 17:38 Danny Milosavljevic [this message]
2019-02-11 17:59 ` bug#34439: vlc build fails on guix master Danny Milosavljevic
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=20190211183845.363091fc@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=34439@debbugs.gnu.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 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.