<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 3 July 2015 at 09:30, <span dir="ltr"><<a href="mailto:Steffen.Pankratz@elektrobit.com" target="_blank">Steffen.Pankratz@elektrobit.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":bo" class="a3s" style="overflow:hidden">+# Valgrind support is enabled by default currently<br>
+# already fixed upstream: <a href="http://cgit.freedesktop.org/mesa/drm/commit/?id=676c806d0221a7ea375676b2eab514c426fcacd3" rel="noreferrer" target="_blank">http://cgit.freedesktop.org/mesa/drm/commit/?id=676c806d0221a7ea375676b2eab514c426fcacd3</a><br>
+EXTRA_OECONF += "--disable-valgrind"</div></blockquote></div><br>No need for this comment. We'd need the --disable-valgrind when that commit is in a release as then libdrm will enable/disable valgrind support depending on the sysroot, and non-determinism is bad.</div><div class="gmail_extra"><br></div><div class="gmail_extra">(To avoid a cycle I'll pull this into staging but delete the comment)</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>