Remove unsupported '-mcpu=octeontx2+crypto' from BINDGEN_EXTRA_CLANG_ARGS
as clang does not recognize 'octeontx2' as a valid target CPU, causing
bindgen to fail when generating Rust bindings.
Since bindgen only parses headers using Clang, CPU-specific options
like -mcpu are generally unnecessary.
Fixes build failure:
| error: unsupported argument 'octeontx2+crypto' to option '-mcpu='
| error: unknown target CPU 'octeontx2'
Signed-off-by: Bo Sun <bo.sun.cn@windriver.com>
Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com>
Rustix crate needs libc crate to be patched
Fix build on 32-bit hosts without 64bit atomics
Use portable-atomic crate for 64bit atomics, helps 32bit arches without
64bit atomic intrinsics.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Changelog:
===========
- fix checkpatch warnings
- Use the right dev_t decoding for diskerror handler
- Add new modules supported by HiSilicon common section
- Fix some static check warning
- Fix few compilation warnings in non standard hisilicon code
- Fix some compilation alarms in ras-record.h.
- ras-mc-ctl: Update logging of CXL memory module data to align with CXL spec rev 3.1
- ras-mc-ctl: Update logging of CXL DRAM event data to align with CXL spec rev 3.1
- ras-mc-ctl: Update logging of CXL general media event data to align with CXL spec rev 3.1
- ras-mc-ctl: Update logging of common event data to align with CXL spec rev 3.1
- ras-mc-ctl: Fix logging of memory event type in CXL DRAM error table
- cxl: Update memory module event to CXL spec rev 3.1
- cxl: Update CXL DRAM event to CXL spec rev 3.1
- cxl: Update CXL general media event to CXL spec rev 3.1
- cxl: Add Component Identifier formatting for CXL spec rev 3.1
- cxl: Update common event to CXL spec rev 3.1
- cxl: Add automatic indexing for storing CXL fields in SQLite database
- cxl: Fix mismatch in region field's name with kernel DRAM trace event
- cxl: Fix logging of memory event type of DRAM trace event
- Fix for parsing error when trace event's format file is larger than PAGE_SIZE
- Add page offline support for cxl memory
- for ASRock X370 Taichi
- for ASRock X570 Creator
- for ASRock X570S PG Riptide
- mce: decode io port for bus error
- arm: do not print error msg if field not found
- add DE error type for AMD
- Fix the display format of JaguarMicro vendor no standard errors
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Since commit e19b4c9755fd ("thin-provisioning-tools: 1.0.13 -> 1.0.14"),
thin-provisioning-tools is in the clang dynamic layer.
This triggers warnings on AB:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/82/builds/213/steps/12/logs/warnings
So, move the thin-provisioning-tools packagegroup inclusion to the clang
dynamic layer.
Signed-off-by: Yoann Congal <yoann.congal@smile.fr>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
* hardcoding:
${WORKDIR}/recipe-sysroot-native${libdir}
is just wrong when there is a better variable
* This path won't be correct for multilib builds where target ${libdir}
might be e.g. /usr/lib32 while native libdir is /usr/lib.
* use STAGING_LIBDIR_NATIVE variable which uses correct ${libdir_native}
* fixes:
error: failed to run custom build command for `devicemapper-sys v0.3.0`
Caused by:
process didn't exit successfully: `lib32-thin-provisioning-tools/1.1.0/build/target/release/build/devicemapper-sys-88de590bc55acb43/build-script-build` (exit status: 101)
--- stderr
thread 'main' panicked at lib32-thin-provisioning-tools/1.1.0/sources-unpack/cargo_home/bitbake/bindgen-0.69.4/lib.rs:622:31:
Unable to find libclang: "couldn't find any valid shared libraries matching: ['libclang.so', 'libclang-*.so', 'libclang.so.*', 'libclang-*.so.*'], set the `LIBCLANG_PATH` environment variable to a path where one of these files can be found (invalid: [])"
Signed-off-by: Martin Jansa <martin.jansa@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
BUILD_CFLAGS doesn't contain information about the recipe sysroot nor about the target
system - and in case these are not specified for bindgen, then it builds against
the build system's headers, using the build system's arch.
Instead of BUILD_CFLAGS pass HOST_CC_ARCH and TOOLCHAIN_OPTIONS, which contain the sysroot
and the requred cross-compiling flags, beside passing the target flag also.
Fixes the following do_compile error:
| /usr/include/linux/types.h:5:10: fatal error: 'asm/types.h' file not found
| thread 'main' panicked at /yocto/sandbox/build/tmp/work/cortexa72-poky-linux/thin-provisioning-tools/1.1.0/sources-unpack/cargo_home/bitbake/devicemapper-sys-0.3.0/build.rs:24:10:
| Could not generate dm.h bindings: ClangDiagnostic("/usr/include/linux/types.h:5:10: fatal error: 'asm/types.h' file not found\n")
Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
* License-Update: Update links in GPLv3 (http -> https)
* It need depend on pkg-config, udev and clang-native to build
* Move it to dynamic-layers since now it depends on meta-clang.
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The android-tools recipe has been using gold linker to create
executables. Recently OE-Core has dropped support for the gold linker,
which is now causing build errors for the android-tools recipe. Update
the build-system patch in order to stop using gold for linking.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The android-tools's build in several places adds system locations (like
/usr/include/android) to the include path. Extend the OE-specific build
patch to fix those errors.
This fixes errors like:
error: include location "/usr/include/android" is unsafe for cross-compilation.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
This reverts commits 4271cc28279b ("android-tools: Add flag to enable
adbd service (#147)") and b85ae59968f4 ("android-tools 10: Add flag to
enable adbd service"). These two commits added optional
ROOTFS_POSTPROCESS_COMMAND touching the flag file, however this variable
doesn't make any sense in the package recipe, it is only concerned in
the image context.
Drop useless code from the android-tools recipe.
Fixes: 4271cc28279b ("android-tools: Add flag to enable adbd service (#147)")
Fixes: b85ae59968f4 ("android-tools 10: Add flag to enable adbd service")
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Recipes are much more readable with whitespace around the assignment operators.
Fix various assignments in meta-openembedded recipes to show this is definitely
the preferred formatting.
This fixes recipes with larger numbers of issues but there are just under 100
other references left to fix.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Changelog:
=============
- fix common misspellings from codespell project
- nvmetcli: set up the target only after the network is configured
- nvmetcli: fixup ana groupid setting for namespaces
- Documentation: fix typo
- nvmetcli: add a tcp example json
- nvmetcli: Correct xrange usage for py3
- nvmetcli: Allow different devices for make test
- nvmetcli: Report save name correctly
- test_nvmet.py: test_invalid_input fails for py3
- nvme.py: Make modprobe work for kmod lib too
- nvme.py: Sync the containing directory
- nvme.py: Explicit close is redundant
- nvmetcli: Improve IOError handling on restore
- README: Update URL for configshell-fb
- nvmetcli: don't remove ANA Group 1 on clear
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Changelog:
==========
- Fix memory not released on error return from pb_decode_ex()
- Fix deprecated MakeClass() call in generator
- Fix compiler error with enums and --c-style
- Fix version conflict with bazel build rules
Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Fixes errors like
| koishi| Checking for function "getcontext" : NO (cached)
| koishi| Checking for function "setcontext" : NO
| koishi| Checking for function "makecontext" : NO (cached)
| koishi| Checking for function "swapcontext" : NO (cached)
| koishi| Message: ** Backend `ucontext_sjlj` is not supported
|
| ../git/subprojects/koishi/src/meson.build:43:4: ERROR: Problem encountered: Unsupported platform
Signed-off-by: Khem Raj <raj.khem@gmail.com>
ChangeLog:
https://github.com/canonical/netplan/releases/tag/1.1
* Drop the following patches as the issues have been fixed upstream:
0001-meson.build-drop-unnecessary-build-dependencies.patch
0001-networkd.c-define-scope-specific-to-case-statement.patch
* Set build option -Dtesting=false to skip testing.
Signed-off-by: Yi Zhao <yi.zhao@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The patches by Raghuvarya changed the location of the file that systemd
uses to check whether to start the adbd or not. However those patches
completely ignored creating those two flag files, as done by the
android-tools recipes.
Make the android-tools create the /etc/usb-debugging-enabled file so
that it's possible to enable the adbd automatically.
Fixes: a29c6386d576 ("android-toold-adbd: Fix inconsistency between selinux configurations")
Fixes: 8106cfe769aa ("android-tools-adbd.service: Change /var to /etc in ConditionPathExists")
Cc: Raghuvarya S <quic_raghuvar@quicinc.com>
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
ConditionPathExists is set to /etc/usb-debugging-enabled as part of meta-oe/recipes-devtools/android-tools/android-tools/android-tools-adbd.service file. However, in meta-oe/dynamic-layers/selinux/recipes-devtool/android-tools/android-tools/android-tools-adbd.service file ConditionPathExists is set to /var/usb-debugging-enabled
This causes an internal inconsistency between selinux-enabled and -disabled configurations.
Hence, change ConditionPathExists=/var/usb-debugging-enabled to ConditionPathExists=/etc/usb-debugging-enabled
Reported-by: @lumag
The json module is used in several cli commands.
The fcntl module is used in terminal input handling.
Signed-off-by: Esben Haabendal <esben@geanix.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The android-tools package doesn't include the systemd units. Instead
adbd unit is a part of the android-tools-adbd package. Set the
SYSTEMD_PACKAGES variable accordingly.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Fix the warning by pointing S to ${WORKDIR}/sources and UNPACKDIR to ${S}. Since recent UNPACKDIR work, default S directory is not created anymore. By setting UNPACKDIR to S, S in indirectly created in do_unpack.
Signed-off-by: alperak <alperyasinak1@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
android-tools-configfs doesn't have any checked out source files, which
results in a warning regarding S not existing. Fix the warning by
pointing S to ${WORKDIR}/sources and UNPACKDIR to ${S}.
Fix the warning for the selinux-enabled recipe.
The warning text:
WARNING: android-tools-conf-configfs-1.0-r0 do_unpack:
android-tools-conf-configfs: the directory ${WORKDIR}/${BP} (<scrubbed>)
pointed to by the S variable doesn't exist - please set S within the
recipe to point to where the source has been unpacked to
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
With the intruction of the UNPACKDIR the remount script is placed in the
UNPACKDIR and not in S.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
libstdc++ in GCC 14 has dropped several nested includes. Include the
<algorithms> header to fix build error:
system/core/fs_mgr/liblp/utility.cpp: In function 'bool android::fs_mgr::UpdateMetadataForInPlaceSnapshot(LpMetadata*, uint32_t, uint32_t)':
system/core/fs_mgr/liblp/utility.cpp:264:28: error: no matching function for call to 'find(std::vector<LpMetadataPartitionGroup*>::iterator, std::vector<LpMetadataPartitionGroup*>::iterator, __gnu_cxx::__alloc_traits<std::allocator<LpMetadataPartitionGroup>, LpMetadataPartitionGroup>::value_type*)'
264 | auto it = std::find(new_group_ptrs.begin(), new_group_ptrs.end(),
| ~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
265 | &metadata->groups[partition.group_index]);
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Replace references of WORKDIR with UNPACKDIR where it makes sense to do
so in preparation for changing the default value of UNPACKDIR.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The following paths have been replaced with PYTHON_SITEPACKAGES_DIR:
- "${libdir}/${PYTHON_DIR}/site-packages"
- "${libdir}/python${PYTHON_BASEVERSION}/site-packages"
- "${libdir}/python*/site-packages"
- "${libdir}/python3.*/site-packages"
Signed-off-by: alperak <alperyasinak1@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
