https://bugs.freedesktop.org/show_bug.cgi?id=93103
--- Comment #5 from Tobias Schlüter <t...@schlueters.de> --- Thank you for the quick response! I'll take the comments to mean that this shouldn't happen with very recent versions of libmesa and llvm. It does happen with fairly recent versions though. We verified on a colleague's system that the same error appears on Ubuntu 15.05 with libmesa 10.5.9 and libllvm 3.6, (there are some differences in the backtrace because we used a slightly simpler way of triggering the bug as documented in the ROOT bug report I was linking to). I would be surprised if Ubuntu uses scons for the build, but I don't know. Backtrace: =========================================================== #5 0x00007f5c3a87de31 in llvm::cl::AddLiteralOption(llvm::cl::Option&, char const*) () from /home/ritter/belle2/externals/development/Linux_x86_64/opt/root/lib/libCling.so #6 0x00007f5c2d944e3a in llvm::PassRegistry::enumerateWith(llvm::PassRegistrationListener*) () from /usr/lib/x86_64-linux-gnu/libLLVM-3.6.so.1 #7 0x00007f5c2d6e86a8 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-3.6.so.1 #8 0x00007f5c3d4585ba in ?? () from /lib64/ld-linux-x86-64.so.2 #9 0x00007f5c3d4586cb in ?? () from /lib64/ld-linux-x86-64.so.2 #10 0x00007f5c3d45d587 in ?? () from /lib64/ld-linux-x86-64.so.2 #11 0x00007f5c3d458464 in ?? () from /lib64/ld-linux-x86-64.so.2 #12 0x00007f5c3d45c9a3 in ?? () from /lib64/ld-linux-x86-64.so.2 #13 0x00007f5c3bea5fc9 in ?? () from /lib/x86_64-linux-gnu/libdl.so.2 #14 0x00007f5c3d458464 in ?? () from /lib64/ld-linux-x86-64.so.2 #15 0x00007f5c3bea662d in ?? () from /lib/x86_64-linux-gnu/libdl.so.2 #16 0x00007f5c3bea6061 in dlopen () from /lib/x86_64-linux-gnu/libdl.so.2 #17 0x00007f5c3938c47f in cling::DynamicLibraryManager::loadLibrary(std::string const&, bool) () from /home/ritter/belle2/externals/development/Linux_x86_64/opt/root/lib/libCling.so ... ============================================================ I don't agree with Emil that it is a problem on the ROOT side (even though the installed a workaround): one should be able to use libmesa without being afraid that symbols leak through that are not part of libmesa's public interface. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug.
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev