From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 25974] New: Mesa won't compile. Undeclared constants at nv20_context.c.
Date: Sat, 9 Jan 2010 16:35:22 -0800 (PST) [thread overview]
Message-ID: <bug-25974-8800@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=25974
Summary: Mesa won't compile. Undeclared constants at
nv20_context.c.
Product: xorg
Version: unspecified
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau@lists.freedesktop.org
ReportedBy: andrefv@gmail.com
QAContact: xorg-team@lists.x.org
I'm getting these errors when making Mesa:
nv20_context.c: In function ‘nv20_init_hwctx’:
nv20_context.c:326: error: ‘NV20TCL_FOG_MODE_EXP_SIGNED’ undeclared (first
use in this function)
nv20_context.c:326: error: (Each undeclared identifier is reported only once
nv20_context.c:326: error: for each function it appears in.)
nv20_context.c:327: error: ‘NV20TCL_FOG_COORD_FOG’ undeclared (first use in
this function)
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2010-01-10 0:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-10 0:35 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-25974-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2010-01-10 0:42 ` [Bug 25974] Mesa won't compile. Undeclared constants at nv20_context.c bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-01-10 0:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
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-25974-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.