dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 57875] Second Life viewer bad rendering with git-ec83535
Date: Thu, 27 Dec 2012 10:25:05 +0000	[thread overview]
Message-ID: <bug-57875-502-NLe6SiuKTA@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-57875-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1087 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=57875

--- Comment #18 from Piero Finizio <andabata12@yahoo.it> ---
If i try to revert the commit e866bd1adea2c3b4971ad68e69c644752f2ab7b6  (above
mentioned workaround) with git
"HEAD at 7c35521 mesa: add missing texel fetch code for sRGB DXT formats"
the compilation ends with:
 ...
CC     r300_screen.o
r300_screen.c: In function ‘r300_get_param’:
r300_screen.c:130:14: error: ‘PIPE_CAP_TIMER_QUERY’ undeclared (first use in
this function)
r300_screen.c:130:14: note: each undeclared identifier is reported only once
for each function it appears in
r300_screen.c:88:5: warning: enumeration value ‘PIPE_CAP_QUERY_TIME_ELAPSED’
not handled in switch [-Wswitch]
r300_screen.c:88:5: warning: enumeration value
‘PIPE_CAP_TEXTURE_BUFFER_OBJECTS’ not handled in switch [-Wswitch]
gmake[4]: *** [r300_screen.o] Error 1
gmake[4]: Leaving directory `/root/mesa/src/gallium/drivers/r300'
gmake[3]: *** [all-recursive] Error 1

 ...

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1892 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

  parent reply	other threads:[~2012-12-27 10:25 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-04 13:04 [Bug 57875] New: Second Life viewer bad rendering with git-ec83535 bugzilla-daemon
2012-12-04 13:08 ` [Bug 57875] " bugzilla-daemon
2012-12-04 13:11 ` bugzilla-daemon
2012-12-04 13:53 ` bugzilla-daemon
2012-12-06 15:55 ` bugzilla-daemon
2012-12-06 16:54 ` bugzilla-daemon
2012-12-06 17:04 ` bugzilla-daemon
2012-12-06 17:09 ` bugzilla-daemon
2012-12-06 18:20 ` bugzilla-daemon
2012-12-06 18:34 ` bugzilla-daemon
2012-12-06 18:52 ` bugzilla-daemon
2012-12-06 18:55 ` bugzilla-daemon
2012-12-06 20:49 ` bugzilla-daemon
2012-12-06 22:03 ` bugzilla-daemon
2012-12-06 23:43 ` bugzilla-daemon
2012-12-09 21:59 ` bugzilla-daemon
2012-12-10 15:20 ` bugzilla-daemon
2012-12-12 20:29 ` bugzilla-daemon
2012-12-27 10:25 ` bugzilla-daemon [this message]
2013-01-07 15:43 ` bugzilla-daemon
2013-01-07 16:12 ` bugzilla-daemon
2013-01-21 19:07 ` bugzilla-daemon
2013-01-21 22:16 ` bugzilla-daemon
2013-01-22 10:25 ` bugzilla-daemon
2013-01-22 10:39 ` bugzilla-daemon
2013-01-25 11:27 ` bugzilla-daemon
2013-03-13 13:30 ` bugzilla-daemon
2013-03-13 21:20 ` bugzilla-daemon
2013-06-30 16:07 ` bugzilla-daemon
2013-07-01 15:15 ` bugzilla-daemon
2013-07-16 12:43 ` bugzilla-daemon
2013-07-16 13:40 ` bugzilla-daemon
2013-07-16 17:09 ` bugzilla-daemon
2013-07-30 21:12 ` 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-57875-502-NLe6SiuKTA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).