<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - Shader Disk Cache 32/64 bit detection has a flaw. Missed existence of x32 ABI"
href="https://bugs.freedesktop.org/show_bug.cgi?id=100073#c30">Comment # 30</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - Shader Disk Cache 32/64 bit detection has a flaw. Missed existence of x32 ABI"
href="https://bugs.freedesktop.org/show_bug.cgi?id=100073">bug 100073</a>
from <span class="vcard"><a class="email" href="mailto:tdroste@gmx.de" title="Tobias Droste <tdroste@gmx.de>"> <span class="fn">Tobias Droste</span></a>
</span></b>
<pre>(In reply to oiaohm from <a href="show_bug.cgi?id=100073#c29">comment #29</a>)
<span class="quote">> I would still prefer each arch has there own cache directory in case one of
> the archs has a suspect gcc or other complier and has in fact built the
> library wrong. So that only that archs application go splat. Currently
> you have an environmental to turn disc cache off extra option would be an
> environmental to allow forcing using another cache location so that
> Multiarch can do diagnostics.</span >
MESA_GLSL_CACHE_DIR=<something>
<span class="quote">>
> You can look at each arch as it own build environment with its own bugs.
>
> Turning the cache off is not exactly a solution.</span ></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>