Bug 139126 – Failed to load LLVM library at libllvmForJSC.so

• Status: RESOLVED
• Resolution: DUPLICATE
• Component: JavaScriptCore

[Seo Sanghyeon]

r176590.

To reproduce:
Tools/Scripts/build-jsc --gtk --ftl-jit
WebKitBuild/Release/bin/jsc --verboseFTLCompilation=true some.js

This is a regression. If I set USE_LD_GOLD to OFF it works fine.
https://bugs.webkit.org/show_bug.cgi?id=137953

My understanding is that ld and gold have different defaults so that ld sets RPATH, but gold sets RUNPATH. RPATH is applied transitively but RUNPATH is not. Before, jsc had RPATH, jsc links to libjavascriptcoregtk-4.0.so, which dlopen libllvmForJSC.so using RPATH from jsc, but this doesn't happen with RUNPATH. To use RUNPATH, libjavascriptcoregtk-4.0.so should have RUNPATH, not jsc. Here is a good explanation:
http://blog.qt.digia.com/blog/2011/10/28/rpath-and-runpath/

[Csaba Osztrogonác]

I can't reproduce this bug on Ubuntu 14.04. 
Maybe your ld and ld.gold have different default settings.

Could you check if passing --enable-new-dtags or --disable-new-dtags
to your linker fixes this issue or not?

[Seo Sanghyeon]

How can I pass --disable-new-dtags to my linker? I am not that familiar with the build system to know.

[Seo Sanghyeon]

By the way, I am on Ubuntu 14.04 too.

I needed to do clean rebuild to get USE_LD_GOLD change to take effect. Maybe you are still using ld?

[Csaba Osztrogonác]

Created attachment 242406 [details]
test

(In reply to comment #2)
> How can I pass --disable-new-dtags to my linker? I am not that familiar with
> the build system to know.

Try the attached patch.

[Csaba Osztrogonác]

(In reply to comment #3)
> Maybe you are still using ld?
No, I do use ld.gold.

[Seo Sanghyeon]

Passing --disable-new-dtags using the attached patch does fix the issue. Thanks.

[Seo Sanghyeon]

I found that although my system is Ubuntu 14.04, my binutils package is from Ubuntu 14.10. I installed GCC 4.9 from Ubuntu 14.10 repository, which also pulled binutils, but I forgot about it.

Sorry for confusion.

[Csaba Osztrogonác]

*** This bug has been marked as a duplicate of bug 140049 ***