http://bugzilla.suse.com/show_bug.cgi?id=1065593 http://bugzilla.suse.com/show_bug.cgi?id=1065593#c1 Michal Srb changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #1 from Michal Srb --- The LLVM build mode was changed from the (not recommended and buggy) multiple-library mode into a single-library mode. See https://bugzilla.opensuse.org/show_bug.cgi?id=1049703 for more details. There are also links to page where LLVM upstream developers tell that the old mode is not recommended and a list of bugs that it caused us. In the current build mode all LLVM components end up in a single shared library called libLLVM.so. All clang components are only build as static libraries. (Sadly that is the only build mode supported by upstream for clang.) As you already discovered, you need to add the clang4-devel-static to get the libclang* static libraries. Bcc is currently using the `llvm_map_components_to_libnames` cmake function to get the list of LLVM libraries it should link to. I would expect that function to return only "LLVM", but instead it returns names of the individual libraries that do not exist. I have run into this problem before and I think that either the `llvm_map_components_to_libnames` function is broken, or it is not meant to be used by external projects. I have asked on llvm-dev mailing list (on Oct 23) and so far got not answer. It looks like time to create upstream bug. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1065593 http://bugzilla.suse.com/show_bug.cgi?id=1065593#c3 --- Comment #3 from Gary Ching-Pang Lin --- (In reply to Michal Srb from comment #1)

The LLVM build mode was changed from the (not recommended and buggy) multiple-library mode into a single-library mode.

See https://bugzilla.opensuse.org/show_bug.cgi?id=1049703 for more details. There are also links to page where LLVM upstream developers tell that the old mode is not recommended and a list of bugs that it caused us.

In the current build mode all LLVM components end up in a single shared library called libLLVM.so. All clang components are only build as static libraries. (Sadly that is the only build mode supported by upstream for clang.)

As you already discovered, you need to add the clang4-devel-static to get the libclang* static libraries.

Bcc is currently using the `llvm_map_components_to_libnames` cmake function to get the list of LLVM libraries it should link to. I would expect that function to return only "LLVM", but instead it returns names of the individual libraries that do not exist. I have run into this problem before and I think that either the `llvm_map_components_to_libnames` function is broken, or it is not meant to be used by external projects. I have asked on llvm-dev mailing list (on Oct 23) and so far got not answer. It looks like time to create upstream bug.

Is it possible to work around the issue? so that I can at least build bcc while waiting the upstream fix. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1065593 http://bugzilla.suse.com/show_bug.cgi?id=1065593#c5 --- Comment #5 from Gary Ching-Pang Lin --- Although bcc was built, it didn't work anymore :-( Besides, it consumed a lot of RAM while linking the clang libraries. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1065593 http://bugzilla.suse.com/show_bug.cgi?id=1065593#c7 --- Comment #7 from Gary Ching-Pang Lin --- Well, it turned out to be a bug in bcc. Its implementation actually only works for MCJIT. In its cmake settings, bcc actually looks for MCJIT instead of OrcJIT. For the systems with separate LLVM libraries, libLLVMOrcJIT.so is not linked, so bcc (actually llvm::ExecutionEngine) falls back to MCJIT gracefully. Since we built the unified share library, OrcJIT is always there, and the bug hit us. I already sent a pull request(*) to bcc upstream and will submit the updated bcc to Factory. (*) https://github.com/iovisor/bcc/pull/1438 -- You are receiving this mail because: You are on the CC list for the bug.