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 e88b777cbecd85ff7d2916209774354a6a458101)
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 ef9d73fced12e7b2dab485f0443cec84e55d016b)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
This reverts commit a0557fe5433620717eeb00d3b16801711337b1a4.
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 bfb626a23022d871ce3c0c64cb9e5d1cc17c737e)
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 c1ea15792baaa6c6c3d7005d110ad4689051ba20)
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 883860c40c67544dfe3e2d72732e2d8ef46b6f30)
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 06faef7244794a076a64006c61774e7cef1217aa)
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 7ddce1977953723091999ea70c0e1661748fbd77)
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 cb8908b91ead37c5d74b44f949c12c33354956a7)
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 4b59083f4c50e097a09230bd533bdd9fbc8178ef)
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 cd629b722db82b6ec0e97f6564ba52abfe57d93c)
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 46d69cd07c32aa67020b297bc26e47cde0a5b57c)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
clang builds work without this Workaround
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit 61663d299051669c7c08c90da2518f0f24fabaaa)
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 030f6708154054787dca7c2de95d074970115187)
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 722c4f16eb388abc6a0bd518ea991a3a6bebe790)
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 aa851eb8e14eec6a49ef90d2aaa3ed5150916737)
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 708b3016e81a2a06883b0bb23bfedc8cb3e3239d)
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 3f378f792456cf28284e8a342730974957787241)
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 13e83bd009200f42741083c5a6f1fbc653205c49)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
* to avoid possible issue next time new mozjs version recipe is
introduced (as multilib isn't as well tested as other build configs)
* this depends on oe-core change to expand script name in MULTILIB_SCRIPTS:
https://lists.openembedded.org/g/openembedded-core/message/188301
Signed-off-by: Martin Jansa <martin.jansa@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit 7d473b7616efc0eaa3f44582d0ed5b69f9905f02)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
* fixes:
DEBUG: Executing shell function multilibscript_rename
mv: cannot stat 'lib32-mozjs-115/115.2.0/package/usr/bin/js102-config': No such file or directory
WARNING: exit code 1 from a shell command.
* cannot use PV here just yet, see the next commit
Signed-off-by: Martin Jansa <martin.jansa@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit 1abd1a419512f9300e98001494eaa67220ee563a)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
This fixes a possible segfault in polkit
Signed-off-by: Markus Volk <f_l_k@t-online.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit 2887c5c0a2eb321f277037e055288f05878db369)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
If protoc is enabled for the build, recipes using protobuf will
fail when protoc is not available in the recipe sysroot:
| The imported target "protobuf::protoc" references the file
|
| ".../recipe-sysroot/usr/local/oe-sdk-hardcoded-buildpath/sysroots/x86_64-pokysdk-linux/usr/bin/protoc-3.21.5.0"
|
| but this file does not exist. Possible reasons include:
|
| * The file was deleted, renamed, or moved to another location.
|
| * An install or uninstall procedure did not complete successfully.
|
| * The installation package was faulty and contained
|
| ".../recipe-sysroot/usr/local/oe-sdk-hardcoded-buildpath/sysroots/x86_64-pokysdk-linux/usr/lib/cmake/protobuf/protobuf-targets.cmake"
|
| but not all the files it references.
Use SYSROOT_DIRS to stage the binary to sysroot so it's always
available for other recipes.
Signed-off-by: Samuli Piippo <samuli.piippo@qt.io>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit a0557fe5433620717eeb00d3b16801711337b1a4)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Update to latest on 0.13.0 release branch
Set PR to 0.13.0
Drop unused SRC_URI checksum
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit 0e3c482192f2ff8bfc1c05c5d8542b22e1d67d0d)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Unless DEBUG_BUILD is enabled, pass -g1 to massively reduce the size of
the debug symbols
Level 1 produces minimal information, enough for making backtraces in
parts of the program that you don't plan to debug. This includes
descriptions of functions and external variables, and line number
tables, but no information about local variables.
This makes the sstate objects a lot more manageable, and packaging
faster.
Based on - https://patchwork.yoctoproject.org/project/oe-core/patch/20230925113508.1087898-1-ross.burton@arm.com/
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit 6985b3d6a9b77d12bd787fc522533b45e4f501d3)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
