summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* clang_git.bb: assign PYTHON_PN to LLDB_PYTHON_EXE_RELATIVE_PATHstyheadJan Kircher2024-10-251-2/+2
| | | | Signed-off-by: Jan Kircher <jan.kircher@leica-microsystems.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>
* vte: Disable gi data generation when using clangKhem Raj2024-09-241-0/+4
| | | | | | | Somehow clang built binaries used in intermediate step crashes the qemu user mode. Signed-off-by: Khem Raj <raj.khem@gmail.com>
* vte: Use libstdc++ when using clangKhem Raj2024-09-241-0/+6
| | | | | | It does not build with libc++ anymore. Signed-off-by: Khem Raj <raj.khem@gmail.com>
* qtwebengine: Use clang for native toolchain as wellKhem Raj2024-09-191-0/+1
| | | | | | | | | This makes the chromium build less confused when mixing native compiler for gcc and target compiler for clang this does not sit well with gn build system and it starts to pass clang options to gcc, which does not always work Signed-off-by: Khem Raj <raj.khem@gmail.com>
* python3-cffi: Ad clang to rdeps for ptests to passKhem Raj2024-09-181-0/+5
| | | | | | | ptest tries to compile some portions on the target and demands the compiler that was used to cross-compile it Signed-off-by: Khem Raj <raj.khem@gmail.com>
* python3-drgn: Use gcc when compiling for riscv32Khem Raj2024-09-181-0/+2
| | | | | | | openmp port for riscv32 is not yet available so we can not use clang for it for now. Signed-off-by: Khem Raj <raj.khem@gmail.com>
* nmap: Remove LLD build workaround for RISCV-64Khem Raj2024-09-181-3/+0
| | | | | | This is no longer needed with clang-19 Signed-off-by: Khem Raj <raj.khem@gmail.com>
* lldb: Enable on RISCV64Khem Raj2024-09-181-2/+1
| | | | | | With clang-19 LLDB is building fine for RISCV64 Signed-off-by: Khem Raj <raj.khem@gmail.com>
* libjxl: Use -Og instead of -O2 with clang-19Khem Raj2024-09-181-0/+4
| | | | | | | | This is a workaround until [1] is fixed [1] https://github.com/llvm/llvm-project/issues/108262 Signed-off-by: Khem Raj <raj.khem@gmail.com>
* recipes: Use gcc or clang/libstdc++ for some recipesKhem Raj2024-09-181-1/+13
| | | | | | | | These recipes do not yet build with libc++-19, for now use libstdc++, poco and netdata do not compile with clang-19 at all Signed-off-by: Khem Raj <raj.khem@gmail.com>
* clang: scan-build-py: respect LLVM_LIBDIR_SUFFIX like other tools doMartin Jansa2024-09-182-0/+93
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | * other libraries are installed in 'lib64' or 'lib32' based on LLVM_LIBDIR_SUFFIX value, but libscanbuild files were always installed in 'lib' * fixes: ERROR: QA Issue: lib32-clang: Files/directories were installed but not shipped in any package: /usr/lib/libscanbuild /usr/lib/libscanbuild/intercept.py /usr/lib/libscanbuild/analyze.py /usr/lib/libscanbuild/clang.py /usr/lib/libscanbuild/report.py /usr/lib/libscanbuild/arguments.py /usr/lib/libscanbuild/shell.py /usr/lib/libscanbuild/compilation.py /usr/lib/libscanbuild/__init__.py /usr/lib/libscanbuild/resources /usr/lib/libscanbuild/resources/sorttable.js /usr/lib/libscanbuild/resources/selectable.js /usr/lib/libscanbuild/resources/scanview.css Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid installing them or delete them within do_install. lib32-clang: 13 installed and not shipped files. [installed-vs-shipped] e.g. in multilib build where libdir is set to /usr/lib32 or /usr/lib64. Signed-off-by: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* clang: Upgrade to 19.1.0 releaseKhem Raj2024-09-1840-368/+256
| | | | | | | | | | | | Release Notes below llvm - https://releases.llvm.org/19.1.0/docs/ReleaseNotes.html clang - https://releases.llvm.org/19.1.0/tools/clang/docs/ReleaseNotes.html lld - https://releases.llvm.org/19.1.0/tools/lld/docs/ReleaseNotes.html libc++ - https://releases.llvm.org/19.1.0/projects/libcxx/docs/ReleaseNotes.html clang-extra - https://releases.llvm.org/19.1.0/tools/clang/tools/extra/docs/ReleaseNotes.html Signed-off-by: Khem Raj <raj.khem@gmail.com>
* spirv-llvm-translator: Bump to release_190Khem Raj2024-09-181-4/+4
| | | | | | Fixes build with clang-19 Signed-off-by: Khem Raj <raj.khem@gmail.com>
* pbzip2: Do not use libc++ for nowKhem Raj2024-09-181-0/+3
| | | | | | it need to be ported to not use generic char_traits Signed-off-by: Khem Raj <raj.khem@gmail.com>
* bpftrace: fix buildpaths QA issuesMartin Jansa2024-09-042-0/+45
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Avoid line statements from bison to fix: WARNING: bpftrace-0.21.2+git-r0 do_package_qa: QA Issue: File /usr/src/debug/bpftrace/0.21.2+git/parser.tab.cc in package bpftrace-src contains reference to TMPDIR [buildpaths] WARNING: bpftrace-0.21.2+git-r0 do_package_qa: QA Issue: File /usr/src/debug/bpftrace/0.21.2+git/location.hh in package bpftrace-src contains reference to TMPDIR [buildpaths] WARNING: bpftrace-0.21.2+git-r0 do_package_qa: QA Issue: File /usr/src/debug/bpftrace/0.21.2+git/parser.tab.hh in package bpftrace-src contains reference to TMPDIR [buildpaths] WARNING: bpftrace-0.21.2+git-r0 do_package_qa: QA Issue: File /usr/src/debug/bpftrace/0.21.2+git/lex.yy.cc in package bpftrace-src contains reference to TMPDIR [buildpaths] * there are still few more buildpaths issues with ptest enabled: WARNING: bpftrace-0.21.2+git-r0 do_package_qa: QA Issue: File /usr/src/debug/bpftrace/0.21.2+git/tests/data/dwarf_data.h in package bpftrace-src contains reference to TMPDIR [buildpaths] WARNING: bpftrace-0.21.2+git-r0 do_package_qa: QA Issue: File /usr/lib/bpftrace/ptest/tests/.debug/bpftrace_test in package bpftrace-dbg contains reference to TMPDIR [buildpaths] WARNING: bpftrace-0.21.2+git-r0 do_package_qa: QA Issue: File /usr/lib/bpftrace/ptest/tests/bpftrace_test in package bpftrace-ptest contains reference to TMPDIR [buildpaths] WARNING: bpftrace-0.21.2+git-r0 do_package_qa: QA Issue: File /usr/lib/bpftrace/ptest/tests/testlibs/cmake_install.cmake in package bpftrace-ptest contains reference to TMPDIR [buildpaths] WARNING: bpftrace-0.21.2+git-r0 do_package_qa: QA Issue: File /usr/lib/bpftrace/ptest/tests/testlibs/CTestTestfile.cmake in package bpftrace-ptest contains reference to TMPDIR [buildpaths] WARNING: bpftrace-0.21.2+git-r0 do_package_qa: QA Issue: File /usr/lib/bpftrace/ptest/tests/testprogs/cmake_install.cmake in package bpftrace-ptest contains reference to TMPDIR [buildpaths] WARNING: bpftrace-0.21.2+git-r0 do_package_qa: QA Issue: File /usr/lib/bpftrace/ptest/tests/testprogs/CTestTestfile.cmake in package bpftrace-ptest contains reference to TMPDIR [buildpaths] * lower buildpaths from ERROR_QA to WARN_QA when ptest is enabled fixing .cmake files might be simple, but the embedded path to dwarf_data.h in bpftrace_test will be more complicated, so will leave it to someone actually using bpftrace (and its ptest). bpftrace/0.21.2+git/package $ grep -R styhead . ./usr/lib/bpftrace/ptest/tests/testlibs/cmake_install.cmake:# Install script for directory: ${WORKDIR}/git/tests/testlibs ./usr/lib/bpftrace/ptest/tests/testlibs/cmake_install.cmake: set(CMAKE_OBJDUMP "${WORKDIR}/recipe-sysroot-native/usr/bin/aarch64-webos-linux/aarch64-webos-linux-objdump") ./usr/lib/bpftrace/ptest/tests/testlibs/CTestTestfile.cmake:# Source directory: ${WORKDIR}/git/tests/testlibs ./usr/lib/bpftrace/ptest/tests/testlibs/CTestTestfile.cmake:# Build directory: ${WORKDIR}/build/tests/testlibs grep: ./usr/lib/bpftrace/ptest/tests/.debug/bpftrace_test: binary file matches grep: ./usr/lib/bpftrace/ptest/tests/bpftrace_test: binary file matches ./usr/lib/bpftrace/ptest/tests/testprogs/cmake_install.cmake:# Install script for directory: ${WORKDIR}/git/tests/testprogs ./usr/lib/bpftrace/ptest/tests/testprogs/cmake_install.cmake: set(CMAKE_OBJDUMP "${WORKDIR}/recipe-sysroot-native/usr/bin/aarch64-webos-linux/aarch64-webos-linux-objdump") ./usr/lib/bpftrace/ptest/tests/testprogs/CTestTestfile.cmake:# Source directory: ${WORKDIR}/git/tests/testprogs ./usr/lib/bpftrace/ptest/tests/testprogs/CTestTestfile.cmake:# Build directory: ${WORKDIR}/build/tests/testprogs ./usr/src/debug/bpftrace/0.21.2+git/tests/data/dwarf_data.h:constexpr inline const char *dwarf_data_cxx_path = "${WORKDIR}/build/tests/data/data_source_cxx"; Signed-off-by: Martin Jansa <martin.jansa@gmail.com>
* bcc: lower buildpaths from ERROR_QA to WARN_QA when ptest is enabledMartin Jansa2024-09-041-0/+8
| | | | | | | | | | | WARNING: bcc-0.30.0+git-r0 do_package_qa: QA Issue: File /usr/lib/bcc/ptest/tests/cc/test_libbcc_no_libbpf in package bcc-ptest contains reference to TMPDIR [buildpaths] This one is difficult to resolve, because the tests use CMAKE_CURRENT_BINARY_DIR directly in .cc e.g.: https://github.com/iovisor/bcc/commit/7271bfc946a19413761be2e3c60c48bf72c5eea1#diff-233a0bfa490f3d7466c49935b64c86dd93956bbc0461f5af703b344cf6601461 we would probably need to use separate variable for "runtime" path for test assets from the standard CMAKE_CURRENT_BINARY_DIR variable or use relative path from the test binary Signed-off-by: Martin Jansa <martin.jansa@gmail.com>
* bpftrace: move from dynamic-layers/openembedded-layer to ↵Martin Jansa2024-09-043-0/+0
| | | | | | | | | | | | | | | | | | | | | | | dynamic-layers/meta-python * bpftrace itself doesn't depend on meta-python, but bpftrace from dynamic-layers/openembedded-layer depends on bcc from dynamic-layers/meta-python so better to move it there. This way both bcc and bpftrace are either both available at the same time or neither of them. * fixes https://github.com/kraj/meta-clang/issues/985 ERROR: Nothing PROVIDES 'bcc' (but /mnt/secondary/poky/meta-clang/dynamic-layers/openembedded-layer/recipes-devtools/bpftrace/bpftrace_0.20.1.bb DEPENDS on or otherwise requires it). Close matches: bc byacc NOTE: Runtime target 'bpftrace' is unbuildable, removing... Missing or unbuildable dependency chain was: ['bpftrace', 'bcc'] ERROR: Required build target 'core-image-minimal' has no buildable providers. Missing or unbuildable dependency chain was: ['core-image-minimal', 'bpftrace', 'bcc'] when only openembedded-layer (meta-oe) is in BBLAYERS and meta-python isn't. Signed-off-by: Martin Jansa <martin.jansa@gmail.com>
* vulkan-samples: Re-introduce -Wno-error=deprecated-declarationsKhem Raj2024-09-031-1/+2
| | | | | | Its still needed with clang-18 with libc++ Signed-off-by: Khem Raj <raj.khem@gmail.com>
* include-what-you-use: Upgrade to tip of trunkKhem Raj2024-09-021-2/+2
| | | | | | Brings clang-19 support Signed-off-by: Khem Raj <raj.khem@gmail.com>
* bpftrace: Upgrade to 0.21.2+Khem Raj2024-09-026-500/+12
| | | | | | Fix build on upcoming clang-19 Signed-off-by: Khem Raj <raj.khem@gmail.com>
* vulkan-samples: Add Wno-error=overriding-option and remove ↵Khem Raj2024-08-311-2/+2
| | | | | | | | | | Wno-error=deprecated-declarations https://github.com/jtv/libpqxx/issues/738 seems to have been fixed Workaround issue with clang-20 caused by https://github.com/ARM-software/astc-encoder/commit/8377e52e57c1fb5bcf159aa981f3b25b7bad1cb3 Signed-off-by: Khem Raj <raj.khem@gmail.com>
* Revert "libcxx: Do not induce -mbranch-protection externally on arm64"Jose Quaresma2024-08-211-1/+0
| | | | | | | | This reverts commit 96b2f3da50c8cf814f661fba37df0a098457b016. The is required to be applied globally and not only for libcxx. Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io>
* nonclangable: remove '-mbranch-protection=standard' globally on aarch64Jose Quaresma2024-08-211-0/+3
| | | | | | | | | | | | | | | On aarch64 the handling of runtime exception is broken when build with clang. There is currently a fix for libcxx on the layer but it is not enough and this same fix needs to be applied globally. First fix attempt just include libcxx: https://github.com/kraj/meta-clang/issues/963 https://github.com/kraj/meta-clang/pull/968 Remaining reported issue: https://github.com/kraj/meta-clang/issues/998 Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io>
* Revert "rust-llvm: Fix build with clang-18"Khem Raj2024-08-202-355/+0
| | | | This reverts commit 292506c431f2037d35ccb7f4f957ce143b617450.
* Update libcxx_git.bbOiouuu2024-08-201-1/+1
| | | Fix syntax error, '-DD' -> '-D'
* compiler-rt-sanitizers: Package a symlink to address headers include issueKhem Raj2024-08-111-13/+13
| | | | | | | | | Instead of moving the whole install under major.minor.patch, create a symlink so both can be included Fixes https://github.com/kraj/meta-clang/issues/978 Signed-off-by: Khem Raj <raj.khem@gmail.com>
* clang: Set -DLLVM_APPEND_VC_REV=OFFKhem Raj2024-08-096-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes Issue #991 If this is not disabled, the build tries to use CMake magic to compute repository and sha1 its building, however in case of OE it gets it completely wrong when building from tarball, because its building under TMPDIR which maybe a directory under main repo checkout e.g. poky tree so it traverses up and finds the sha of poky and assumes that its building from a git tree instead of tarball and emits the version control info into clang -v output e.g. ❯ ../image/mnt/b/yoe/master/build/tmp/work/x86_64-linux/clang-native/20.0.0/recipe-sysroot-native/usr/bin/clang -v clang version 20.0.0 (/home/kraj/work/llvm-project f133c59b33a749dc6d5fa8fb9a2366b95ea45068) This can contain buildpaths since work-shared is where llvm sources will be and they will appear here. Therefore, avoid cmake trying to do this and we get good clean version info > ../recipe-sysroot-native/usr/bin/aarch64-yoe-linux/aarch64-yoe-linux-clang clang version 20.0.0 This will also avoid emitting buildpaths into debuginfo in some cases where compiler version is emitted into build.id info Signed-off-by: Khem Raj <raj.khem@gmail.com>
* libclc: use cmake-qemu to clean up recipeRoss Burton2024-08-061-14/+2
| | | | | | | The cmake-qemu class handles using qemu-user as a CMake emulator, so use that and clean up the recipe. Signed-off-by: Ross Burton <ross.burton@arm.com>
* clang: improve reproducibilityOleh Matiusha2024-07-301-4/+16
| | | | | | | | | | | | | | | | | Currently, class-target is reproducible, but class-nativesdk is not. What I did: - noticed that BuildVariables.inc contains meaningless path fragments after running sed, so I adjusted sed commands to remove the rest of paths as well; - moved common code into a function, which is then called twice; - changed do_compile:prepend into do_configure:append, this is more conventional and intuitive; - verified that the resulting code works for both target and nativesdk after these changes. Signed-off-by: Oleh Matiusha <omatiush@cisco.com>
* compiler-rt-sanitizers: Fix native build tooling pathsEric Sun2024-07-291-3/+6
| | | | | | | | | | | Native builds of compiler-rt-sanitizers fail because llvm-ranlib, llvm-ar, and llvm-nm are not found where the recipe specifies that they'll be. Other recipes (in particular: compiler-rt) only specify the locations of those tools for target and nativesdk builds, and they build fine. This commit implements the same thing for compiler-rt-sanitizers, fixing native builds. Signed-off-by: Eric Sun <ericsun2@cisco.com>
* include-what-you-use: new recipeChristian Eggers2024-07-241-0/+22
| | | | | | Clang based checker for C/C++ header includes. "Experimental software, as of June 2024.", but definitely very useful. Signed-off-by: Christian Eggers <ceggers@arri.de>
* bindgen-cli: update 0.64.0 -> 0.69.4Markus Volk2024-07-222-111/+98
| | | | | | | | mesa requires at least bindgen-cli_0.65.0 https://gitlab.freedesktop.org/mesa/mesa/-/blob/main/src/gallium/frontends/rusticl/meson.build#L111 Signed-off-by: Markus Volk <f_l_k@t-online.de> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* perf: Use gcc as default compilerKhem Raj2024-07-221-0/+1
| | | | | | | | | Since its being build from kernel sources which are procecced with gcc by default KERNEL_CC is gcc, its a constant battle to keep this compiling with clang, so unless clang is also used to compile kernel this is a fruitless excercise to use clang just for perf. Signed-off-by: Khem Raj <raj.khem@gmail.com>
* bcc: Upgrade to 0.30.0+Khem Raj2024-07-151-1/+3
| | | | | | This will fix build on clang19+ Signed-off-by: Khem Raj <raj.khem@gmail.com>
* util-linux,util-linux-libuuid: Use -Wl,--undefined-version' with lld linkerKhem Raj2024-07-151-0/+3
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* clang: remove pointless experimental targets codeRoss Burton2024-07-111-9/+0
| | | | | | | | | | | LLVM_EXPERIMENTAL_TARGETS_TO_BUILD is appended with the value of get_clang_experimental_target_arch() which is just the value of get_clang_experimental_arch which is always the empty string despite appearances. Thus none of this is useful, remove it. Signed-off-by: Ross Burton <ross.burton@arm.com>
* Revert "recipes-devtools/llvm/llvm_%.bbappend: fix the build of bpftrace ↵Khem Raj2024-07-101-1/+0
| | | | | | | | ptest failed" This caused meta-clang to fail check-layer-nightly builds This reverts commit 0c2b19b7ad03bba7c21b6bf111ba1a118ea9d44a.
* qt6/qtbase: Always use lld linker with clangKhem Raj2024-07-101-0/+1
| | | | | | | | | | chromium has certain options e.g. -Wl,-mllvm,xxx assumed when compiler chosen is clang. These options are not understood by GNU linker, therefore force using LLD when clang toolchain is used to compile QT6 components. Signed-off-by: Khem Raj <raj.khem@gmail.com>
* recipes-devtools/llvm/llvm_%.bbappend: fix the build of bpftrace ptest failedHongxu Jia2024-07-081-0/+1
| | | | | | | | | | | | | | | | | | | | | Due to commit [1][2], llvm-native was added to bpftrace to provide llvm-objcopy for the ptest. But because of commit [3], llvm-native requires opengl in DISTRO_FEATURES to support libllvm. In order to make the build of bpftrace ptest work, explicitly add libllvm to PACKAGECONFIG for llvm-native if ptest enabled. According to [2][3], bpftrace used llvm-objcopy to generate BTF data for unit tests, regardless opengl in DISTRO_FEATURES, enable accelerated software renderer or not does not have side effect on bpftrace [1] https://github.com/kraj/meta-clang/commit/bf6c02a47fb2ffec735df6c7dd642432f3681337 [2] https://github.com/bpftrace/bpftrace/commit/6cc531e35cd3bf77aa2a30cef3e3481c9c53042e [3] https://git.openembedded.org/openembedded-core/commit/?id=ec22bfa67f6f1766102501d4593ce29aafe8c166 Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
* bluez5: Use BFD linker instead of lldKhem Raj2024-07-081-1/+2
| | | | | | | | | | | | | | | Some ptests do not build with LLD on RISCV64 | riscv64-yoe-linux-ld: error: undefined symbol: __stop___debug | >>> referenced by log.c:168 (/usr/src/debug/bluez5/5.76/../bluez-5.76/src/log.c:168) | >>> src/log.o:(__btd_log_init) | | riscv64-yoe-linux-ld: error: undefined symbol: __start___debug | >>> referenced by log.c:168 (/usr/src/debug/bluez5/5.76/../bluez-5.76/src/log.c:168) | >>> src/log.o:(__btd_log_init) | >>> the encapsulation symbol needs to be retained under --gc-sections properly; consider -z nostart-stop-gc (see https://lld.llvm.org/ELF/start-stop-gc) Signed-off-by: Khem Raj <raj.khem@gmail.com>
* libcxx: Do not induce -mbranch-protection externally on arm64Khem Raj2024-07-041-0/+1
| | | | | | | | | | | | On arm64 OE-Core has moved the gcc default configuration done with --enable-standard-branch-protection to be a CFLAGS option which is appended to CC variable, this means that this option can override the package's default to not use it e.g. libunwind where the library has to be built without it. Fixes https://github.com/kraj/meta-clang/issues/963 Signed-off-by: Khem Raj <raj.khem@gmail.com>
* nativesdk-clang-glue: Delete do_create_package_spdx taskKhem Raj2024-07-041-0/+1
| | | | | | | SPDX 3.0 has this task executing but other tasks which it depends on are deleted, delete this one too. Signed-off-by: Khem Raj <raj.khem@gmail.com>
* clang.bbclass: remove mcpu option with qualifiers for the octeontx2 coreRuiqiang Hao2024-07-041-1/+1
| | | | | | | | | Currently, only the '-mcpu=octeontx2' option is removed, and any -mcpu parameters with qualifiers (such as +crc+crypto) are not removed, e.g., '-mcpu=octeontx2+crypto'. Remove these mcpu parameters with qualifiers by using '-mcpu=octeontx2${TUNE_CCARGS_MARCH_OPTS}'. Signed-off-by: Ruiqiang Hao <Ruiqiang.Hao@windriver.com>
* clang: Add packageconfig option for build-idKhem Raj2024-07-041-1/+2
| | | | | | | | Enable it by default, since it is needed for debuginfod to work Fixes https://github.com/kraj/meta-clang/issues/956 Signed-off-by: Khem Raj <raj.khem@gmail.com>
* python-bcrypt: Do not use lld when building with ptests on.Khem Raj2024-07-021-0/+1
| | | | | | | | | | Somehow linker/lld here fails to link ptests with cargo, therefore workaround it by disabling lld when ptest feature is on. Fixes errors like note: riscv64-yoe-linux-ld.lld: error: undefined symbol: PyExc_ValueError\nreferenced by bcrypt_rust.a93ef5fbf090e743-cgu.0 Signed-off-by: Khem Raj <raj.khem@gmail.com>
* clang: Package docs related to clang-doc toolKhem Raj2024-06-281-0/+1
| | | | | | | | | | | Fixes ERROR: clang-19.0.0-r0 do_package: QA Issue: clang: Files/directories were installed but not shipped in any package: /usr/share/clang-doc /usr/share/clang-doc/clang-doc-default-stylesheet.css /usr/share/clang-doc/index.js Signed-off-by: Khem Raj <raj.khem@gmail.com>
* clang: remove True option to getVar callsPeter Marko2024-06-261-2/+2
| | | | | | | Layer cleanup similar to https://git.openembedded.org/openembedded-core/commit/?id=26c74fd10614582e177437608908eb43688ab510 Signed-off-by: Peter Marko <peter.marko@siemens.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-05-13 00:36:48 +0000