https://bugs.llvm.org/show_bug.cgi?id=28127

Evangelos Foutras <evange...@foutrelis.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|FIXED                       |---
                 CC|                            |evange...@foutrelis.com
             Status|RESOLVED                    |REOPENED

--- Comment #7 from Evangelos Foutras <evange...@foutrelis.com> ---
Either this issue has regressed in LLDB 6.0.0 or the LLVM package I pushed to
Arch Linux is buggy.

I'm doing an out-of-tree build of LLDB 6.0.0 with LLVM_LINK_LLVM_DYLIB=ON. The
resulting lldb-{server,test} binaries link to both libLLVMSupport.a and
libLLVM-6.0.so and result in the following runtime errors:

=========================
$ lldb-server 
: CommandLine Error: Option 'disable-symbolication' registered more than once!
LLVM ERROR: inconsistency in registered CommandLine options

$ lldb-test 
: CommandLine Error: Option 'help-list' registered more than once!
LLVM ERROR: inconsistency in registered CommandLine options
=========================

I'm unable to reproduce the issue on Fedora Rawhide, but I believe that has to
do with the fact that Fedora's libLLVM-6.0.so links statically to libstdc++
(not sure why this has any effect on this problem though). If I build my LLVM
package with static libstdc++ like Fedora does
(-DCMAKE_SHARED_LINKER_FLAGS="-Wl,-Bsymbolic -static-libstdc++") then
lldb-{server,test} run fine.

I also tried to repro on Debian without any success. (Perhaps it matters that
they do an in-tree build?)

For now I've resorted to removing all references to /usr/lib/libLLVMSupport.a
from the generated build.ninja file. This seems to allow the above tools to
run.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

Reply via email to