The source information used during packaging can be use from other tasks to
have more detailed information on the files used during the compilation and
improve SPDX accuracy.
Source files used during compilation are store as compressed zstd json in
pkgdata/debugsources/$PN-debugsources.json.zstd
Format:
{ binary1: [src1, src2, ...], binary2: [src1, src2, ...] }
I checked the sstate size, and it slightly increases using core-image-full-cmdline:
without patch: 2456792 KB sstate-cache/
with patch: 2460028 KB sstate-cache/
(4236 KB or 0.17%)
(From OE-Core rev: c507dcb8a8780a42bfe68b1ebaff0909b4236e6b)
Adaptations to match spdx in scarthgap: change BP to PF
CC: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
CC: Richard Purdie <richard.purdie@linuxfoundation.org>
(From OE-Core rev: cba53212f5debf897752453364b9756a05c197de)
Signed-off-by: Daniel Turull <daniel.turull@ericsson.com>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
Install libpng test-suite to run it as a ptest.
As the test-suite takes more than 30 seconds to run,
add libpng-ptest to PTESTS_SLOW in ptest-packagelists.inc
(From OE-Core rev: 1b52b7ebe5f8fb490088622181cdb95e6b7f5a29)
Signed-off-by: Poonam Jadhav <poonam.jadhav@kpit.com>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
Remove aarch64 for ARM Cortex-R52 processor as it supports only 32-bit
ISA but not 64-bit ISA. Also update ARMPKGARCH for cortexr52hf.
(From OE-Core rev: 8ee21ec40e9f25ee97ec077b93751fea14b66e32)
Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Signed-off-by: Sandeep Gundlupet Raju <grsandeep85@gmail.com>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
This recipe takes longer time >20min when bitbake for package
write stage. When cross-verified for longer time duration, found
that do_check() stage taking 20min while other stages completes
before 6min.
This recipe gives only below two test binaries in the packages to
test (ptest: glibc-y2038-tests):
io/ftwtest
io/ftwtest-time64
The above test binaries are already included for testing in recipe
glibc-testsuite_2.39.bb.
It is by now well established that glibc itself works as it should,
that all affected 32 bit targets are configured to use 64 bit time_t,
and that any lingering y2038 issues are in components other than the c
library, and usually come from C programming mistakes (e.g. storing
timestamps in long). So this recipe seems to be redundant and
can be removed.
Review comments for fixing above longer time duration ended up in
removing this recipe as a proposal is below
https://lists.openembedded.org/g/openembedded-core/topic/112188476#msg214636
Removed lines having reference to glibc-y2038-tests in the files.
For master branch requested for integration and below is the link
https://lists.openembedded.org/g/openembedded-core/message/215655
(From OE-Core rev: b214cc84a922f7a3fb7ebbc501189ce25e8bd2bd)
Signed-off-by: rajmohan r <semc.2042@gmail.com>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
(From OE-Core rev: 7626067432743657e9c536ca16a2dac513ba4929)
Signed-off-by: Michael Halstead <mhalstead@linuxfoundation.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Martin Jansa <martin.jansa@gmail.com>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
When multiple recipes are built in parallel, Ccache sometimes refuses to
lookup some objects in cache, leading to undesired cache misses. The
root cause of this is an interaction between the way how bitbake
constructs a recipe sysroot and Ccache's `include_file_ctime` check.
Whenever bitbake creates a recipe's sysroot it hardlinks the files
provided by a recipes dependencies. Adding a hardlink to a file changes
it's ctime which in turn leads Ccache to believe that the file was
modified thus aborting the cache lookup.
To avoid this situation, add `include_file_ctime` to the list of checks
that should be ignored using the Ccache sloppiness configuration option
[1].
Example of a log entry that Ccache ignores a file:
/
|recipe-sysroot/usr/include/bits/pthread_stack_min.h had status change
|near or after invocation (ctime 1739822508.107677255, invocation time
|1739822507.970071107)
\
1 - https://ccache.dev/manual/4.10.2.html#config_sloppiness
(From OE-Core rev: c74a6d6afc52606825e583cae1162e13a5369498)
Signed-off-by: Fabio Berton <fabio.berton@criticaltechworks.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(cherry picked from commit 4899698297c7783e02aba5388e0469cc83bd2f70)
Signed-off-by: Steve Sakoman <steve@sakoman.com>
In case both UBOOT_SIGN_ENABLE and UBOOT_ENV are enabled and
kernel-fitimage.bbclass is in use to generate signed kernel
fitImage, there is a circular dependency between uboot-sign
and kernel-fitimage bbclasses . The loop looks like this:
kernel-fitimage.bbclass:
- do_populate_sysroot depends on do_assemble_fitimage
- do_assemble_fitimage depends on virtual/bootloader:do_populate_sysroot
- virtual/bootloader:do_populate_sysroot depends on virtual/bootloader:do_install
=> The virtual/bootloader:do_install installs and the
virtual/bootloader:do_populate_sysroot places into
sysroot an U-Boot environment script embedded into
kernel fitImage during do_assemble_fitimage run .
uboot-sign.bbclass:
- DEPENDS on KERNEL_PN, which is really virtual/kernel. More accurately
- do_deploy depends on do_uboot_assemble_fitimage
- do_install depends on do_uboot_assemble_fitimage
- do_uboot_assemble_fitimage depends on virtual/kernel:do_populate_sysroot
=> do_install depends on virtual/kernel:do_populate_sysroot
=> virtual/bootloader:do_install depends on virtual/kernel:do_populate_sysroot
virtual/kernel:do_populate_sysroot depends on virtual/bootloader:do_install
Attempt to resolve the loop. Pull fitimage configuration options into separate
new configuration file image-fitimage.conf so these configuration options can
be shared by both uboot-sign.bbclass and kernel-fitimage.bbclass, and make use
of mkimage -f auto-conf / mkimage -f auto option to insert /signature node key-*
subnode into U-Boot control DT without depending on the layout of kernel fitImage
itself. This is perfectly valid to do, because the U-Boot /signature node key-*
subnodes 'required' property can contain either of two values, 'conf' or 'image'
to authenticate either selected configuration or all of images when booting the
fitImage.
For details of the U-Boot fitImage signing process, see:
https://docs.u-boot.org/en/latest/usage/fit/signature.html
For details of mkimage -f auto-conf and -f auto, see:
https://manpages.debian.org/experimental/u-boot-tools/mkimage.1.en.html#EXAMPLES
(From OE-Core rev: 259bfa86f384206f0d0a96a5b84887186c5f689e)
Fixes: 5e12dc911d0c ("u-boot: Rework signing to remove interdependencies")
Reviewed-by: Adrian Freihofer <adrian.freihofer@siemens.com>
(From OE-Core rev: d7bd9c6276611c8c8de0c2a24947783eae5d932a)
Signed-off-by: Marek Vasut <marex@denx.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
Cortexa32 is a 32-bit armv8a architecture processor, so set the tune feature
as armv8a instead of aarch64 which is 64-bit armv8a architecture.
It solves the following build error while compiling libgcc-initial
and libssp-nonshared.
-- snip --
aarch64-poky-linux-musl-gcc: error: unrecognized command-line option '-mfpu=neon'
aarch64-poky-linux-musl-gcc: error: unrecognized command-line option '-mfloat-abi=hard'
-- snip --
(From OE-Core rev: a83ead146c15772970c7ca649e81929302349033)
Signed-off-by: Jagadeesh Krishnanjanappa <workjagadeesh@gmail.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(cherry picked from commit 3b898270aca62559dfa42ed71d296fe8a8b46a41)
Signed-off-by: Steve Sakoman <steve@sakoman.com>
Some wic images need this command. Since it is part of coreutils, it doesn't really
cost anything to have in HOSTTOOLS and it avoids signifiant build dependencies on
coreutils-native.
[YOCTO #15571]
(From OE-Core rev: 85451cdaee4718233211da1e43db01f5cd2b1aff)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(cherry picked from commit 522000ce5c4f0201cbe42d7826b6a8489ed10117)
Signed-off-by: Steve Sakoman <steve@sakoman.com>
Add myself as maintainer for the following:
- python3-setuptools
- python3-smmap
- python3-subunit
- python3-testtools
With that, every Python recipe in oe-core has a maintainer assigned.
(From OE-Core rev: 97c2cf74e556511b3827362f6b3439daa26091e9)
Signed-off-by: Trevor Gamblin <tgamblin@baylibre.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
(cherry picked from commit f7c4ab54d3ff1895d9fcb9aa20dece5e0661579d)
Signed-off-by: Steve Sakoman <steve@sakoman.com>
This rebuilds whenever DISTRO_VERSION changes (i.e. any commit is made)
and systemd depends upon it so lots of things end up rebuilding which
isn't necessary,
(From OE-Core rev: 9d2eded1d423a24a8fa811f26d501bd68cd7a1be)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(cherry picked from commit 002a2a9d977ed5b86138333c567d25616d38c60b)
Signed-off-by: Steve Sakoman <steve@sakoman.com>
* Since commit [a23c482cab allarch: only enable allarch when multilib is
not used], allarch recipes will also be installed into
${MLPREFIX}recipe-sysroot, so this appending is not needed.
* This appending also causes some QA errors. Eg: for lib32-php, the
recipe will use 's@${RECIPE_SYSROOT}@@g' to remove host specific path,
this appending makes not all the host specific path are matched.
(From OE-Core rev: e88f159989cbf8080f0a8fb449c878f2a5747774)
Signed-off-by: Changqing Li <changqing.li@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(cherry picked from commit e6e6076f1956c711814c14d76194794d950e45f8)
Signed-off-by: Steve Sakoman <steve@sakoman.com>
gcc stable version upgraded from v13.2 to v13.3
Dropped CVE-2023-4039.patch, CVE-2024-0151.patch and 0026-aarch64-Fix-loose-ldpstp-check-PR111411.patch
because its been taken to gcc-13.3 with below commits 71a2aa2127283f450c623d3604dbcabe0e14a8d4, 5550214b58e95320b54e42ef0e37c6479e04b27b
and 4bb1ae3c13ce4fb72129229de66f5ffbcd45fe4c respectively.
For changes in v13.3 see: https://gcc.gnu.org/onlinedocs/gcc-13.3.0/gcc/
Below is the bug fix list for v13.3
https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&list_id=429106&resolution=FIXED&target_milestone=13.3
There are a total 173 bugs are fixed in this release, below is the list of bugs fixed excluding the regression fixes.
ID Product Comp Assignee▲ Summary
114408 gcc analyzer dmalcolm ICE when invoking strcmp multiple times with -fsanitize=undefined -O1 -fanalyzer -flto
109251 gcc analyzer dmalcolm -Wanalyzer-deref-before-check false positives seen in Linux kernel due to check in macros
114473 gcc analyzer dmalcolm ICE: in deref_rvalue, at analyzer/region-model.cc:2780 with -fanalyzer -fanalyzer-call-summaries
100988 gcc fortran anlauf Missed optimization: RESTRICT missing for optional arguments
112764 gcc fortran anlauf Associating entity does not have target attribute if selector has pointer attribute in associate block
114001 gcc fortran anlauf is_contiguous considers unlimited polymorphic dummy always as contiguous
112787 gcc target avieira Codegen regression of large GCC vector extensions when enabling SVE
114160 gcc target cmuellner ICE on RISCV (-mcpu=thead-c906) when building glibc in dwarf2out_frame_debug_cfa_offset
110882 gcc analyzer dmalcolm ICE with -fanalyzer on zero-sized array
111289 gcc analyzer dmalcolm Unwarranted -Wanalyzer-va-arg-type-mismatch warning
112790 gcc analyzer dmalcolm Wanalyzer-deref-before-check false positives seen in Linux kernel due to inlining
112792 gcc analyzer dmalcolm Wanalyzer-out-of-bounds false positives seen on Linux kernel with certain unions
114316 gcc libstdc+ fdumont assert failure with _GLIBCXX_DEBUG and empty range of singular iterators passed to std:: algorithm
108121 gcc modula2 gaius Failing tests on x86_64-linux-gnu
110754 gcc middle-e jakub assume create spurious load for volatile variable
105456 gcc libfortr jvdelisle Child I/O does not propage iostat
114747 gcc target kito Wrong SEW set for mixed-size intrinsics
104831 gcc target patrick RISCV libatomic LR.aq/SC.rl pair insufficient for SEQ_CST
108174 gcc target pinskia ICE: tree check: expected function_type or method_type, have ggc_freed in aarch64_resolve_overloaded_memtag, at config/aarch64/aarch64-builtins.cc:3349
114314 gcc driver pinskia ICE: in common_handle_option, at opts.cc:3356 with -fno-multiflags
99493 gcc c++ ppalka Address of template parameter object is not a valid template argument
99631 gcc c++ ppalka decltype of non-type template-parameter shouldn't be const
104634 gcc c++ ppalka Explicit template instantiation does not work when there are multiple partial template specialization using concepts
110809 gcc c++ ppalka ICE: in unify, at cp/pt.cc:25226 with floating-point NTTPs
110927 gcc c++ ppalka GCC fails to parse dependent type in concept through partial specialization
111493 gcc c++ ppalka multidimensional subscript operator inside requires is broken
113242 gcc c++ ppalka g++ rejects-valid template argument of class type containing an lvalue reference
113529 gcc c++ ppalka Incorrect result of requires-expression in case of function call ambiguity and `operator<=>`
108046 gcc libstdc+ redi The dot in the floating-point alternative form has wrong position
110708 gcc libstdc+ redi std::format("{:%EEC %OOd}", std::chrono::system_clock::now()) should be rejected 2023-07-28
110719 gcc libstdc+ redi Should chrono formatters always use std::time_put for locale's representation?
110860 gcc libstdc+ redi std::format("{:f}",2e304) invokes undefined behaviour
110862 gcc libstdc+ redi format out of bounds read on format string "{0:{0}"
110917 gcc libstdc+ redi std::format_to(int*, ...) fails to compile because of _S_make_span
110944 gcc libstdc+ redi std::variant & optional GDB representation is too verbose
110968 gcc libstdc+ redi format out of bounds read on format("{:05L}",-1.f)
110970 gcc libstdc+ redi clang / c++23 missing 'typename' prior to dependent type name
110990 gcc libstdc+ redi `format_to_n` returns wrong value
111511 gcc libstdc+ redi Incorrect ADL in std::to_array in GCC 11/12/13
111826 gcc libstdc+ redi __cpp_lib_format should be 202110, not 202106
111948 gcc libstdc+ redi subrange modifies a const size object
112607 gcc libstdc+ redi _Normalize does not consider char_type for the basic_string_view case
112832 gcc libstdc+ redi Broken non-SFINAE-friendly `set_debug_format()` for `const char *` formatter
113500 gcc libstdc+ redi Using std::format with float or double based std::chrono::time_point causes error: no match for 'operator<<'
13512 gcc libstdc+ redi Incorrect results for std::format("{:#.3g}", flt)
114103 gcc libstdc+ redi FAIL: 29_atomics/atomic/lock_free_aliases.cc -std=gnu++20 (test for excess errors)
114152 gcc libstdc+ redi Wrong exception specifiers for LFTSv3 scope guard destructors
114863 gcc libstdc+ redi std::format applying grouping to nan's and inf's
115063 gcc libstdc+ redi compilation error: std::basic_stracktrace::max_size()
105523 gcc target saaadhu Wrong warning array subscript [0] is outside array bounds
93370 gcc target unassigned Aarch64 accepts but ignores target("+sm4") unless ARMv8.2-A is enabled
93762 gcc fortran unassigned Truncation of deferred-length string when passing as optional
100285 gcc libstdc+ unassigned experimental/net/socket/socket_base.cc fails on arm-eabi (r12-137)
106037 gcc ada unassigned internal error with Aggregate aspect on array type
110127 gcc c++ unassigned -fimplicit-constexpr leads to extremely slow and memory intensive compilation
110133 gcc libstdc+ unassigned System error message should ideally use strerror_r over strerror
110974 gcc libstdc+ unassigned format out of bounds read on invalid format string "{:{}."
111102 gcc libstdc+ unassigned illegal pointer arithmetic invoked by std::format("L{:65536}",1)
112480 gcc libstdc+ unassigned optional<T>::reset emits inefficient code when T is trivially-destructible
113294 gcc libstdc+ unassigned constexpr error from accessing inactive union member in basic_string after move assignment
113815 gcc ada unassigned error: there is no applicable operator "*" for a string type
113824 gcc target unassigned AVR: ATA5795 in wrong multilib set 2024-02-08
113850 gcc libgcc unassigned condition variables timed wait does a lot of spurious wakeups on Win32 threading implementation
113927 gcc target unassigned Sets up a stack-frame even for trivial code
114136 gcc middle-e unassigned wrong code for c23 fully anonymous arg lists on arm
97245 gcc fortran anlauf ASSOCIATED intrinsic does not recognize a pointer variable the second time it is used
101135 gcc fortran anlauf Load of null pointer when passing absent assumed-shape array argument for an optional dummy argument
110825 gcc fortran anlauf TYPE(*) dummy argument to generate an unused hidden argument
110826 gcc fortran anlauf Fortran array of derived type with a pointer to function with dimensional arguments fails
113799 gcc fortran anlauf gfc_replace_expr: double free detected ?
114012 gcc fortran anlauf overloaded unary operator called twice
113601 gcc target gjl avr: Wrong SRAM start for ATmega3208 and ATmega3209
107201 gcc target unassigned -nodevicelib not working for devices -mmcu=avr...
114024 gcc fortran unassigned ICE allocate statement with source=cmp%re and z an array
53372 gcc target unassigned Section attribute ignored with address space
112952 gcc target unassigned avr: attribute address not working with -fdata-sections -fno-common
114752 gcc target unassigned AVR: internal compiler error. Unknown mode: const_double:DF
114794 gcc target unassigned Speed up udivmodqi4
(From OE-Core rev: 20b94a6f3681afc9d5f7c07d571fcc47efcc9827)
Signed-off-by: Deepthi Hemraj <Deepthi.Hemraj@windriver.com>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
In testing websocket hashequivalence, corrupted sstate was injected into the
autobuilder extensively. With the new release/LTS, being able to clearly
differentiate between old and new sstate is probably desireable anyway
so bump the appropriate versions.
(From OE-Core rev: 7f107c180f592be29f57f580c60a6adbbebd7714)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
For the newer hash equivlance servers we need websockets. Import it
from meta-oe so we can easily include it in buildtools tarball.
(From OE-Core rev: c61ed007b9e06683065aed62af1e1ca4569b8c16)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
oldincludedir was removed by 506c91cbc6a604a84e37e53ccff430436369802e
(From OE-Core rev: 0228ab43e9b659771f4f59944897aec6879f8209)
Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When run-postinsts is installed, a service is added for system which can run
while the package is still being installed. This calls "opkg configure" and if
package management is still running, it can deadlock and error.
To work around this, call fcntl-lock on the opkg lock file and if the lock
was held, it would wait to obtain it. This wait gives the package management
time to finish the install before the configure can then take the lock and run.
Note the dependency in SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS otherwise we'd see
sstate selftest failures.
Also ensure that if the configure fails, the scripts returns an error. This
applies to opkg and dpkg.
(From OE-Core rev: 96d37df074dc1fe1578c1406235dff7e328b62b7)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The upstream maintainer for Error has deprecated it for quite some time [1].
The only dependency in oe-core was coreutils-ptest.
[YOCTO #15461]
[1] https://metacpan.org/pod/Error#WARNING
Using the "Error" module is no longer recommended due to the black-magical
nature of its syntactic sugar, which often tends to break. Its maintainers
have stopped actively writing code that uses it, and discourage people from
doing so. See the "SEE ALSO" section below for better recommendations [2].
[2] https://metacpan.org/pod/Error#SEE-ALSO
SEE ALSO
--------
See Exception::Class for a different module providing Object-Oriented
exception handling, along with a convenient syntax for declaring hierarchies
for them. It doesn't provide Error's syntactic sugar of try { ... },
catch { ... }, etc. which may be a good thing or a bad thing based on what
you want. (Because Error's syntactic sugar tends to break.)
Error::Exception aims to combine Error and Exception::Class "with correct
stringification".
TryCatch and Try::Tiny are similar in concept to Error.pm only providing a
syntax that hopefully breaks less.
(From OE-Core rev: 7750469e0acfb7f7ef5b3002d1562df5354e6a61)
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Any image that inherits qemuboot must also add image dependencies on
qemu-system-native and qemu-helper-native, otherwise the image won't
be able to be booted.
Currently this is done by conf/machine/include/qemu.inc, but not every
machine that uses qemuboot includes that file.
Move the EXTRA_IMAGEDEPENDS from qemu.inc into qemuboot.bbclass, so that
the dependencies don't have to be duplicated.
(From OE-Core rev: dd54cf058f632e985917ff227483995f368e6a7d)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
As we're close to release, drop compatibility to nanbield, people
have had time to switch now.
(From OE-Core rev: 0e42326dfd6b9042b405329ceb56a93199a89a85)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add vulkan-volk recipe to support building latest vulkan-tools.
(From OE-Core rev: d3d0375fa0b4809d2c69837faf5df297d92de683)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fish vfs was renamed to shell vfs:
6ca4ab4b4e
(From OE-Core rev: 3dc97bf745239a817af956e354b9b991bf108e59)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It's a hard dependency of recent python3-sphinx-rtd-theme
versions:
4d6de11137
The issue is exposed by latest btrfs-tools update.
(From OE-Core rev: 7a3d074f2d1679b4d4e52c4a023edb46224ca0be)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The bmaptool (previously: bmap-tools, bmap-tool, bmaptool) has been moved
to be under the Yocto Project umbrella and is now hosted at:
github.com/yoctoproject/bmaptool
[RP: Added a couple of missing renames]
(From OE-Core rev: 7a036b1a1ec7dcd27dbe18d4c2e703bd2a8af182)
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If we enable package-management for core-image-full-cmdline we need the workarounds
used for core-image-weston to ensure the oe-selftest license QA tests keep working.
(From OE-Core rev: 29bc855c167ff66aea7ca4681cee85c2557b2308)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Drop backported musl fixes.
* Set `change-id` rather than `changelog-seen`
to fix build warning.
* Add fixes for 4b7e0a0b56aa24 ("Handle vendored sources
when remapping paths") which otherwise cause build failures:
| thread 'main' panicked at src/core/builder.rs:1795:26:
| std::fs::read_dir(registry_src) failed with No such file or directory (os=
error 2)
https://blog.rust-lang.org/2023/12/28/Rust-1.75.0.html
(From OE-Core rev: 9aec2c6c777388bb3129aa4c4f27a40f912522b4)
Signed-off-by: Yash Shinde <Yash.Shinde@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Now both gcc and clang all support -march=loongarch64, so we can use it.
(From OE-Core rev: acc08582293709c73011083aa7d5c631a9ae8c8c)
Signed-off-by: Xiaotian Wu <wuxiaotian@loongson.cn>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
split_locales() must only check subdirectories in paths added to
LOCALE_PATHS to avoid creating weird packages based on filenames also
present in paths.
Without such a filter, cups recipe adding ${datadir}/cups/templates to
LOCALE_PATHS creates the following incorrect packages:
- cups-locale-add-class.tmpl
- cups-locale-add-printer.tmpl
- cups-locale-admin.tmpl
(From OE-Core rev: ba3aee0d516bd066829d6edaa8d7bacdd75dd6ef)
Signed-off-by: Jonathan GUILLOT <jonathan@joggee.fr>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meson-python is a Python build backend built on top of the Meson
build-system. It enables you to use Meson for your Python packages.
https://meson-python.readthedocs.io/en/latest/
It is used as the PEP-517 build-backend for python3-numpy and python3-scipy.
For other projects using the backend, see:
https://meson-python.readthedocs.io/en/latest/projects-using-meson-python.html
(From OE-Core rev: 57df1e3fd77a412fb7d585362a7263a4f847fe07)
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is a dependency for python3-meson-python.
(From OE-Core rev: b8c8d384b4622de7b5a4748e6e06665615674ba8)
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Due to hashserv API changes in siggen, we need bitbake 2.7.3.
(From OE-Core rev: 7172fd527fde440f26dd6cc371cde2720dbaa366)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Existing conf-notes.txt is not adequate in situations where the user
needs to select a config template from several, or get an overview of them and
is interested only in a brief explanation of what the template is for,
but not extended multi-paragraph instructions for how to use it.
Such summaries can be provided via conf-summary.txt and
this patch adds such a summary for the oe-core default template.
Updates to the tools and a tool for selecting templates which
will make specific use of the summary will follow.
(From OE-Core rev: aa96c2064a874714cfe4bac2fa622690e4c27ee4)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is present in the poky repository, even though it should
not be:
https://git.yoctoproject.org/poky/tree/meta/conf/templates/default
I couldn't find which tool leaves the file in place when combining
oe-core/bitbake/meta-yocto repos into poky, so this patch is rather
a request to point me to where it happens (or just fix it directly there).
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Some packages may contain localized files not located in default path
${datadir}/locale. Add the new variable LOCALE_PATHS to allow a recipe
to define extra paths or even fully override the scanned directories.
LOCALE_PATHS is set at ${datadir}/locale by default to keep the exact
same behavior for the recipes which did not need modification.
(From OE-Core rev: 0ffc7cf01225743789ac30dd325fca05b9203be1)
Signed-off-by: Jonathan GUILLOT <jonathan@joggee.fr>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There is a single version of llvm in core these days, furthermore the
version is no longer asked for by recipes such as mesa, which would use
llvm-config tool according to version of llvm found.
(From OE-Core rev: 15d09b02b2632ab1cabc3b1bd9f521e6d3d3b83f)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Cc: Ross Burton <ross.burton@arm.com>
Acked-by: Martin Jansa <martin.jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Python 3 interprets string literals as Unicode strings, and therefore
\s is treated as an escaped Unicode character which is not correct.
Declaring the RegEx pattern as a raw string instead of unicode is
required for Python 3.
(From OE-Core rev: 662f52f1713c9f070550fc0c874eb62312218ea4)
Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com>
feature-microblaze-versions.inc#
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Upstream is in the process of migrating testing to pytest, backport
test_dump_load.py (the legacy_tests were throwing Errors and Failures).
We don't really need to run upstream's test suite, but we do need to verify
that our runtime is functional.
a98fd6088e
(From OE-Core rev: b0fdf0688109ba6b87840a0837bebee3d9a27089)
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This reverts commit dea5e8863792dc7bb3324b543e04da4c94a060aa.
The original commit claims that lzop is unused in OE-core.
That is not correct, the following places still use it and
became unbuildable now:
"
meta/classes-recipe/image_types.bbclass:CONVERSION_CMD:lzo = "lzop -9 ${IMAGE_NAME}.${type}"
meta/classes-recipe/image_types.bbclass:CONVERSION_DEPENDS_lzo = "lzop-native"
meta/classes-recipe/kernel-uboot.bbclass: lzop -9 linux.bin
meta/classes-recipe/kernel.bbclass:DEPENDS += "${@bb.utils.contains("INITRAMFS_FSTYPES", "cpio.lzo", "lzop-native", "", d)}"
meta/classes-recipe/kernel.bbclass: lzop -df ${B}/usr/${INITRAMFS_IMAGE_NAME}.$img
"
Furthermore, LZO is the best compromise between kernel decompression
time and size on low end ARM systems, that is why it is often used
with e.g.:
FIT_KERNEL_COMP_ALG = "lzo"
FIT_KERNEL_COMP_ALG_EXTENSION = ".lzo"
Reinstate the package to avoid breaking this use case.
[RP: For me, the real reason to justify this is fact that several SoC/BSP
layers do want this as a dependency]
(From OE-Core rev: 6e8a0d66e05387d55c49a275faa7f4aa2bf6f2ac)
Signed-off-by: Marek Vasut <marex@denx.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
