These are test images to build all recipes in layer. Renaming them makes
them refect what they are. Moreover we can rename the ptest images to
match OE-Core naming conventions for meta-oe/meta-perl/meta-python
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit 0cb0180594)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
These were essentially duplicates of core-image-minimal, however
core-image-base is a better baseline for upper layers, so switched the
consumers of these images to use core-image-base
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit e88b777cbe)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
We really do not need to define base images which already exist in core
layer, reuse them here.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit ef9d73fced)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
This reverts commit a0557fe543.
As said by Ross[Ø]:
"Putting the _target_ protoc into the sysroot for executation at _build_
time isn't useful because even if it has the right architecture, the
tune might be incompatible. Recipes which want protoc should just depend
on protobuf-native."
This has been reverted recently by Samuli[1]:
"If protoc is enabled for the build, recipes using protobuf will
fail when protoc is not available in the recipe sysroot"
Be the revert is incorret as This is an issue coming from qtgrpc
other recipes that use protobuf or gRPC compiler, proplery looks for
the binary in the correct sysroot folder.
Qtgrpc recipe should fix this issue at the recipe level, for example this
is what I've done for "etcd-cpp-apiv3" recipe[2] that doesn't need this
patch to properly compile.
So keeping this hack doesn't seems to be a correct fix.
Note that qtgrpc recipe isn't available on meta-oe nor any other public
layers.
0: https://patchwork.yoctoproject.org/project/oe/patch/20230904161230.377450-1-ross.burton@arm.com/
1: https://patchwork.yoctoproject.org/project/oe/patch/20230927051101.3088498-1-samuli.piippo@qt.io/
2: 47f0d9e032
CC: Samuli Piippo <samuli.piippo@gmail.com>
CC: Ross Burton <ross.burton@arm.com>
Signed-off-by: Clément Péron <peron.clem@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit bfb626a230)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
This bolt product does not currently have an entry in the CVE database.
However, the default cve-check logic that maps recipes to products in
the CVE database is incorrectly matching this package to a different
bolt product made by bolt-cms. As a result, CVE checking incorrectly
reports CVEs for that product for this package.
Signed-off-by: Jeffrey Pautler <jeffrey.pautler@ni.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit c1ea15792b)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Support --with-http_xslt_module configure option via a PACKAGECONFIG
option. The option is not added to the defaults.
Signed-off-by: Joe Slater <joe.slater@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit e0ac8eec48)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
The graphviz configure script used $prefix/include and $prefix/lib search
directories, thus bypassing the recipe sysroot, which could lead to build
contamination or failures. The added patch (backported from graphviz 9.0.0)
fixes this.
Due to the $prefix != /usr check in the configure script, this issue only
showed up for recipe build variants which use a different prefix value,
such as nativesdk-graphviz (prefix = SDKPATHNATIVE/...) or graphviz-native
(prefix = STAGING_DIR_NATIVE/...). Using STAGING_DIR_NATIVE is probably not
a problem, since it is recipe-specific anyways, but using SDKPATHNATIVE
may be a problem, if it happens to exist and contains headers/libraries.
Even though this may be unlikely with the default SDKPATH =
"/usr/local/oe-sdk-hardcoded-buildpath" value used in bitbake.conf,
the problem can still be triggered, especially if the paths like prefix
or SDKPATH are customized in a build.
Link: https://gitlab.com/graphviz/graphviz/-/issues/2442
Signed-off-by: Daniel Klauer <daniel.klauer@gin.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit 883860c40c)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Changelog:
=========
This release contains two security related fixes. One each for VP8 and
VP9.
- Upgrading:
This release is ABI compatible with the previous release.
- Bug fixes:
https://crbug.com/1486441 (CVE-2023-5217)
Fix to a crash related to VP9 encoding (#1642)
Signed-off-by: Benjamin Bara <benjamin.bara@skidata.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit 06faef7244)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Fixes
AssertionError:-
ptests which had no test results:
['minicoredumper']
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit 7ddce19779)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
The recipe currently indicates that the cukinia package is licensed
under both GPLv3 AND Apache 2.0 licenses, but the upstream specifies
using it under GPLv3 OR Apache 2.0 license, is user's choice.
Signed-off-by: Philip-Dylan Gleonec <philip-dylan.gleonec@savoirfairelinux.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit cb8908b91e)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Improvements:
xml_attribute::set_name and xml_node::set_name now have overloads that accept pointer to non-null-terminated string and size
Implement parse_merge_pcdata parsing mode in which PCDATA contents is merged into a single node when original document had comments that were skipped during parsing
xml_document::load_file now returns a more consistent error status when given a path to a folder
Bug fixes:
Fix assertion in XPath number→string conversion when using non-English locales
Fix PUGIXML_STATIC_CRT CMake option to correctly select static CRT when using MSVC and recent CMake
Compatibility improvements:
Fix GCC 2.95/3.3 builds
Fix CMake 3.27 deprecation warnings
Fix XCode 14 sprintf deprecation warning when compiling in C++03 mode
Fix clang/gcc warnings -Wweak-vtables, -Wreserved-macro-identifier
Thanks to @DavidKorczynski, @jiangqucheng, @SoapGentoo, @asmaloney, @ArchXUser, @stefanroellin and @vineethkuttan for contributions!
- license checksum has changed because of copyright year
Signed-off-by: Markus Volk <f_l_k@t-online.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit 4b59083f4c)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
The signature recalculation task can fail:
```
/.../build/tmp/work/armv8a-poky-linux/libcamera/1_0.0.4-r0/temp/run.do_recalculate_ipa_signatures_package.937421: line 154: /.../build/tmp/work/armv8a-poky-linux/libcamera/1_0.0.4-r0/git/src/ipa/ipa-sign-install.sh: No such file or directory
```
This happens whenever ${S} is removed and packages are retrieved from
sstate cache.
Instead of trying to fix the task, avoid the issue altogether by
performing the signature recalculation directly in do_package.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
Acked-by: Kieran Bingham <kieran.bingham@ideasonboard.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit fe3a2def88)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
This fixes
AssertionError:-
ptests which had no test results:
['nodejs']
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit cd629b722d)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Fixes
AssertionError:-
ptests which had no test results:
['fftw']
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit 46d69cd07c)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
When building against the 6.5 kernel (and kernel headers), the following
build error is encountered:
| vboxguestdrivers/7.0.10/vboxguestdrivers-7.0.10/vboxvideo/vbox_fb.c:194:24: error: 'drm_fb_helper_sys_fillrect' undeclared here (not in a function); did you mean 'drm_fb_helper_lastclose'?
| 194 | .fb_fillrect = drm_fb_helper_sys_fillrect,
| | ^~~~~~~~~~~~~~~~~~~~~~~~~~
| | drm_fb_helper_lastclose
| vboxguestdrivers/7.0.10/vboxguestdrivers-7.0.10/vboxvideo/vbox_fb.c:195:24: error: 'drm_fb_helper_sys_copyarea' undeclared here (not in a function); did you mean 'drm_fb_helper_set_par'?
| 195 | .fb_copyarea = drm_fb_helper_sys_copyarea,
| | ^~~~~~~~~~~~~~~~~~~~~~~~~~
| | drm_fb_helper_set_par
| vboxguestdrivers/7.0.10/vboxguestdrivers-7.0.10/vboxvideo/vbox_fb.c:196:25: error: 'drm_fb_helper_sys_imageblit' undeclared here (not in a function) | 196 | .fb_imageblit = drm_fb_helper_sys_imageblit,
| | ^~~~~~~~~~~~~~~~~~~~~~~~~~~
A patch from vbox-dev has been posted to fix the issue.
Upstream-Status: Submitted [https://www.mail-archive.com/vbox-dev@virtualbox.org/msg10129.html]
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit 030f670815)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Building against the 6.5+ kernel and headers resulted in a build failure
due to missing detected features. We can fix the issues by bumping to
2.2.0-rc4
Bumping zfs to version zfs-2.2.0-rc4-35-g229ca7d73, which comprises the following commits:
739db06ce Tag 2.2.0-rc4
4da8c7d11 Intel QAT 1.7 compatibility
32949f256 Relax error reporting in zpool import and zpool split
79ac1b29d ZIL: Change ZIOs issue order.
7dc2baaa1 ZIL: Revert zl_lock scope reduction.
5a7cb0b06 ZIL: Tune some assertions.
400f56e3f dmu_buf_will_clone: change assertion to fix 32-bit compiler warning
63159e5bd checkstyle: fix action failures
7eabb0af3 Try to clarify wording to reduce zpool add incidents
c65aaa838 Avoid save/restoring AMX registers to avoid a SPR erratum
e99e684b3 zed: update zed.d/statechange-slot_off.sh
1b696429c Make zoned/jailed zfsprops(7) make more sense.
084ff4abd tests/block_cloning: rename and document get_same_blocks helper
ab999406f Update outdated assertion from zio_write_compress
d19304ffe zed: Add zedlet to power off slot when drive is faulted
92f095a90 copy_file_range: fix fallback when source create on same txg
645a7e4d9 Move zinject from openzfs-zfs-test to openzfs-zfsutils
95649854b dracut: support mountpoint=legacy for root dataset
895cb689d zfs_clone_range should return a descriptive error codes
6bdc7259d libzfs: sendrecv: send_progress_thread: handle SIGINFO/SIGUSR1
1e488eec6 linux/spl/kmem_cache: undefine `kmem_cache_alloc` before defining it
c418edf1d Fix some typos
df8c9f351 ZIL: Second attempt to reduce scope of zl_issuer_lock.
bb31ded68 ZIL: Replay blocks without next block pointer.
c1801cbe5 ZIL: Avoid dbuf_read() before dmu_sync().
ffaedf0a4 Remove fastwrite mechanism.
02ce9030e Avoid waiting in dmu_sync_late_arrival().
0ae7bfc0a zpool_vdev_remove() should handle EALREADY error return
bd1eab16e linux: zfs: ctldir: set [amc]time to snapshot's creation property
b3c1807d7 readmmap.c: fix building with MUSL libc
b5e245633 Check the return value in clonefile test
c47f0f441 linux/copy_file_range: properly request a fallback copy on Linux <5.3
12f2b1f65 zdb: include cloned blocks in block statistics
4a104ac04 Tag 2.2.0-rc3
c24a48063 BRT should return EOPNOTSUPP
36d1a3ef4 zts: block cloning tests
2768dc04c linux: implement filesystem-side copy/clone functions for EL7
3366ceaf3 linux: implement filesystem-side clone ioctls
5d12545da linux: implement filesystem-side copy/clone functions
a3ea8c8ee dbuf_sync_leaf: check DB_READ in state assertions
0426e1327 dmu_buf_will_clone: only check that current txg is clean
8aa4f0f0f brt_vdev_realloc: use vmem_alloc for large allocation
7698503dc zfs_clone_range: use vmem_malloc for large allocation
b9aa32ff3 zed: Reduce log noise for large JBODs
571762b29 Linux 6.4 compat: META
991834f5d Remove zl_issuer_lock from zil_suspend().
41a0f6627 ZIL: Fix config lock deadlock.
c79d1bae7 Update changelog for OpenZFS 2.2.0 release
70232483b Tag 2.2.0-rc2
c5273e0c3 shellcheck: disable "unreachable command" check [SC2317]
685ae4429 metaslab: tuneable to better control force ganging
81be809a2 Adjust prefetch parameters.
8a6fde821 Add explicit prefetches to bpobj_iterate().
b6f618f8f Don't emit cksum_{actual_expected} in ereport.fs.zfs.checksum events
51a2b5976 Don't emit checksum histograms in ereport.fs.zfs.checksum events
8c81c0b05 zed: Fix zed ASSERT on slot power cycle
b221f4394 Fix zpl_test_super race with zfs_umount
e037327bf spa_min_alloc should be GCD, not min
1a2e486d2 Don't panic if setting vdev properties is unsupported for this vdev type
d8011707c Ignore pool ashift property during vdev attachment
f5f5a2db9 Rollback before zfs root is mounted
83b0967c1 Do not request data L1 buffers on scan prefetch.
73ba5df31 Linux 6.5 compat: disk_check_media_change() was added
1bc244ae9 Linux 6.5 compat: BLK_STS_NEXUS renamed to BLK_STS_RESV_CONFLICT
931dc7055 Linux 6.5 compat: intptr_t definition is canonically signed
5299f4f28 set autotrim default to 'off' everywhere
f917cf1c0 Fix the ZFS checksum error histograms with larger record sizes
56ed389a5 Fix raw receive with different indirect block size.
e613e4bbe Avoid extra snprintf() in dsl_deadlist_merge().
b4e630b00 Add missed DMU_PROJECTUSED_OBJECT prefetch.
bf6cd3079 FreeBSD: catch up to __FreeBSD_version 1400093
1266cebf8 FreeBSD: Fix build on stable/13 after 1302506.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit 67e31c930d)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
This bolt product does not currently have an entry in the CVE database.
However, the default cve-check logic that maps recipes to products in
the CVE database is incorrectly matching this package to a different
bolt product made by bolt-cms. As a result, CVE checking incorrectly
reports CVEs for that product for this package.
Signed-off-by: Jeffrey Pautler <jeffrey.pautler@ni.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit 722c4f16eb)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
* even openembedded-core/scripts/yocto-check-layer didn't spot missing Upstream-Status in:
/OE/layers/meta-openembedded/meta-oe/dynamic-layers/gnome-layer/recipes-graphics/openbox/openbox-xdgmenu/7_6.diff
nor
Malformed Upstream-Status 'Malformed Upstream-Status in patch
/OE/layers/meta-openembedded/meta-oe/dynamic-layers/meta-python/recipes-connectivity/lirc/lirc/0001-Unbolt-ubuntu-hack.patch
Please correct according to https://docs.yoctoproject.org/contributor-guide/recipe-style-guide.html#patch-upstream-status :
Upstream-Status: Inappropriates [ Cross-compile specific ]' (/OE/layers/meta-openembedded/meta-oe/dynamic-layers/meta-python/recipes-connectivity/lirc/lirc/0001-Unbolt-ubuntu-hack.patch)
Unknown Upstream-Status value 'inappropriates' (/OE/layers/meta-openembedded/meta-oe/dynamic-layers/meta-python/recipes-connectivity/lirc/lirc/0001-Unbolt-ubuntu-hack.patch)
those were caught by patchreview.py again, but executed on dynamic-layers/* as:
openembedded-core# for l in /OE/layers/meta-openembedded/meta-oe/dynamic-layers/*; do ./scripts/contrib/patchreview.py -v $l > $l.qa-patches; done
Signed-off-by: Martin Jansa <martin.jansa@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit aa851eb8e1)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
This ensures that all ptests can pass, libidn wrapper does not seem to
find the library and as a result the idn tests fail.
Fixes
Failed ptests:
{'libio-socket-ssl-perl': ['t/verify_hostname']}
as they are now skipped
ok 78 # skip no IDN support with Net::LibIDN
ok 79 # skip no IDN support with Net::LibIDN
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit 5851ca93a5)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
kodi uses its own FindNFS.cmake to find libnfs and succeeds with pkgconfig.
If libnfs-config.cmake is found it will also be utilized (for win/mac?)
which is generally bad for cross-compiling and causes the prefix to get hardcoded
to /usr thus libnfs.so.5.0.2 is taken from the host machine
Removing this file fixes:
| aarch64-poky-linux-ld.lld: error: /usr/lib/libnfs.so.5.0.2 is incompatible with elf64-littleaarch64
| aarch64-poky-linux-clang++: error: linker command failed with exit code 1 (use -v to see invocation)
| ninja: build stopped: subcommand failed.
Add CFLAG workaround to fix compiling with clang complaining about
old coding style while gcc doesn't care.
Signed-off-by: Markus Volk <f_l_k@t-online.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit 708b3016e8)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Move to new upstream, drop use of autotools-brokensep as the build now
works without it, drop local patches which have been merged, fix
buildpaths leakage.
License-Update: Fix misspellings [5cebe86a7b]
Signed-off-by: Alex Kiernan <alex.kiernan@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit 3f378f7924)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Update to latest release of latest LTS 20 release
* node v20 introduces several new features and fixes many bugs and CVEs as shown in [1]
* Refresh 0001-liftoff-Correct-function-signatures.patch against 20.5.1
* License-Update:
- Change zlib version 1.2.13, October 13th, 2022 to version 1.2.13.1, October xxth, 2022 [2]
- Change Copyright 2023 from Ada authors to Yagiz Nizipli and Daniel Lemire [4]
* Remove big-endian.patch as it is merged in v20.x [5] [6]
* Remove below list of patches since mips32 is deleted from v8 as part of update V8 to 10.7.193.13 [7] [8]
- mips-less-memory.patch
- 0001-mips-Use-32bit-cast-for-operand-on-mips32.patch
* Update Using-native-binaries.patch for node_js2c, it resolved below do_compile error [9]
Error:
/bin/sh: line 1: build/tmp/work/core2-64-poky-linux/nodejs/20.5.1/node-v20.5.1/out/Release/node_js2c: No such file or directory
* Remove obsolete dtrace & etw configure options (we had: --without-<feature>) from the recipe [10]
https://github.com/nodejs/node/releases/tag/v20.5.1
[1] https://github.com/nodejs/node/blob/main/doc/changelogs/CHANGELOG_V20.md
[2] f100732575
[3] 900ae1bda7
[4] d246536924
[5] 3cea5d5425
[6] f226350fcb
[7] a26ca5ed14
[8] 6bd756d7c6
[9] 4da7bc915c
[10] aa3a572e6b
Signed-off-by: Archana Polampalli <archana.polampalli@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit 13e83bd009)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
