| Summary: | sys-devel/llvm-3.9.0-r1[lldb]: force linking of libLLVMSupport.so | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Alessandro Di Federico <ale> |
| Component: | Current packages | Assignee: | LLVM support project <llvm> |
| Status: | RESOLVED TEST-REQUEST | ||
| Severity: | normal | CC: | ale, ave |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
Force linking libLLVMSupport.so for the lldb-mi target
Force linking libLLVMSupport.so for the lldb-mi target |
||
FYI, the current live git (dev-util/lldb-9999) builds fine for me, so you may want to see what kind of fix upstream did. Also, is 3.9.0 ncurses[tinfo]-clean? In the release_39 branch there are quite a few commits related to CMake and lldb-mi, probably not included in 3.9.0, but it's not immediately evident to me which one is fixing the problem or at least it's not a one-liner but might involve importing multiple patches. https://github.com/llvm-mirror/lldb/commits/release_39/tools/lldb-mi/CMakeLists.txt LLVM 3.9.1 is expected to be release on Dec 5th. I'd suggest to either wait for 3.9.1 or simply apply the proposed patch. I've ncurses without the tinfo USE flag and it build and runs fine, "gui" command included. Created attachment 454440 [details, diff] Force linking libLLVMSupport.so for the lldb-mi target New patch, extracted from the following commit (excluding the first hunk): https://github.com/llvm-mirror/lldb/commit/240c36dc42eff1efe71023cd1b6b5d47adbbfd48 It seems to work too. Is 3.9.1 fine now or does it need more patches? Since lldb in 3.9 is not a priority, closing until someone confirms what needs to be done for 3.9.1. |
Created attachment 454380 [details, diff] Force linking libLLVMSupport.so for the lldb-mi target Hi, currently the base profile masks the lldb USE flag for the LLVM package since it "needs a lot of minor fixes". I've tried to unmask it and I only had to force linking libLLMVSupport.so to make it build correctly (see attached patch). The patch might not be the ideal solution and we should probably report the issue upstream, but it works. Can we unmask the USE flag in the base profile?