srecord/input/file/hp64k.h:82:21: error: ‘uint16_t’ has not been declared
82 | bool read_u16be(uint16_t *dest);
| ^~~~~~~~
/home/abuild/rpmbuild/BUILD/srecord-1.65.0-build/srecord-1.65.0-Source/./srecord/input/file/hp64k.h:1:1: note: ‘uint16_t’ is defined in header ‘<cstdint>’; this is probably fixable by adding ‘#include <cstdint>’
+++ |+#include <cstdint>
1 | //
make[2]: *** [srecord/CMakeFiles/lib_srecord.dir/build.make:222: srecord/CMakeFiles/lib_srecord.dir/arglex/tool/input.cc.o] Error 1
* From gcc 13, cstdint header must be explicitly included for uint_X data types.
* See also: https://gcc.gnu.org/gcc-13/porting_to.html#header-dep-changes
Signed-off-by: mark.yang <mark.yang@lge.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
meta-gnome does not currently depend on meta-multimedia.
When "commercial" is in LICENSE_FLAGS_ACCEPTED, gimp depends on libheif
by default but libheif is in meta-multimedia. That leads to build
failures, for example, in the reproducible-meta-oe AB build[0].
To fix this, remove the default "heif" PACKAGECONFIG.
To enable heif support in gimp, users can add "commercial" in
LICENSE_FLAGS_ACCEPTED and add meta-multimedia to their build.
[0]: https://autobuilder.yoctoproject.org/valkyrie/#/builders/87/builds/39/steps/16/logs/stdio
Signed-off-by: Yoann Congal <yoann.congal@smile.fr>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Fixes
| error[E0425]: cannot find function `getrandom` in crate `libc`
| --> /usr/src/debug/deqp-runner/0.20.3/sources-unpack/cargo_home/bitbake/getrandom-0.3.2/src/backends/getrandom.rs:29:15
| |
| 29 | libc::getrandom(buf.as_mut_ptr().cast(), buf.len(), 0)
| | ^^^^^^^^^ not found in `libc`
|
| Building [===============> ] 77/121: thiserror-impl, indexmap,...
| Building [===============> ] 78/121: thiserror-impl, indexmap,...
| For more information about this error, try `rustc --explain E0425`.
| error: could not compile `getrandom` (lib) due to 1 previous error
|
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Update dependency on tempfile crate to 3.x so it can
pick 3.19 which brings latest rustix and latest libc
which has support for riscv32 + 1 patch which is submitted
Signed-off-by: Khem Raj <raj.khem@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>
Since this file is downloaded and upstream does not version it on changes
we have to ensure that we store the versions in DL_DIR and also ensure they
do not step on each other
Fixes
stdio: WARNING: unicode-ucd-14.0.0-r0 do_fetch: Checksum mismatch for local file /srv/autobuilder/valkyrie.yocto.io/current_sources/license.txt
stdio: WARNING: unicode-ucd-14.0.0-r0 do_fetch: Renaming /srv/autobuilder/valkyrie.yocto.io/current_sources/license.txt to /srv/autobuilder/valkyrie.yocto.io/current_sources/license.txt_bad-checksum_f7830d126f59d83842565d3dddedc79db4ca978ed52aee0ebcc040ea76a85519
Signed-off-by: Khem Raj <raj.khem@gmail.com>
This is downloaded and does not have version, so we have to
update it whenever upstream update it. The copyright year
is changed this time.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
This avoids warnings like:
ld: warning: NE10_physics.neon.s.o: missing .note.GNU-stack section
implies executable stack
ld: NOTE: This behaviour is deprecated and will be removed in a future
version of the linker
With glibc 2.41, the need for an executable stack lead to errors like
this in runtime:
[ ERR ] foo@0[984]: [setup-script: /usr/share/foo/foo.enc] sol:
runtime error: libNE10.so.10: cannot enable executable stack as shared
object requires: Invalid argument
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Migration to Fastcv static lib for Fastcv Extns and
adding fastcv enablement option as packageconfig.
Signed-off-by: Pulkit Singh Tak <quic_ptak@quicinc.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Backport patch to fix issue: https://errors.yoctoproject.org/Errors/Details/850167/
TOPDIR/tmp/work/core2-64-oe-linux/thrift/0.21.0/thrift-0.21.0/lib/cpp/src/thrift/concurrency/Mutex.h:47:26: error: 'int64_t' has not been declared
47 | virtual bool timedlock(int64_t milliseconds) const;
| ^~~~~~~
TOPDIR/tmp/work/core2-64-oe-linux/thrift/0.21.0/thrift-0.21.0/lib/cpp/src/thrift/concurrency/Mutex.h:25:1: note: 'int64_t' is defined in header '<cstdint>'; this is probably fixable by adding '#include <cstdint>'
24 | #include <thrift/TNonCopyable.h>
+++ |+#include <cstdint>
Signed-off-by: Nguyen Dat Tho <tho3.nguyen@lge.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Add a mechanism to check mismatch between runtime version and build time version.
To use, add the following line to local.conf:
include conf/version-check.conf
Ideally, layers will have their own conf/version-check.conf to establish
some baseline, so that any future warning indicates some error. In such
case, users can use include_all:
include_all conf/version-check.conf
The basic idea is to use qemu to run executables at build time, extract
possible versions, and check if there's a mismatch found.
Python meta data and .pc files are also checked for quick match. This
is because such info are also easy to be checked by users.
check-version-mismatch.bbclass is the class that does the actual work.
A new variable, CHECK_VERSION_PV, is introduced. It defaults to ${PKGV},
but also allows override. This allows us to handle special cases in each
layer.
version-check.conf is the configuration file that makes this functionality
easier to use and draws some baseline. It contains some override settings
for some recipes. With these overrides, all recipes in oe-core are handled
well. All warnings are valid warnings.
Note that 'ps' is added to HOSTTOOLS in version-check.conf. This is because
we need 'ps' to find stale processes and then clean them.
The warnings are like below:
WARNING: time-1.9-r0 do_package_check_version_mismatch: Possible runtime versions ['UNKNOWN'] do not match recipe version 1.9
WARNING: python3-unittest-automake-output-0.2-r0 do_package_check_version_mismatch: Possible runtime versions ['0.1'] do not match recipe version 0.2
WARNING: pinentry-1.3.1-r0 do_package_check_version_mismatch: Possible runtime versions ['1.3.1-unknown'] do not match recipe version 1.3.1
...
There will be a data directory containing all details: tmp/check-version-mismatch.
This directory contains detailed data for each recipe that is built.
If users don't want it, they can set DEBUG_VERSION_MISMATCH_CHECK to 0.
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
