See https://github.com/uutils/coreutils/releases/tag/0.2.0
- re-add stdbuf now that cross-compiling has been fixed ( see b5d4b0ee1d )
- enable compilation of libstdbuf.so as external library (instead of embedding it into stdbuf and writing it to /tmp during runtime)
- remove export of PROJECT_NAME_FOR_VERSION_STRING now that the variable has been removed
Signed-off-by: Etienne Cordonnier <ecordonnier@snap.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Specify -native versions of dependencies. These were satisfied
transitively through other dependencies, but we should specify
them explicitly. It also removes dependencies on the target
system for a native recipe.
Signed-off-by: Dan McGregor <dan.mcgregor@usask.ca>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Synchronize with OpenCL v3.0.19 specification release.
Also patch OpenCL CTS in order to prevent its breakage with the updated
headers.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
This project is abandoned and does not exist on
https://01.org/ anymore, a mirror is found on
github.com/intel but its marked archived and unmaintained
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Remove the konkretcmpi recipe, as the upstream has been inactive for over 8 years.
No new releases, bug fixes or security updates.
Signed-off-by: Alper Ak <alperyasinak1@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Remove the properties-cpp recipe, as the upstream has been inactive for over 10 years.
No new releases, bug fixes or security updates are expected.
Signed-off-by: Alper Ak <alperyasinak1@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The network access during compile task has been resolved now.
Change-Id: Id7a8510ae1095a2430d26015bdd6cc54b633781f
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Changelog:
===========
- Use _aligned_malloc in Windows/MSVC builds
- Add option to force number of iteration per kernel
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Add a recipe to build systemd-repart-native.
The chosen version is a relatively recent one, to support:
1) PKCS#11 uris [1] to pass in the private key when creating a
discoverable disk image (as·--private-key-source).
2) setting Compression=/CompressionLevel= in the configuration [2],
which is then passed over to a (recent version of) mkfs.erofs
The recipe was adapted from an incomplete 'systemd-tools' patch [3]
that is floating upstream.
Link: [1]: 0a8264080a
Link: [2]: 27cacec939
Link: [3]: https://lists.openembedded.org/g/openembedded-core/topic/108223984#msg204065
Signed-off-by: Johannes Schneider <johannes.schneider@leica-geosystems.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Please see
https://git.yoctoproject.org/poky/commit/?id=4dd321f8b83afecd962393101b2a6861275b5265
for what changes are needed, and sed commands that can be used to make them en masse.
I've verified that bitbake -c patch world works with these, but did not run a world
build; the majority of recipes shouldn't need further fixups, but if there are
some that still fall out, they can be fixed in followups.
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Latest layer compatibility checks have been enhanced to check for
network access during non-fetch tasks and flag it as failure, which
is now happening for these recipes since it calls go module fetcher
during do_compile
Latest gomod fetcher has got improvements and can be used for these
recipes but it needs some work. Skip them until it is fixed
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The user should now be able to choose the preferred runtime D-Bus
implementation with VIRTUAL-RUNTIME_dbus variable. In order to avoid
situation where both Freedesktop.org's dbus and dbus-broker are pulled
into the same root filesystem, add conflict declaration which will help
to detect the problem already during the Yocto build.
Signed-off-by: Niko Mauno <niko.mauno@vaisala.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The new VIRTUAL-RUNTIME_dbus in oe-core can now be used to select the
preferred runtime D-Bus implementation, such as dbus-broker, so refer
to the variable instead.
Signed-off-by: Niko Mauno <niko.mauno@vaisala.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
In order to facilitate using e.g. dbus-broker as runtime D-Bus
implementation, change the Freedesktop.org specific D-Bus runtime
dependency declaration to honor oe-core's new VIRTUAL-RUNTIME_dbus
variable.
Signed-off-by: Niko Mauno <niko.mauno@vaisala.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
In order to facilitate using e.g. dbus-broker as runtime D-Bus
implementation, change the Freedesktop.org specific D-Bus runtime
dependency to honor oe-core's new VIRTUAL-RUNTIME_dbus variable.
Furthermore mark the runtime dependency as target specific, which
avoids unbuildable dependency chain issue when bitbaking native or
nativesdk variant of the recipe, when dbus-broker is preferred.
Signed-off-by: Niko Mauno <niko.mauno@vaisala.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Since it is already declared in DEPENDS the build system will add the
libsigc++-3 runtime dependency automatically, therefore we can leave
out the redundant declaration.
Signed-off-by: Niko Mauno <niko.mauno@vaisala.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The build time dependency seems to be particular to the 'tools'
PACKAGECONFIG option, so update the recipe in this respect to
reflect the state of affairs more accurately.
Signed-off-by: Niko Mauno <niko.mauno@vaisala.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Latest OpenCL CTS is released after the latest OpenCL Headers and uses a
symbol which is not defined in the release. Backport a patch to make
OpenCL CTS compile.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Upgrade OpenCL-Headers to the latest release. Upgrade opencl-clhpp with
the same commit so that they stay in sync, otherwise projects using
clhpp might fail to build.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Remove this not maintained recipe. The latest commit of pmtools is 12
years ago. And it generates 3 binaries: acpidump/acpixtract/madt, but
there is a recipe acpica in oe-core provides acpidump/acpixtract, and
according to README.madt, it is hacked out from Linux kernel, if someone
requests it, mayb user can add one recipe similar like turbostat.
[1] https://github.com/anyc/pmtools/tree/master
Signed-off-by: Changqing Li <changqing.li@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Fixes:
Error: Transaction test error:
file /usr/bin/minizip conflicts between attempted installs of minizip-1.3.1-r0.riscv64 and minizip-ng-4.0.8-r0.riscv64
file /usr/lib/libminizip.so.1 conflicts between attempted installs of minizip-1.3.1-r0.riscv64 and minizip-ng-4.0.8-r0.riscv64
Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
minizip-ng is a zip manipulation library written in C that is supported
on Windows, macOS, and Linux.
minizip-ng has new features and bug fixes compared to the original library
minizip [1] which had not been maintained for a long period of time.
[1] https://github.com/madler/zlib/tree/master/contrib/minizip
Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
This installs cmake and pkgconfig files so that other recipes can find
the header files.
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
There is a bug in uutils-coreutils causing stdbuf to include the HOST version of libstdbuf.so, even when cross-compiled.
As a side-effect, the uutils-coreutils binary was containing the buildpath, because RPATH was set on libstdbuf.so.
Thus the buildpath error can be re-enabled.
This is tracked upstream by https://github.com/uutils/coreutils/issues/6591
Signed-off-by: Etienne Cordonnier <ecordonnier@snap.com>
Co-authored-by: Gyorgy Sarvari <skandigraun@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
* don't seem to be needed, I don't see any failures or changes after removing them
* they were needed before in older version as explained by Etienne in:
https://lists.openembedded.org/g/openembedded-devel/message/115756
regarding SELINUX_INCLUDE_DIR, it was definitely needed as I implemented the recipe. During implementation I submitted this patch to selinux-sys ( a6667c404e ) to correctly use this variable, and was getting a build error without this fix because the rust crate selinux-sys was not finding the selinux header-file (specifically, the bindgen tool).
However, this was in 2022, and since then there has been this patch in selinux-sys: d3ea4674e1 , and it seems that the variable is not needed any more.
At least I'm not able to reproduce the build error which I was getting, even with commenting out SELINUX_LIB_DIR and SELINUX_INCLUDE_DIR.
The header-file is used for generating rust code from the C header-file using bindgen, so I don't think it makes a difference whether the native version or the target version is used.
This is the old build error I was getting:
process didn't exit successfully: `/workdir/build/tmp-glibc/work/armv8a-linux/uutils-coreutils/0.0.14.AUTOINC+43a5b8c7d7-r0/build/target/release/build/selinux-sys-0849198bc1fef4a4/build-script-build` (exit status: 101)
--- stdout
cargo:root=/workdir/build/tmp-glibc/work/armv8a-linux/uutils-coreutils/0.0.14.AUTOINC+43a5b8c7d7-r0/build/target/aarch64-snap-linux/release/build/selinux-sys-d96748d49908959f/out
cargo:rerun-if-env-changed=SELINUX_STATIC_aarch64-snap-linux
cargo:rerun-if-env-changed=SELINUX_STATIC_aarch64_snap_linux
cargo:rerun-if-env-changed=TARGET_SELINUX_STATIC
| --- stderr
| src/selinux-sys.h:1:10: fatal error: 'selinux/selinux.h' file not found
| src/selinux-sys.h:1:10: fatal error: 'selinux/selinux.h' file not found, err: true
Signed-off-by: Martin Jansa <martin.jansa@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
