search for: libclangbasic

...lib/libLLVMX86Disassembler.a lib/libLLVMX86Info.a lib/libLLVMX86Utils.a lib/libLLVMXCoreCodeGen.a lib/libLLVMXCoreAsmPrinter.a lib/libLLVMXCoreDesc.a lib/libLLVMXCoreInfo.a lib/libLLVMXCoreDisassembler.a lib/libLLVMXCoreInfo.a lib/libLLVMOption.a lib/libLLVMSupport.a -lpthread lib/libclangAST.a lib/libclangBasic.a lib/libclangDriver.a lib/libclangFrontend.a lib/libclangRewriteFrontend.a lib/libclangStaticAnalyzerFrontend.a lib/libclangTooling.a lib/libLLVMAArch64Desc.a lib/libLLVMAArch64AsmPrinter.a lib/libLLVMAArch64Info.a lib/libLLVMAArch64Utils.a lib/libLLVMAMDGPUDesc.a lib/libLLVMAMDGPUAsmPrinter.a lib...

...po.a lib/libLLVMAggressiveInstCombine.a lib/libLLVMInstCombine.a lib/libLLVMInstrumentation.a lib/libLLVMMC.a lib/libLLVMMCParser.a lib/libLLVMObjCARCOpts.a lib/libLLVMOption.a lib/libLLVMScalarOpts.a lib/libLLVMSupport.a lib/libLLVMTransformUtils.a lib/libLLVMVectorize.a -lpthread lib/libclangBasic.a lib/libclangCodeGen.a lib/libclangDriver.a lib/libclangFrontend.a lib/libclangFrontendTool.a lib/libclangSerialization.a lib/libLLVMAArch64Desc.a lib/libLLVMAArch64Info.a lib/libLLVMAArch64Utils.a lib/libLLVMMIRParser.a lib/libLLVMAMDGPUDesc.a lib/libLLVMAMDGPUInfo.a lib/libLLVMAMDGPU...

...lib/libclangToolingInclusions.a lib/libclangFrontend.a lib/libclangParse.a lib/libclangSerialization.a lib/libclangSema.a lib/libclangEdit.a lib/libclangAnalysis.a lib/libclangASTMatchers.a lib/libclangDriver.a lib/libclangToolingCore.a lib/libclangAST.a lib/libclangRewrite.a lib/libclangLex.a lib/libclangBasic.a lib/libLLVM-11git.so && : [5803/7319] /usr/lib/llvm/10/bin/clang++ -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -Itools/clang/tools/driver -I/home/laguest/src/mine-new/llvm/llvm-project/clang/tools/driver -I/home/laguest/src/mine-new/llvm/llvm-proje...

