Search results

...ined to be necessary to maintain functionality in other RPMS that use llvm/clang. Any compatibility packages we add for Fedora 41 will be retired or orphane * '''Spec file merge.''' We plan to retire the clang, compiler-rt, lld and libomp packages and merge them in with llvm and have

...and llvm11 will be added to ensure that packages that currently depend on clang and llvm version 11 libraries will continue to work. ** Review existing llvm and clang compatibility packages and orphan any packages that are no longer used.

...and llvm9.0 will be added to ensure that packages that currently depend on clang and llvm version 9 libraries will continue to work. ** Review existing llvm and clang compatibility packages and orphan any packages that are no longer used.

...ies-In-clang-lib-Package | Stop shipping individual component libraries in clang-libs package]]=== ...angAST.so, etc.) from the clang-libs package. Packages that depend on the clang libraries should instead link against libclang-cpp.so.

Clang 16 will also benefit from these porting efforts. However, Clang 16 may land in Fedora before this work concludes, so the LLVM team is inves ...he-new-werror-implicit-function-declaration/65213/32 with an uncoordinated Clang update].

...he GPU hardware driver is in the linux kernel. The compiler is the system clang. The ROCm software stack provides the higher level libraries that enable o

...sed project with secure oriented development and with usage of Flawfinder, Clang Static Analyzer, OCLint and some other tools. I want to gain a opportunity

* Development - [[User:asosedkin|Alexander Sosedkin]] (asosedkin), [[User:clang|Clemens Lang]] (neverpanic)

...rent tools that can be used to actually execute builds (compilers like gcc/clang, build job schedulers like make/ninja, and so on). Thus, CMake upstream str

$ clang --version | head -n1 Debian clang version 11.1.0-4

* redhat-hardened-clang.cfg ...-rpm-macros means that they won't be run for packages that don't depend on clang or gcc. This will help speed up some builds.

...fore the 2.6 release. JIT compiler is supported when Ruby is built by GCC, Clang, or Microsoft VC++, which needs to be available on runtime. Otherwise you c

...build with GCC unless the upstream project for the package only supported Clang/LLVM. This change proposal replaces that policy with one where, given a go

* clang

...endpoint doesn't need to reply the same on 2020 for a Fedora Machine with Clang, as it did on 2015 for a CentOS rig with GCC - if you <s>know</s> get what

* python2-clang

- Linux/x86_64, gcc-3.[3-4], gcc-4.[0-6].x, clang-2.8