<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [CMake] Do not use LLVM static libraries for FTL JIT"
href="https://bugs.webkit.org/show_bug.cgi?id=151559#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [CMake] Do not use LLVM static libraries for FTL JIT"
href="https://bugs.webkit.org/show_bug.cgi?id=151559">bug 151559</a>
from <span class="vcard"><a class="email" href="mailto:cgarcia@igalia.com" title="Carlos Garcia Campos <cgarcia@igalia.com>"> <span class="fn">Carlos Garcia Campos</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=151559#c5">comment #5</a>)
<span class="quote">> OK, my vote is to either fix this or disable FTL again before 2.12. Using
> static libs is not considered acceptable on Linux, and it's causing build
> problems for openSUSE and Gentoo, which don't have LLVM static libs at all;
> no doubt it will be problematic for other distros too.
>
> openSUSE came up with a rather innovative solution [1] to use
> -DLLVM_CONFIG_EXE at cmake time to pointing cmake to a script that wraps
> llvm-config like so:
>
> #!/bin/bash
>
> /usr/bin/llvm-config $1 |sed "s,\\.a,\\.so,g"
>
> Yuck, but their package is reportedly working without issues, so I doubt the
> static libs were ever really needed. It would be better to use a similar
> wrapper around llvm-config to handle this automagically than to continue
> using static libs.</span >
It's not that easy, this hack works for SUSE because they are building llvm with CMake, so they have a .so for each static library. However, if llvm is built using autotools (like debian and fedora do) what we have is a single .so file. So we need to detect this as well at configure.</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>