(Mon May 10 08:30:28 2010)
If we build Mesa with "--enable-gles2", glean/pixelFormats fails.
If we build Mesa using the below options without enabling gles2, glean/pixelFormats passes.
"./autogen.sh --prefix=/opt/X11R7 --with-driver=dri --with-dri-drivers="i915 i965 swrast" --with-dri-driverdir=/opt/X11R7/lib/dri --disable-glut --without-demos --disable-gallium"
May 19 2010 is the first day that we built Mesa with "--enable-gles2" in nightly testing. Before that time, we built Mesa without enabling gles2 and glean/pixelFormats always passed. So we are not sure which commit introduced this issue.
But since commit 61aa9c86c20b1bc9957aa9fe9976703a93cc4d3c(May 13 10:13:52 2010), with/without "--enable-gles2", glean/pixelFormats fails. Please refer to bug 29925.
Created attachment 38351 [details]
Did you do a full rebuild of Mesa with a clean tree (git clean -f -d -x is the most reliable way to do so, note that this will remove everything in your tree that isn't in git) when switching configure options? You have to do that when changing configure options or you'll get strange behavior.
I did "git clean -f -d -x" before rebuild mesa
Author: Eric Anholt <firstname.lastname@example.org>
Date: Mon Jul 11 11:32:04 2011 -0700
i915: Fix map/unmap mismatches from leaving INTEL_FALLBACK during TNL.
The first rendering after context create didn't know of the color
buffer yet, triggering a sw fallback. The intel_prepare_render() from
intelSpanRenderStart then found the buffer and turned off fallbacks,
but intelSpanRenderFinish was never called and things were left
mapped. By checking buffers before making the call on whether to do
the fallback pipeline or not, we avoid the fallback change inside of
the rendering pipeline.
Reviewed-by: Ian Romanick <email@example.com>
Verified with Mesa master 0aed27ee37860ba332df776425d89d97ca1168b2.
on May 31, 2016 at 19:51:50.
(provided by the Example extension).