[Sorry about the crosspost. Since this is a clang build question but the build is invoked from the top-level LLVM directory I'm not sure where the question should go.] I've got a clang build against libstdc++ on Linux but I would really like one built against libc++/libc++abi. In other words I'd like to rebuild clang/llvm with clang using libc++ and libc++abi on Linux. I looked at

....2-4.el8.x86_64 - nothing provides libLLVM-8.so(LLVM_8)(64bit) needed by qt-creator-4.9.2-4.el8.x86_64 - nothing provides libclang.so.8()(64bit) needed by qt-creator-4.9.2-4.el8.x86_64 - nothing provides libclang.so.8(LLVM_8)(64bit) needed by qt-creator-4.9.2-4.el8.x86_64 - nothing provides libclangBasic.so.8()(64bit) needed by qt-creator-4.9.2-4.el8.x86_64 - nothing provides libclangFormat.so.8()(64bit) needed by qt-creator-4.9.2-4.el8.x86_64 - nothing provides libclangLex.so.8()(64bit) needed by qt-creator-4.9.2-4.el8.x86_64 - nothing provides libclangRewrite.so.8()(64bit) needed by qt-crea...

...po.a lib/libLLVMAggressiveInstCombine.a lib/libLLVMInstCombine.a lib/libLLVMInstrumentation.a lib/libLLVMMC.a lib/libLLVMMCParser.a lib/libLLVMObjCARCOpts.a lib/libLLVMOption.a lib/libLLVMScalarOpts.a lib/libLLVMSupport.a lib/libLLVMTransformUtils.a lib/libLLVMVectorize.a -lpthread lib/libclangBasic.a lib/libclangCodeGen.a lib/libclangDriver.a lib/libclangFrontend.a lib/libclangFrontendTool.a lib/libclangSerialization.a lib/libLLVMAArch64Desc.a lib/libLLVMAArch64Info.a lib/libLLVMAArch64Utils.a lib/libLLVMMIRParser.a lib/libLLVMAMDGPUDesc.a lib/libLLVMAMDGPUInfo.a lib/libLLVMAMDGPU...

...c.o - >> o ../../../../bin/c-index-test -rdynamic ../../../../lib/ >> libCIndex.so ../../../../lib/libclangIndex.a ../../../../lib/ >> libclangFrontend.a ../../../../lib/libclangSema.a ../../../../lib/ >> libclangAST.a ../../../../lib/libclangLex.a ../../../../lib/ >> libclangBasic.a ../../../../lib/libLLVMBitReader.a ../../../../lib/ >> libLLVMMC.a ../../../../lib/libLLVMCore.a ../../../../lib/ >> libLLVMSupport.a ../../../../lib/libLLVMSystem.a -ldl -lpthread -Wl,- >> rpath,/home/dreamkxd/llvm/lib >> >> And so, it's won't linkage with C...

...l the given function the programmer needs to choose the right dependencies to link to or the program will not link. Clang Diagnostics <https://reviews.llvm.org/D41357> (work in progress): The diagnostics for each component are in their own component directories, but are then all included from libClangBasic, a library none of those components depends on. (so this isn't so much an inlining case as #include based circular dependency) Generally I'd like to get buy-in that stricter layering is desirable, and that these few cases are at least sub-optimal, if accepted for now. Happy to go into mo...

How big is your project? LTO eats RAM even faster than chrome. For example linking clang with LTO could take 16GB of ram. Have you tried using LTO on your project on that machine, or is it your first time? Piotr On Sat, Jul 23, 2016 at 2:42 AM, Sedat Dilek via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On Thu, Jul 21, 2016 at 12:01 PM, Sedat Dilek <sedat.dilek at

...pe.cpp.o > CMakeFiles/libclang.dir/IndexBody.cpp.o > CMakeFiles/libclang.dir/IndexDecl.cpp.o > CMakeFiles/libclang.dir/IndexTypeSourceInfo.cpp.o > CMakeFiles/libclang.dir/Indexing.cpp.o > CMakeFiles/libclang.dir/IndexingContext.cpp.o ../../../../lib/libclangAST.a > ../../../../lib/libclangBasic.a ../../../../lib/libclangFrontend.a > ../../../../lib/libclangIndex.a ../../../../lib/libclangLex.a > ../../../../lib/libclangSema.a ../../../../lib/libclangTooling.a > ../../../../lib/libclangARCMigrate.a -ldl ../../../../lib/libLLVMCore.a > ../../../../lib/libLLVMSupport.a ../../../....

...ll the given function the programmer needs to choose the right dependencies to link to or the program will not link. Clang Diagnostics<https://reviews.llvm.org/D41357> (work in progress): The diagnostics for each component are in their own component directories, but are then all included from libClangBasic, a library none of those components depends on. (so this isn't so much an inlining case as #include based circular dependency) Generally I'd like to get buy-in that stricter layering is desirable, and that these few cases are at least sub-optimal, if accepted for now. Happy to go into mo...

...e programmer needs to choose the right dependencies to link to or > the program will not link. > Clang Diagnostics <https://reviews.llvm.org/D41357> (work in > progress): The diagnostics for each component are in their own > component directories, but are then all included from libClangBasic, a > library none of those components depends on. (so this isn't so much an > inlining case as #include based circular dependency) > > > Generally I'd like to get buy-in that stricter layering is desirable, > and that these few cases are at least sub-optimal, if accepte...

...> programmer needs to choose the right dependencies to link to or the program > will not link. > Clang Diagnostics <https://reviews.llvm.org/D41357> (work in progress): > The diagnostics for each component are in their own component directories, > but are then all included from libClangBasic, a library none of those > components depends on. (so this isn't so much an inlining case as #include > based circular dependency) > > > Generally I'd like to get buy-in that stricter layering is desirable, and > that these few cases are at least sub-optimal, if accepted f...

...y: '/Users/joan/LLVM-9/llvm-project/build/Debug/lib/libclangAST.a' >> clang: error: no such file or directory: '/Users/joan/LLVM-9/llvm-project/build/Debug/lib/libclangLex.a' >> clang: error: no such file or directory: '/Users/joan/LLVM-9/llvm-project/build/Debug/lib/libclangBasic.a' >> >> Up until recently, I have worked with LLVM 7.0 and all what I did was downloading both llvm and clang from llvm.org <http://llvm.org/>, copied clang into llvm/tools, and ran the cmake application (not command line). That kind of worked except for some minor glitches...

...RewriteFrontend.a lib/libclangFrontend.a lib/libclangDriver.a lib/libclangParse.a lib/libLLVMMCParser.a lib/libLLVMProfileData.a lib/libLLVMOption.a lib/libclangRewrite.a lib/libclangSerialization.a lib/libclangSema.a lib/libclangAnalysis.a lib/libclangEdit.a lib/libclangAST.a lib/libclangLex.a lib/libclangBasic.a lib/libLLVMMC.a lib/libLLVMBitReader.a lib/libLLVMCore.a lib/libLLVMSupport.a -lrt -ldl -lcurses -lpthread -lz -lm -Wl,-rpath,"\$ORIGIN/../lib" && : /usr/bin/ld.gold: bin/lldb-argdumper: hidden symbol `__morestack' in /usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/6.2.1/libgcc.a...

...deGen.a lib/libLLVMCore.a lib/libLLVMipo.a > lib/libLLVMInstCombine.a lib/libLLVMInstrumentation.a lib/libLLVMMC.a > lib/libLLVMMCParser.a lib/libLLVMObjCARCOpts.a lib/libLLVMOption.a > lib/libLLVMScalarOpts.a lib/libLLVMSupport.a > lib/libLLVMTransformUtils.a lib/libLLVMVectorize.a lib/libclangBasic.a > lib/libclangCodeGen.a lib/libclangDriver.a lib/libclangFrontend.a > lib/libclangFrontendTool.a lib/libLLVMAsmPrinter.a > lib/libLLVMSelectionDAG.a lib/libLLVMCodeGen.a > lib/libLLVMX86AsmPrinter.a lib/libLLVMX86Utils.a lib/libLLVMX86Info.a > lib/libLLVMMCDisassembler.a lib/libcla...

...ne.a >> lib/libLLVMInstCombine.a lib/libLLVMInstrumentation.a lib/libLLVMMC.a >> lib/libLLVMMCParser.a lib/libLLVMObjCARCOpts.a lib/libLLVMOption.a >> lib/libLLVMScalarOpts.a lib/libLLVMSupport.a lib/libLLVMTransformUtils.a >> lib/libLLVMVectorize.a -lpthread lib/libclangBasic.a >> lib/libclangCodeGen.a lib/libclangDriver.a lib/libclangFrontend.a >> lib/libclangFrontendTool.a lib/libclangSerialization.a >> lib/libLLVMAArch64Desc.a lib/libLLVMAArch64Info.a >> lib/libLLVMAArch64Utils.a lib/libLLVMMIRParser.a lib/libLLVMAMDGPUDesc.a >&gt...

...VMInstCombine.a lib/libLLVMInstrumentation.a lib/libLLVMMC.a >>>> lib/libLLVMMCParser.a lib/libLLVMObjCARCOpts.a lib/libLLVMOption.a >>>> lib/libLLVMScalarOpts.a lib/libLLVMSupport.a lib/libLLVMTransformUtils.a >>>> lib/libLLVMVectorize.a -lpthread lib/libclangBasic.a >>>> lib/libclangCodeGen.a lib/libclangDriver.a lib/libclangFrontend.a >>>> lib/libclangFrontendTool.a lib/libclangSerialization.a >>>> lib/libLLVMAArch64Desc.a lib/libLLVMAArch64Info.a >>>> lib/libLLVMAArch64Utils.a lib/libLLVMMIRParser.a...

...needs to choose the right dependencies to link to or the program >> will not link. >> Clang Diagnostics <https://reviews.llvm.org/D41357> (work in progress): >> The diagnostics for each component are in their own component directories, >> but are then all included from libClangBasic, a library none of those >> components depends on. (so this isn't so much an inlining case as #include >> based circular dependency) >> >> >> Generally I'd like to get buy-in that stricter layering is desirable, and >> that these few cases are at least su...

...ressiveInstCombine.a > lib/libLLVMInstCombine.a lib/libLLVMInstrumentation.a lib/libLLVMMC.a > lib/libLLVMMCParser.a lib/libLLVMObjCARCOpts.a lib/libLLVMOption.a > lib/libLLVMScalarOpts.a lib/libLLVMSupport.a lib/libLLVMTransformUtils.a > lib/libLLVMVectorize.a -lpthread lib/libclangBasic.a > lib/libclangCodeGen.a lib/libclangDriver.a lib/libclangFrontend.a > lib/libclangFrontendTool.a lib/libclangSerialization.a > lib/libLLVMAArch64Desc.a lib/libLLVMAArch64Info.a > lib/libLLVMAArch64Utils.a lib/libLLVMMIRParser.a lib/libLLVMAMDGPUDesc.a > lib/libLLVMAMDGPU...