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 ( https://github.com/koutheir/selinux-sys/commit/a6667c404ecc33266f66e9516bb8e30150c41ec2 ) 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: https://github.com/koutheir/selinux-sys/commit/d3ea4674e18c5240918348bea4ec6248e50516e5 , 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>
* use STAGING_LIBDIR_NATIVE variable for LIBCLANG_PATH and SELINUX_LIB_DIR
and STAGING_INCDIR_NATIVE variable for SELINUX_INCLUDE_DIR
not sure why it uses native version and not target, but at least use
correct variable
* 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.
* even with meta-selinux added to my builds I don't see any failure
maybe these variables aren't really used?
* use STAGING_LIBDIR_NATIVE variable which uses correct ${libdir_native}
OE qemuarm64-multilib@ /OE/build/oe-core $ bitbake-getvar LIBCLANG_PATH -r uutils-coreutils
#
# $LIBCLANG_PATH [2 operations]
# exported /OE/build/oe-core/meta-openembedded/meta-oe/recipes-core/uutils-coreutils/uutils-coreutils_0.0.29.bb:33
# [export] "1"
# set /OE/build/oe-core/meta-openembedded/meta-oe/recipes-core/uutils-coreutils/uutils-coreutils_0.0.29.bb:33
# "${WORKDIR}/recipe-sysroot-native${libdir}"
# pre-expansion value:
# "${WORKDIR}/recipe-sysroot-native${libdir}"
export LIBCLANG_PATH="/OE/build/oe-core/tmp/work/cortexa57-oe-linux/uutils-coreutils/0.0.29/recipe-sysroot-native/usr/lib64"
OE qemuarm64-multilib@ /OE/build/oe-core $ bitbake-getvar STAGING_LIBDIR_NATIVE -r uutils-coreutils
#
# $STAGING_LIBDIR_NATIVE
# set /OE/build/oe-core/openembedded-core/meta/conf/bitbake.conf:425
# "${STAGING_DIR_NATIVE}${libdir_native}"
STAGING_LIBDIR_NATIVE="/OE/build/oe-core/tmp/work/cortexa57-oe-linux/uutils-coreutils/0.0.29/recipe-sysroot-native/usr/lib"
OE qemuarm64-multilib@ /OE/build/oe-core $ bitbake-getvar LIBCLANG_PATH -r lib32-uutils-coreutils
#
# $LIBCLANG_PATH [2 operations]
# exported /OE/build/oe-core/meta-openembedded/meta-oe/recipes-core/uutils-coreutils/uutils-coreutils_0.0.29.bb:33
# [export] "1"
# set /OE/build/oe-core/meta-openembedded/meta-oe/recipes-core/uutils-coreutils/uutils-coreutils_0.0.29.bb:33
# "${WORKDIR}/recipe-sysroot-native${libdir}"
# pre-expansion value:
# "${WORKDIR}/recipe-sysroot-native${libdir}"
export LIBCLANG_PATH="/OE/build/oe-core/tmp/work/armv7at2-neon-oemllib32-linux-gnueabi/lib32-uutils-coreutils/0.0.29/recipe-sysroot-native/usr/lib32"
OE qemuarm64-multilib@ /OE/build/oe-core $ bitbake-getvar STAGING_LIBDIR_NATIVE -r lib32-uutils-coreutils
#
# $STAGING_LIBDIR_NATIVE
# set /OE/build/oe-core/openembedded-core/meta/conf/bitbake.conf:425
# "${STAGING_DIR_NATIVE}${libdir_native}"
STAGING_LIBDIR_NATIVE="/OE/build/oe-core/tmp/work/armv7at2-neon-oemllib32-linux-gnueabi/lib32-uutils-coreutils/0.0.29/recipe-sysroot-native/usr/lib"
Signed-off-by: Martin Jansa <martin.jansa@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
As of right now there are no applications available for benchmarking
OpenCL. Clpeak is a simple synthetic benchmark for OpenCL that is
designed to determine the peak capabilities of OpenCL devices.
It's currently one of the more popular CL benchmarks supported by
OpenBenchmarking.org and licensed Apache-2.0.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Iksemel is a XML parser library that was designed for Jabber applications,
but it has no users and hasn't been maintained for 14 years.
Signed-off-by: Ross Burton <ross.burton@arm.com>
Setting `--kernel-command-line` in systemd service is unmodifiable
from the bootloader kernel parameters.
`splash` together with `plymouth.ignore-serial-consoles` should be
added by the user to e.g. bootloader configuration file instead.
Signed-off-by: Piotr Łobacz <p.lobacz@welotec.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
This recipe provides the opecl-cts suite. This is a pre-release version
v2024-08-08, which I have tested to work with opencl-headers version v2024.05.08
. The pre-release version was picked due to incompatibility issues with other
versions of headers.
Add a patch to add an option to disable warning as error
Signed-off-by: Antonios Christidis <a-christidis@ti.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
In case "asciidoctor" meson option is enabled for building
the documentation, meson looks for a binary called "asciidoctor",
which is a ruby application, different from "asciidoc", and fails
with the following error:
../git/meson.build:153:15: ERROR: Program 'asciidoctor' not found or not executable
When "asciidoctor" option is disabled, meson looks for "asciidoc",
which is readily provided by asciidoc-native. When docs PACKAGECONFIG
is disabled, the "asciidoctor" option can be left on its default value.
Also, add xmlto-native as a dependency for the "docs" PACKAGECONFIG,
otherwise build fails with the following error after finding asciidoc:
../git/meson.build:156:12: ERROR: Program 'xmlto' not found or not executable
Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
In case "tests" PACKAGECONFIG is not included, do_configure fails
with the following error message:
../git/ndctl/meson.build:51:4: ERROR: Problem encountered: '-D=destructive=enabled' requires '-Dtest=enabled'
Since "destructive" option only enables an extra set of tests, it only
makes sense to use along with including the tests. In case tests
are not required, this option can be left on its default value (disabled).
Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
This will remove false-positive CVE-2024-50655 from reports.
There are different emlog components from other vendors around.
Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Everyone should be using x11-common now (in oe-core) and this recipe
hasn't been touched since 2018, so remove it.
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
This recipe has been added to openembedded-core layer, since hwdata is
now a requirement to build libdisplay-info, used by weston (see commit
3e5d5ba74bea "hwdata: add recipe from meta-openembedded" from oe-core).
Therefore, drop this recipe.
Signed-off-by: Hiago De Franco <hiago.franco@toradex.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Khem Raj
Thomas Noack
Niko Mauno
Peter Kjellerstedt
Etienne Cordonnier
Dmitry Baryshkov
Changqing Li
Martin Jansa
Mingli Yu
Richard Purdie
Yoann Congal
Randolph Sapp
Ross Burton
Piotr Łobacz
Antonios Christidis
Gyorgy Sarvari
Wang Mingyu
Peter Marko
Hongxu Jia
Markus Volk
Hiago De Franco
J. S.