Le 23/08/2019 à 09:39, Mariana Meireles a écrit :
On Tue, 15 Jan 2013 22:55:03 +0100 Matthias Klose <d...@debian.org> wrote:
Package: clang
Severity: important

at least for 3.2:

$ ls /usr/lib/libclang*
/usr/lib/libclang.a             /usr/lib/libclangFrontendTool.a
/usr/lib/libclang.so            /usr/lib/libclangLex.a
/usr/lib/libclang.so.1          /usr/lib/libclangParse.a
/usr/lib/libclangARCMigrate.a   /usr/lib/libclangRewriteCore.a
/usr/lib/libclangAST.a          /usr/lib/libclangRewriteFrontend.a
/usr/lib/libclangASTMatchers.a  /usr/lib/libclangSema.a
/usr/lib/libclangAnalysis.a     /usr/lib/libclangSerialization.a
/usr/lib/libclangBasic.a        /usr/lib/libclangStaticAnalyzerCheckers.a
/usr/lib/libclangCodeGen.a      /usr/lib/libclangStaticAnalyzerCore.a
/usr/lib/libclangDriver.a       /usr/lib/libclangStaticAnalyzerFrontend.a
/usr/lib/libclangEdit.a         /usr/lib/libclangTooling.a
/usr/lib/libclangFrontend.a

and it doesn't look like libclang.so is the catch-all shared library, like
libLLVM-3.2.so is for llvm. Is this intended?

so creduce (currently in NEW) has to use the static libs.



Hi, I’m interested in working in this bug. Even though I have some previous 
experience contributing to open source I’ve never contributed to Debian before. 
Is someone available to mentor this bug and help me out if I get stuck in 
something?

Also, can I work in this?

Sure but you should check that it is even possible upstream :)

don't hesitate if you need anything

S

Reply via email to