<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - egl-static/Makefile: linking fails with llvm >= 3.4"
href="https://bugs.freedesktop.org/show_bug.cgi?id=70410#c14">Comment # 14</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - egl-static/Makefile: linking fails with llvm >= 3.4"
href="https://bugs.freedesktop.org/show_bug.cgi?id=70410">bug 70410</a>
from <span class="vcard"><a class="email" href="mailto:awatry@gmail.com" title="Aaron Watry <awatry@gmail.com>"> <span class="fn">Aaron Watry</span></a>
</span></b>
<pre>Created <span class=""><a href="attachment.cgi?id=91751" name="attach_91751" title="llvm-config patch to place system-libs on a single line">attachment 91751</a> <a href="attachment.cgi?id=91751&action=edit" title="llvm-config patch to place system-libs on a single line">[details]</a></span> <a href='page.cgi?id=splinter.html&bug=70410&attachment=91751'>[review]</a>
llvm-config patch to place system-libs on a single line
Patch modifies llvm-config to print --system-libs on a single line.
If the user requests 'llvm-config --libs --system-libs', then it still puts it
on a single line, but orders the system libraries to come at the end. If you
request --libs, then you just get libs. If you request --system-libs, then you
just get system libraries that llvm links against.
This way we just have to modify the mesa build to call 'llvm-config --libs
--system-libs' anywhere needed, instead of doing some sed fiddling to the
output and hoping we get it right.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>