From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 63864] New: Compile failure; OPCODE_PRINT not found.
Date: Wed, 24 Apr 2013 07:07:00 +0000 [thread overview]
Message-ID: <bug-63864-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1379 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=63864
Priority: medium
Bug ID: 63864
Assignee: dri-devel@lists.freedesktop.org
Summary: Compile failure; OPCODE_PRINT not found.
Severity: major
Classification: Unclassified
OS: Linux (All)
Reporter: knut.tidemann@gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/DRI/r200
Product: Mesa
When building mesa from git master this morning
(9a32203e1618486e87c7baf494134e05f0e38cf3), the build failed with:
r200_vertprog.c:64:39: error: 'OPCODE_PRINT' undeclared here (not in a
function)
#define OPN(operator, ip) {#operator, OPCODE_##operator, ip}
^
r200_vertprog.c:98:4: note: in expansion of macro 'OPN'
OPN(PRINT, 0),
^
make[5]: *** [r200_vertprog.lo] Error 1
This is probably due to that commit;
commit 9a32203e1618486e87c7baf494134e05f0e38cf3
Author: Marek Olšák <maraeo@gmail.com>
Date: Sun Apr 14 19:59:06 2013 +0200
mesa: remove unused opcodes AND, DP2A, NOT, NRM3, NRM4, OR, PRINT, XOR
Reviewed-by: Brian Paul <brianp@vmware.com>
Reviewed-by: Eric Anholt <eric@anholt.net>
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2908 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2013-04-24 7:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 7:07 bugzilla-daemon [this message]
2013-04-24 12:29 ` [Bug 63864] Compile failure; OPCODE_PRINT not found bugzilla-daemon
2013-04-24 13:10 ` bugzilla-daemon
2013-04-24 16:14 ` bugzilla-daemon
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=bug-63864-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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.
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.