<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Unigine Valley & Heaven "error: syntax error, unexpected EXTENSION, expecting $end" IVB HD4000" href="https://bugs.freedesktop.org/show_bug.cgi?id=75664#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Unigine Valley & Heaven "error: syntax error, unexpected EXTENSION, expecting $end" IVB HD4000" href="https://bugs.freedesktop.org/show_bug.cgi?id=75664">bug 75664</a> from <a class="email" href="mailto:eero.t.tamminen@intel.com" title="Eero Tamminen <eero.t.tamminen@intel.com>"> Eero Tamminen</a> <pre>Yes, Gallium drivers have quite different shader compiler code from classic Mesa side. Blend function issue will be fixed in next version of Valley, it's a bug in the demo. If you don't want to work around the demo bugs with environment variables, you have also an option to patch Mesa: <a href="http://cgit.freedesktop.org/~kwg/mesa/log/?h=unigine">http://cgit.freedesktop.org/~kwg/mesa/log/?h=unigine</a> (There are also patches floating around for allowing extension declarations elsewhere in shader source, but they seem to get fairly quickly out of date, and AFAIK they won't get merged into Mesa until Khronos GL specs have been changed accordingly. See e.g. patch mentioned in <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTOURBUG - Second Life shaders fail to compile (extension declared in middle of shader)" href="show_bug.cgi?id=71591">bug 71591</a>.)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>