summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* clang-cross: Create cross binary copies instead of symlinksKhem Raj2025-03-211-1/+5
| | | | | | | | | | | This ensures that search path for subsequent tools e.g. linker assembler are searched in the same dir where <cross>-clang is installed. If its a symlink to ../clang then the reference installation dir is ../ and all cross-tools are not there so clang may fail to find assembler/linker from cross staging area and use /usr/bin/ld or /usr/bin/as which we do not want Signed-off-by: Khem Raj <raj.khem@gmail.com>
* python3-numpy: Enable vector extentions since highway pkg needs itKhem Raj2025-03-211-0/+5
| | | | | | | | | | | | | Fixes | ../numpy-2.2.3/numpy/_core/src/highway/hwy/ops/rvv-inl.h:644:17: error: use of undeclared identifier '__riscv_vsetvl_e32mf2' | ../numpy-2.2.3/numpy/_core/src/highway/hwy/ops/rvv-inl.h:644:17: error: use of undeclared identifier '__riscv_vsetvl_e32mf2' | ../numpy-2.2.3/numpy/_core/src/highway/hwy/ops/rvv-inl.h:644:17: error: use of undeclared identifier '__riscv_vsetvlmax_e64m1' | ../numpy-2.2.3/numpy/_core/src/highway/hwy/ops/rvv-inl.h:644:17: error: use of undeclared identifier '__riscv_vsetvl_e64m1' | ../numpy-2.2.3/numpy/_core/src/highway/hwy/ops/rvv-inl.h:644:17: error: use of undeclared identifier '__riscv_vsetvl_e64m1' | ../numpy-2.2.3/numpy/_core/src/highway/hwy/ops/rvv-inl.h:644:17: error: use of undeclared identifier '__riscv_vsetvl_e64m1' | fatal error: too many errors emitted, stopping now [-ferror-limit=] Signed-off-by: Khem Raj <raj.khem@gmail.com>
* bpftrace: Inherit bash completion classKhem Raj2025-03-211-1/+1
| | | | | | | | | | Fixes ERROR: bpftrace-0.23.0+git-r0 do_package: QA Issue: bpftrace: Files/directories were installed but not shipped in any package: /usr/share/bash-completion /usr/share/bash-completion/completions /usr/share/bash-completion/completions/bpftrace Signed-off-by: Khem Raj <raj.khem@gmail.com>
* bpftrace: Upgrade to 0.23.x branchKhem Raj2025-03-213-31/+4
| | | | | | This is targetting clang-20 support. Signed-off-by: Khem Raj <raj.khem@gmail.com>
* bcc: Upgrade to 0.33.0+Khem Raj2025-03-212-32/+3
| | | | | | Fix version string and add missing dependencies for ptests Signed-off-by: Khem Raj <raj.khem@gmail.com>
* clang.bbclass,compiler-rt: Do not set -target for native clangKhem Raj2025-03-214-25/+40
| | | | | | | | | | | | | | | | | | | | | | | | | When building native recipes using clang as native compiler e.g. compiler-rt-native, setting -target can be out of sync with the underlying distro's understanding of gcc tuple e.g. aarch64-linux or aarch64-linux-gnu, which is used by distros to house the gcc runtime e.g. on ubuntu /usr/lib/gcc/aarch64-linux-gnu/11 /usr/lib/gcc/aarch64-linux-gnu/9 if we provide -target its not able to deduce it from the build host which is required for native packages try with recipe-sysroot-native/usr/bin/clang -xc /dev/null -rtlib=libgcc --unwindlib=libgcc -stdlib=libstdc++ -v or recipe-sysroot-native/usr/bin/clang -xc /dev/null -rtlib=libgcc --unwindlib=libgcc -stdlib=libstdc++ -target aarch64-linux -v to see the difference Signed-off-by: Khem Raj <raj.khem@gmail.com>
* fmt: Disable invalide-specialization warning as errorKhem Raj2025-03-211-0/+3
| | | | | | This fails fmt to build with clang-20 + libcxx Signed-off-by: Khem Raj <raj.khem@gmail.com>
* include-what-you-use: Upgrade to 0.23+ releaseKhem Raj2025-03-211-2/+6
| | | | | | | | | | Use IWYU_RESOURCE_RELATIVE_TO=iwyu License-Update: Copyright year incremented [1] [1] https://github.com/include-what-you-use/include-what-you-use/commit/414d6f760caba8068b208d31125409a60930df69 Signed-off-by: Khem Raj <raj.khem@gmail.com>
* castxml: Upgrade to 0.6.11Khem Raj2025-03-211-1/+1
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* spirv-llvm-translator: Upgrade to clang 20.1 branchKhem Raj2025-03-211-4/+4
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* clang: Upgrade to 20.x releaseKhem Raj2025-03-2137-147/+189
| | | | | | | | | | | Release Notes clang-extra-tools [4] lld [3] clang [2] llvm [1] [1] https://releases.llvm.org/20.1.0/docs/ReleaseNotes.html [2] https://releases.llvm.org/20.1.0/tools/clang/docs/ReleaseNotes.html [3] https://releases.llvm.org/20.1.0/tools/lld/docs/ReleaseNotes.html [4] https://releases.llvm.org/20.1.0/tools/clang/tools/extra/docs/ReleaseNotes.html Signed-off-by: Khem Raj <raj.khem@gmail.com>
* fix: [Issue #1061] - check for existence before trying to process a fileaprospero2025-03-171-2/+6
| | | | | | | | | | | | | | In certain configurations LLVMConfig.cmake does not exist. If that's the case do_install breaks for the nativesdk-clang recipe. Eg. set the following: EXTRA_OECMAKE:append:pn-nativesdk-clang = " -DLLVM_INSTALL_TOOLCHAIN_ONLY=ON" as suggested here: https://llvm.org/docs/BuildingADistribution.html Signed-off-by: aprospero <apro@posteo.de>
* clang: set BPN = "clang" for clang cross,crosssdk,cross-canadian recipesHongxu Jia2025-02-246-0/+12
| | | | | | | | | | | | | | Similar gcc recipes in oe-core [1], set BPN = "clang" in common.inc for clang cross,crosssdk,cross-canadian recipes, but the recipe compiler-rt-sanitizers, compiler-rt, libclc, libcxx, openmp which shares sources with clang are not affected Due to commit [2], the BPN of llvm-project-source is not affected by this commit [1] https://github.com/openembedded/openembedded-core/commit/a2c5509520d5c3e082f55844e6545d0309565f8f [2] https://github.com/kraj/meta-clang/commit/e7517e1910a7d49abb4782fa0778f0b958f7717d Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
* libmodulemd,libblockdev,webkitgtk: Disable g-i on x86-64Khem Raj2025-02-111-1/+5
| | | | | | | Somehow g-i parser is confused with glibc 2.41 headers on x86-64 as well when using clang, it works ok when using gcc Signed-off-by: Khem Raj <raj.khem@gmail.com>
* libslirp,avahi-libnss-mdns: Add --undefined-version to LDFLAGS with LLDKhem Raj2025-02-091-0/+4
| | | | | | LLD does not understand the linker script versioning scheme as BFD linker does Signed-off-by: Khem Raj <raj.khem@gmail.com>
* libmodulemd,libblockdev,webkitgtk: Disable g-i on x86Khem Raj2025-02-041-0/+6
| | | | | | | Somehow g-i parser is confused with glibc 2.41 headers on x86 when using clang, it works ok when using gcc Signed-off-by: Khem Raj <raj.khem@gmail.com>
* recipes: Update to match OE-Core virtual/cross-* changesRichard Purdie2025-01-2110-10/+10
| | | | | | | Update meta-clang to match OE-Core changes to use recipe specific virtual providers (without yet switching to the new switching mechanism). Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lttng-ust: Link with libatomic on 32bit x86Khem Raj2025-01-181-0/+4
| | | | | | Clang generates _atomic_store calls Signed-off-by: Khem Raj <raj.khem@gmail.com>
* clang: Upgrade to 19.1.7Khem Raj2025-01-183-3/+3
| | | | | | | | | | | Changes described here https://discourse.llvm.org/t/llvm-19-1-7-released/84062 Brings [1] [1] https://github.com/llvm/llvm-project/compare/llvmorg-19.1.6...llvmorg-19.1.7 Signed-off-by: Khem Raj <raj.khem@gmail.com>
* boost: Use -no-integrated-as for armKhem Raj2025-01-181-0/+8
| | | | | | | With boost 1.87, internal assembler seems to be not able to compile boost only on arm ( 32bit ), so for now disable internal assembler Signed-off-by: Khem Raj <raj.khem@gmail.com>
* snort3,libdaq: Always use libstdc++ for C++ runtimeKhem Raj2025-01-071-0/+3
| | | | | | | Newer version of snort3 does not work with libc++, until its fixed resort to using libstdc++ Signed-off-by: Khem Raj <raj.khem@gmail.com>
* bingen-cli: Upgrade to 0.71.1Goetz2025-01-072-109/+109
| | | | | | | | | | | | | | Related to some issues in my project with compiling aws-lc-rs, issue https://github.com/aws/aws-lc-rs/issues/591, I updated to the current version. Tested on my project https://github.com/MrTarantoga/SpotyPee/commit/f83b2a0c32f28af2c81069ced5b9942bbb98d25a and with the poky standard arm environment. Changelog https://github.com/rust-lang/rust-bindgen/releases/tag/v0.71.1 Signed-off-by: Götz Grimmer <goetz-dev@web.de>
* clang: Upgrade to 19.1.6Khem Raj2024-12-253-3/+3
| | | | | | | | Brings following changes [1] [1] https://github.com/llvm/llvm-project/compare/llvmorg-19.1.5...llvmorg-19.1.6 Signed-off-by: Khem Raj <raj.khem@gmail.com>
* clang: Upgrade to 19.1.5 releaseKhem Raj2024-12-173-3/+3
| | | | | | | Changes https://discourse.llvm.org/t/llvm-19-1-5-released/83455 Signed-off-by: Khem Raj <raj.khem@gmail.com>
* ot-br-posix: Disable sign-compare warning as errorKhem Raj2024-12-171-1/+2
| | | | | | Use same way for seatd Signed-off-by: Khem Raj <raj.khem@gmail.com>
* libpam: Disable --undefined-version with LLDKhem Raj2024-12-171-0/+2
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* clang: remove PROVIDES:append settingsChen Qi2024-12-021-3/+0
| | | | | | | | | | | | | | | | | | | | With these settings, we'll have multiple providers of llvm. This means that with pristine poky master + meta-clang master, we'll have some output like below: NOTE: Multiple providers are available for llvm-native (llvm-native, clang-native) Consider defining a PREFERRED_PROVIDER entry to match llvm-native And when running 'bitbake world', we'll get error messages like below: ERROR: Multiple .bb files are due to be built which each provide llvm-native: virtual:native:/PATH/TO/poky/meta/recipes-devtools/llvm/llvm_19.1.4.bb virtual:native:/PATH/TO/Yocto/poky/meta-clang/recipes-devtools/clang/clang_git.bb As the README.md has already specified how to use this layer, let's remove such settings before sorting things out. Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
* clang: Upgrade to 19.1.4Khem Raj2024-11-2848-191/+162
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* SECURITY: Add readme file for security issue reportingKhem Raj2024-11-201-0/+20
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* openssl: Drop riscv workarounds to add libatomicKhem Raj2024-10-291-9/+1
| | | | | | | Additionally disable relaxation on rv32 with lld see [1] [1] https://github.com/llvm/llvm-project/issues/113838 Signed-off-by: Khem Raj <raj.khem@gmail.com>
* nonclangable: Fix append and override orderKhem Raj2024-10-261-10/+10
| | | | | | VAR:append:<OVERRIDES> is the right way to use it Signed-off-by: Khem Raj <raj.khem@gmail.com>
* doxygen: Disable missing-template-arg-list-after-template-kw as error with clangKhem Raj2024-10-261-0/+2
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* busybox: Loosen the regexp to include all busying 1.xKhem Raj2024-10-251-0/+0
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* doxygen: added to LIBCPLUSPLUSJan Vermaete2024-10-251-0/+1
| | | | Signed-off-by: Jan Vermaete <jan.vermaete@gmail.com>
* clang_git.bb: assign PYTHON_PN to LLDB_PYTHON_EXE_RELATIVE_PATHJan Kircher2024-10-241-2/+2
| | | | Signed-off-by: Jan Kircher <jan.kircher@leica-microsystems.com>
* ostree: Use libgcc for compiler runtime when using glibc for systemKhem Raj2024-10-181-1/+11
| | | | | | | | | | | | | glibc static library expects builtins from libgcc which may not exist in compiler-rt, therefore use libgcc explicitly. Now that static is enabled by default in packageconfig Fix is taken from [1] [1] https://github.com/foundriesio/meta-lmp/commit/0abb08c83aee7027711f538e29a5ff16dc334304 Signed-off-by: Khem Raj <raj.khem@gmail.com>
* tomlplusplus: Pin to use libstdc++ with clangKhem Raj2024-10-171-0/+2
| | | | | | | libc++ seems to result in test failures, perhaps something to fix in toml++ but it needs to be triaged. Signed-off-by: Khem Raj <raj.khem@gmail.com>
* clang: Upgrade to 19.1.2 releaseKhem Raj2024-10-163-10/+10
| | | | | | | | | Release has changes as mentioned in [1] and [2] [1] https://discourse.llvm.org/t/llvm-19-1-1-released/82321 [2] https://discourse.llvm.org/t/llvm-19-1-2-released/82550 Signed-off-by: Khem Raj <raj.khem@gmail.com>
* llvm-project-source.inc: fix racing on building ↵Hongxu Jia2024-10-122-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | lib32-llvm-project-source-19.1.0 and llvm-project-source-19.1.0 While enabling multilib, build lib32-llvm-project-source-19.1.0 and llvm-project-source-19.1.0 at the same time: $ MACHINE = "qemux86-64" $ require conf/multilib.conf $ MULTILIBS = "multilib:lib32" $ DEFAULTTUNE:virtclass-multilib-lib32 = "x86" $ bitbake lib32-llvm-project-source-19.1.0 llvm-project-source-19.1.0 ... $ cat tmp/work-shared/llvm-project-source-19.1.0-r0/temp/log.task_order 20241012-070604.819630 do_recipe_qa (2728706): log.do_recipe_qa.2728706 20241012-070604.883194 do_recipe_qa (2728707): log.do_recipe_qa.2728707 20241012-070605.037448 do_fetch (2728779): log.do_fetch.2728779 20241012-070605.165280 do_fetch (2728848): log.do_fetch.2728848 20241012-071030.798104 do_unpack (2733554): log.do_unpack.2733554 20241012-071030.864536 do_unpack (2733559): log.do_unpack.2733559 There are two tasks for do_fetch, do_unpack and others, so there are race issues. Both of them have the same hardcode 'llvm-project-source-' prefix in ${WORKDIR} and ${S}, explicitly disable lib32-llvm-project-source-19.1.0 for multilib Set llvm-project-source as BPN of llvm-project-source-19.1.0 Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
* libunix-statgrab: Use compiler for linker always irrespective of compilerKhem Raj2024-10-111-1/+3
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* libhugetlbfs: Always use BFD linker when using clang toolchainKhem Raj2024-10-111-0/+1
| | | | | | | | it uses its own linker wrapper which calls LD variable in the end and expects it to be traditional GNU linker. Lets provide it what it needs. Signed-off-by: Khem Raj <raj.khem@gmail.com>
* clang.bbclass: Use ld.lld as default for LD with ld-is-lldKhem Raj2024-10-101-0/+1
| | | | | | | | When ld-is-lld is in DISTRO_FEATURE, user wants to use lld as system linker, therefore honor the setting for bare linker as well, for compiler its being taken care by clang itself using -fuse-ld=lld Signed-off-by: Khem Raj <raj.khem@gmail.com>
* clang: Do not override default ld with ld.lldKhem Raj2024-10-102-11/+1
| | | | | | | | | | | This creates a problem when swapping linkers, it does not work without cleaning the recipe first, in anycase if we want to use lld as default in clang then it should be done during clang compile Add packageconfig to let clang defualt Signed-off-by: Khem Raj <raj.khem@gmail.com>
* Revert "libhugetlbfs: Do not use lld linker"Khem Raj2024-10-101-2/+0
| | | | This reverts commit d1793483a76914baa11a44eb767acaeef675d310.
* Update README.mdPablo Saavedra Rodiño2024-10-091-1/+1
| | | | | | Trivial fix for a typo in the LIBCPLUSPLUS examples. Signed-off-by: Pablo Saavedra <psaavedra@igalia.com>
* libhugetlbfs: Do not use lld linkerKhem Raj2024-10-071-0/+2
| | | | | | It needs to use BFD linker Signed-off-by: Khem Raj <raj.khem@gmail.com>
* layer.conf: Update to walnascar (5.2) layer/release seriesKhem Raj2024-10-071-1/+1
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* u-boot: u-boot is clangableJon Mason2024-10-071-2/+0
| | | | | | | | | | | | | | Since clang is at version 19 now, remove the blocking of building u-boot. I'm not seeing any issues with building u-boot and running testimage for qemuarm, qemuarm64, and qemumips. Based on the original comment, this limitation probably should've been only applied to mips. Leaving the BSP versions of u-boot in nonclangable, as I don't know if those have issues or not, and thought it better to err on the side of caution. Signed-off-by: Jon Mason <jdmason@kudzu.us>
* Revert "vte: Use libstdc++ when using clang"Ross Burton2024-09-301-6/+0
| | | | | | | | | | This issue has been resolved upstream: https://gitlab.gnome.org/GNOME/vte/-/commit/c8838779d5f8c0e03411cef9775cd8f5a10a6204 This reverts commit 70295d739f830a8d2abb2ad961e1c544f01be197. Signed-off-by: Ross Burton <ross.burton@arm.com>
* clang: Do not package clang-pseudo clang-pseudo-gen and clang-renameKhem Raj2024-09-261-6/+9
| | | | | | | | | These tools are unmaintained and clang-20+ has removed them [1] [2] [1] https://github.com/llvm/llvm-project/commit/ed8f78827895050442f544edef2933a60d4a7935 [2] https://github.com/llvm/llvm-project/commit/40c45b6b43180221acb49f387e7d3158adf49e3e Signed-off-by: Khem Raj <raj.khem@gmail.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-07-08 03:33:52 +0000