Package: libclang1-3.4 Version: 1:3.4.2-8 Severity: important Control: affects -1 codelite-plugins
Hi, The clang co-installable update is causing crashes is codelite when multiple versions of libclang1 are installed. Normally codelite (with codelite-plugins) will load libclang.so.1 and liblldb.so.1 from LLVM 3.4 and everything works: codelite libclang.so.1 (symlink to libclang-3.4.so.1) libLLVM-3.4.so.1 LLDBDebugger.so liblldb.so.1 (libLLVM-3.4.so.1 already loaded) But if you install libclang1-3.6 at the same time, codelite will load that library because libclang1.so.1 now points to it: codelite libclang.so.1 (symlink to libclang-3.6.so.1) libLLVM-3.6.so.1 LLDBDebugger.so liblldb.so.1 libLLVM-3.4.so.1 (symbol collision) Then codelite segfaults in the constructors for libLLVM-3.4 due to (I assume) a symbol collision with libLLVM-3.6.so.1 As a temporary workaround, I can add a Breaks: libclang1-3.5, libclang1-3.6 to codelite but that doesn't seem very clean. In my opinion, allowing co-installation of libraries whose sonames are the same is a recipe for disaster. Thanks, James -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 mipsel Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libclang1-3.4 depends on: ii libc6 2.19-10 ii libffi6 3.1-2 ii libgcc-4.9-dev 4.9.1-9 ii libgcc1 1:4.9.1-9 ii libllvm3.4 1:3.4.2-8 ii libobjc-4.9-dev 4.9.1-9 ii libstdc++-4.9-dev 4.9.1-9 ii libstdc++6 4.9.1-9 ii libtinfo5 5.9+20140712-2 ii multiarch-support 2.19-10 libclang1-3.4 recommends no packages. libclang1-3.4 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
