<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - OSMesa 17.1.3 simd16intrin build FAIL on Win/MinGW - 'expected initializer before _simd16_setzero_ps ...'"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101614#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - OSMesa 17.1.3 simd16intrin build FAIL on Win/MinGW - 'expected initializer before _simd16_setzero_ps ...'"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101614">bug 101614</a>
from <span class="vcard"><a class="email" href="mailto:trevor.sandy@gmail.com" title="Trevor SANDY <trevor.sandy@gmail.com>"> <span class="fn">Trevor SANDY</span></a>
</span></b>
<pre>George,
I haven't personally experienced this error but I did come across it in several
places. In fact, <a class="bz_bug_link
bz_status_NEW "
title="NEW - error: The command line is too long when building MESA on Windows with MinGW-W64"
href="show_bug.cgi?id=94072">Bug 94072</a> - error: The command line is too long when building
MESA on Windows with MinGW-W64 I think covers this behaviour.
I likely haven't seen it because I'm only building osmesa - not the full build.
It looks like those experiencing this behaviour are also building libgl-gdi.
Nevertheless, the problem appears to be rooted in SCons which is probably where
the behaviour I'm experiencing is rooted also. I say this because osmesa w/
llvm (swr on Ubuntu Linux 16.04 and llvmpipe on OSX Sierra both run to
completion without issue.
Try your build without libgl-gdi - just osmesa. If you have a MSYS/MinGW env
with the required pre-reqs installed, my script
(<a href="https://github.com/trevorsandy/osmesa-install/blob/master/osmesa-install.sh">https://github.com/trevorsandy/osmesa-install/blob/master/osmesa-install.sh</a>)
automates the build quite nicely. You tweak and run quite efficiently to better
narrow down the cause of failure.
Cheers,</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>