Khem Raj [Sat, 27 Nov 2021 09:22:39 +0000 (01:22 -0800)]
weston-init: Pass --continue-without-input when launching weston
This ensures that we do not need keyboard/mouse or other input system
Weston's default behavior is to not open if input devices are not
found, but we may not always have input devices connected for systems
running weston in field
Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Jacob Kroon [Wed, 24 Nov 2021 05:31:10 +0000 (06:31 +0100)]
native/cross: Add ar wrapper for determinism
Add a wrapper around ar calls for native/cross recipes. This wrapper adds
the -D option so that deterministic archives are built for native/cross
output. This improves the changes of hash equivalence matches and hence
build artefact reuse.
We don't need this in the target case since we compile binutils-cross
with an option making this the default. We need a wrapper since we need
to remove the "u" option and replace it with "D" but also allow things like
"--version" to continue to work too.
Signed-off-by: Jacob Kroon <jacob.kroon@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Mon, 22 Nov 2021 16:11:45 +0000 (16:11 +0000)]
nativesdk: Handle chown/chgrp calls in nativesdk do_install tasks
We disable the useradd code for nativesdk targets since we don't support
postinstalls or multiple users in those cases. This means any usage
of chown/chgrp inside do_install tasks won't work and would have to be
conditional. Rather than require all recipes to do that, add intercepts
of the calls and map those to root/root user/groups. We can't just ignore
them as some calls are used to remove host contamination from the host
user ID so they need to be made, just as root.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Max Krummenacher [Mon, 22 Nov 2021 16:34:58 +0000 (17:34 +0100)]
perf: sort-pmuevents: don't drop elements
If a struct element neither has an element cpuid or name it gets silenty
dropped.
Kernel 5.15 for some ARCHs have at least one array of structs matching
this.
e.g. for arm pmu-events.c:
Bruce Ashfield [Tue, 23 Nov 2021 21:23:43 +0000 (16:23 -0500)]
kernel: introduce python3-dtschema-wrapper
The 5.16 kernel introduced mandatory schema checking on any dtb file
built through the kernel.
That funcionality is provided via python3-dt-schema.
The dependencies to enable that functionality is not small, and may
not always be desired (in particular on architectures that do not
support dtbs, or in development cycles). It may also be useful for
allowing a non-conformant dts to be compiled.
This commit introduces a set of wrapper scripts that when added
as a depenency to the kernel, can pass both the validation testing
and validation steps of a dts.
We use the wrapper by default, while more dts file are brought up
to spec and the dt-validation matures upstream.
To enable valiation, simply add 'dt-valiation' to the PACKAGECONFIG
variable and the full dt-schema package will be selected and
validation will occur.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Bruce Ashfield [Tue, 23 Nov 2021 04:15:16 +0000 (23:15 -0500)]
linux-yocto: export pkgconfig variables to devshell
Not all of the kernel host/build Makefiles allow pkg-config
to be overriden to pkg-config-native. Exporting these variables
allow us to debug host tool issues with the kernel build.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Bruce Ashfield [Tue, 23 Nov 2021 03:54:28 +0000 (22:54 -0500)]
python: import rfc3339-validator from meta-python
Importing rfc3339-validator from meta-python, which is a dependency of
python3-jsonschema. These packges are required to support
the validation of kernel device trees.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Bruce Ashfield [Tue, 23 Nov 2021 03:54:28 +0000 (22:54 -0500)]
python: import idna from meta-python
Importing idna from meta-python, which is a dependency of
python3-jsonschema. These packges are required to support
the validation of kernel device trees.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Bruce Ashfield [Thu, 25 Nov 2021 16:20:37 +0000 (11:20 -0500)]
python3-jsonpointer: Update 2.1 to 2.2
The import from meta-python was slightly out of date, and the
2.1 version was grabbed. We bump the oe-core version to 2.2
to match the latest meta-oe version.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bruce Ashfield [Tue, 23 Nov 2021 04:22:55 +0000 (23:22 -0500)]
kernel: export native PKGCONFIG variables
In a similar manner to cml1.bbclass, we export the pkg-config
variables to allow a direct call to pkg-config access to the
native sysroot versus the target sysroot.
The kernel doesn't use pkg-config for target configuration,
and has many explicit calls to pkg-config, without the
possibility of easy override to pkg-config-native.
The calls to pkg-config could be made cross friendly via
replacement with make variables, but until that effort is
undertaken upstream, we need a bridge approach.
In particular, this is required for dtschema validation,
which is a requirement in kernel 5.16+
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Bruce Ashfield [Tue, 23 Nov 2021 04:17:09 +0000 (23:17 -0500)]
linux-yocto-dev: bump to v5.16+
Bumping the version of -dev ot 5.16. We also pickup two new
dependencies to support kernel dtschema validation. This
requirement was introduced by kernel commit:
It is possible to build a single dtb, but not with DT schema validation
enabled. Enable the schema validation to run for %.dtb and %.dtbo
targets. Anyone building a dtb for a specific platform *should* pay
attention to schema warnings.
This could be supported with a separate %.dt.yaml target instead.
However, the .dt.yaml format is considered an intermediate format and
could possibly go away at some point if schema checking is integrated
into dtc. Also, the plan is to enable the schema checks by default once
platforms are free of warnings, and this is a move in that direction.
Cc: Dmitry Baryshkov <dmitry.baryshkov@linaro.org> Cc: Tom Rini <trini@konsulko.com> Cc: Masahiro Yamada <masahiroy@kernel.org> Cc: linux-kbuild@vger.kernel.org Signed-off-by: Rob Herring <robh@kernel.org> Acked-by: Masahiro Yamada <masahiroy@kernel.org> Link: https://lore.kernel.org/r/20210913145146.766080-1-robh@kernel.org Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Ross Burton [Wed, 24 Nov 2021 17:15:29 +0000 (17:15 +0000)]
oe/utils: by default cap cpu_count() to 64 cores
Larger systems may have large numbers of cores, but beyond a certain
point they can't all be used for compiling: whilst purely
compute-intensive jobs can be parallelised to hundreds of cores,
operations such as compressing (needs lots of RAM) or compiling (lots of
I/O) don't scale linearly.
For example, the Marvel ThunderX2 has 32 cores, each capable of
executing four threads, and can be configured with two sockets, making
256 CPUs according to Linux. Zstd using 256 threads has been seen to
fail to allocate memory during even small recipes such as iso-codes.
Add a default cap of 64 CPUs to the cpu_count() method so that extreme
parallisation is limited. 64 is high enough that meaningful gains
beyond it are unlikely, but high enough that most systems won't be
effected.
Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Rework support for error() on non-glibc targets:
upstream now provides its own implementation, so we can drop
the patch that adds ours; said implementation isn't
build-tested with tests, so ptest has to be disabled on musl.
This, in turns, allows dropping 0004-Fix-error-on-musl.patch.
License-Update: copyright years Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bruce Ashfield [Tue, 23 Nov 2021 21:57:31 +0000 (16:57 -0500)]
kernel-yocto: conditionally enable stack protection checking on x86-64
The kernel Makfile uses pkgconfig to check for libelf when enabling
CONFIG_STACK_VALIDATION. We already have libelf in our DEPENDS, but
the kernel Makefiles hardcode 'pkgconfig', so fail to pick up our
pkgconfig-native binary that would report the correct flags and paths
for libelf support.
Rather than patching the kernel Makefile's to use pkgconfig-native,
we can use the KERNEL_EXTRA_ARGS variable to pass the definition of
HOST_LIBELF_LIBS via the kernel build commmand line.
We conditionally set HOST_LIBELF_LIBS based on "stack" being in
a newly introduced variable KERNEL_DEBUG_OPTIONS. The value of
HOST_LIBELF_LIBS is the same as pkgconfig-native would set in a
kernel build (but we cannot call pkgconfig at the point this
variable is set).
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This release adds feedback to the DMA buffer protocol, allowing smarter and
more dynamic DMA buffer allocation semantics. Other changes include
documentation improvements and improved testing infrastructure.
This is also the first release of wayland-protocols that do not include a
autotools build description.
Khem Raj [Mon, 22 Nov 2021 22:27:59 +0000 (14:27 -0800)]
image: Include psplash only when screen machine feature is enabled
base-image boots in degraded mode when using systems without display
system since there is no fb device detected and pslash service would
fail to start. Removing this image feature means that core-image-base is
complete for headless devices
[RP: tweak the false case so it builds] Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Mon, 22 Nov 2021 16:08:16 +0000 (16:08 +0000)]
bitbake.conf: Pass -D option to ranlib for determisim
Add the -D option to BUILD_RANLIB so that deterministic archives
are built for native/cross output. This improves the changes of hash
equivalence matches and hence build artefact reuse.
We don't need this in the target case since we compile binutils-cross
with an option making this the default.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Tue, 23 Nov 2021 13:14:35 +0000 (13:14 +0000)]
buildhistory: Fix do_package race issues
The buildhistory_list_pkg_files function uses data from do_package, not
do_packagedata. Usally the two are restored together but it may see
a half complete directory or other races issues depending on timing.
Rework the function so that it uses the correct task dependencies. This
should avoid races but means the data is only restored to buildhistory
if the do_package or do_package_setscene tasks are restored.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Lukasz Majewski [Tue, 9 Nov 2021 15:28:51 +0000 (16:28 +0100)]
glibc: ptest: Add running glibc time related test suite (Y2038) with ptest
This patch introduces new recipe - namely 'glibc-tests', which
builds and installs time related (to check if Y2038 support works) glibc
test suite to OE/Yocto built image.
It reuses code from already available 'glibc-testsuite' recipe,
which is run with 'bitbake glibc-testsuite -c check' and uses qemu
to execute remotely (via SSH) tests on some emulated machine.
This recipe installs time related glibc tests on some rootfs image.
Afterwards, those tests can be executed on the real hardware, to
facilitate validation of it with Y2038 problem compliance.
To test time related subset - one needs to call:
ptest-runner glibc-tests
then change the date after Y2038 threshold for 32 bit systems:
date -s "20 JAN 2038 18:00:00"
and then run ptest-runner again.
To facilitate debugging, source files are provided by default with
the unstripped debugging symbols. Such approach would reduce the
already complex recipe (as it inherits base glibc one), so there
is no need to also install *-dbg and *-src packages.
Signed-off-by: Lukasz Majewski <lukma@denx.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
wangmy [Mon, 22 Nov 2021 14:58:31 +0000 (22:58 +0800)]
libjpeg-turbo: upgrade 2.1.1 -> 2.1.2
Significant changes relative to 2.1.1:
Fixed a regression introduced by 2.1 beta1[13] that caused the remaining
GAS implementations of AArch64 (Arm 64-bit) Neon SIMD functions
(which are used by default with GCC for performance reasons) to be placed in
the .rodata section rather than in the .text section.
This caused the GNU linker to automatically place the .rodata section in
an executable segment, which prevented libjpeg-turbo from working properly
with other linkers and also represented a potential security risk.
Fixed an issue whereby the tjTransform() function incorrectly computed the
MCU block size for 4:4:4 JPEG images with non-unary sampling factors and
thus unduly rejected some cropping regions, even though those regions aligned
with 8x8 MCU block boundaries.
Fixed a regression introduced by 2.1 beta1[13] that caused the build system
to enable the Arm Neon SIMD extensions when targetting Armv6 and other legacy
architectures that do not support Neon instructions.
libjpeg-turbo now performs run-time detection of AltiVec instructions on
FreeBSD/PowerPC systems if AltiVec instructions are not enabled at compile time.
This allows both AltiVec-equipped and non-AltiVec-equipped CPUs to be supported
using the same build of libjpeg-turbo.
cjpeg now accepts a -strict argument similar to that of djpeg and jpegtran,
which causes the compressor to abort if an LZW-compressed GIF input image
contains incomplete or corrupt image data.
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
wangmy [Mon, 22 Nov 2021 14:58:33 +0000 (22:58 +0800)]
python3-mako: upgrade 1.1.5 -> 1.1.6
Fixed issue where control statements on multi lines with a backslash would
not parse correctly if the template itself contained CR/LF pairs as on
Windows.
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
wangmy [Mon, 22 Nov 2021 14:58:32 +0000 (22:58 +0800)]
mesa: upgrade 21.2.5 -> 21.3.0
New features:
VK_EXT_color_write_enable on lavapipe
GL_ARB_texture_filter_anisotropic in llvmpipe
Anisotropic texture filtering in lavapipe
VK_EXT_shader_atomic_float2 on Intel and RADV.
VK_EXT_vertex_input_dynamic_state on RADV.
VK_KHR_timeline_semaphore on lavapipe
VK_EXT_external_memory_host on lavapipe
GL_AMD_pinned_memory on llvmpipe
GL 4.5 compatibility on llvmpipe
VK_EXT_primitive_topology_list_restart on RADV and lavapipe.
ES 3.2 on zink
VK_KHR_depth_stencil_resolve on lavapipe
VK_KHR_shader_integer_dot_product on RADV.
OpenGL FP16 support on llvmpipe
VK_KHR_shader_float16_int8 on lavapipe
VK_KHR_spirv_1_4 on lavapipe
Experimental raytracing support on RADV
VK_KHR_synchronization2 on Intel
NGG shader based culling is now enabled by default on GFX10.3 on RADV.
VK_KHR_maintenance4 on RADV
VK_KHR_format_feature_flags2 on RADV.
EGL_EXT_present_opaque on wayland
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
wangmy [Mon, 22 Nov 2021 14:59:34 +0000 (22:59 +0800)]
python3-scons: upgrade 4.2.0 -> 4.3.0
NOTE: 4.3.0 now requires Python 3.6.0 and above. Python 3.5.x is no longer supported
Changelog:
- Default hash algorithm check updated for SCons FIPS compliance. Now checks for hash viability
first and then walks the tree to use the first viable hash as the default one. This typically
selects SHA1 on FIPS-enabled systems less than Python 3.9 as the new default instead of MD5,
unless SHA1 has also been disabled by security policy, at which point SCons selects SHA256
as the default. For systems running Python 3.9 and later, the hashlib bug has been fixed,
and SCons will once again default to MD5 as the preferred algorithm.
- Fix MSVS tests (vs-N.N-exec.py) for MSVS 6.0, 7.0, and 7.1 (import missing module).
- Add support for Visual Studio 2022.
- Fix reproducible builds. Restore logic respecting SOURCE_DATE_EPOCH when set.
- Fix version tests to work with updated scons --version output. (Date format changed)
- Fix issue #4021. Change the way subst() is used in Textfile() to not evaluate '$$(' -> '$',
but instead it should yield '$('.
- Change SCons.Platform.win32.get_architecture() to return platform.platform() when run in an
environment where neither: PROCESSOR_ARCHITEW6432 nor PROCESSOR_ARCHITECTURE is set.
This should fix platform tests which started failing when HOST_OS/HOST_ARCH changes
introduced by Aaron Franke (listed below) were merged.
- Further PCH updates. It's now recommended that env['PCH'] should always be a File node.
Either via return value from env.PCH() or by explicitly using File('StdAfx.pch').
- Added --no-ignore-skips to runtest.py. Changed default to ignore skips when setting
runtest.py's exit status. Previously would exit 2 if any tests were skipped.
Now will only exit 2 if user specifies --no-ignore-skips and some tests were skipped.
- Small fix to ensure CLVar default value is an empty list.
See MongoDB bug report: https://jira.mongodb.org/browse/SERVER-59656
Code contributed by MongoDB.
- Ninja - Fixed an issue where if you control-c and/or killed ninja while it was running scons to
regenerate build.ninja you would end up with no build.ninja file and have to rerun scons from scratch.
Code contributed by MongoDB.
- Define HOST_OS and HOST_ARCH in the environment for all platforms.
Before this change, these were only defined for Win32 and OS/2.
- Fix ninja tool to never use for_sig substitution because ninja does not use signatures. This
issue affected CommandGeneratorAction function actions specifically.
- Expanded ninja Mkdir to also support Mkdir actions.
- Added support for the PCH environment variable to support subst generators.
- Fix command line escaping for ninja dollar sign escape. Without escaping ninja properly,
the ninja file scons regenerate and callback invocations will lose the $ characters used in
the scons command line which ninja uses itself for escaping. For Example:
scons BUILD=xyz OTHERVAR=$BUILD
Prior to this fix, it would cause ninja to fail to escape the dollar sign, leading to the
single dollar sign being used as a ninja escape character in the ninja file.
- Added ninja API 'NINJA_FORCE_SCONS_BUILD' to force a node to callback to scons.
- Two small Python 3.10 fixes: one more docstring turned into raw
because it contained an escape; updated "helpful" syntax error message
from 3.10 was not expected by SubstTests.py and test/Subst/Syntax.py
- EmitterProxy rich comparison set is completed (checker warning).
Added __le__, __gt__, __ge__.
- Fix gcc/g++ tool failing if "gcc --version" returns text which fails
to_String conversion (i.e., not UTF-8) - failure happens when tool
initialization checks version. For gcc, the initial version string is
not translated, for the rest, don't convert, just consume raw and discard.
- Maintenance and doc: modernize some usage in Scanner package,
calling super(), switching some imitialization to comprehensions,
and code formatting. Docstring for scanner Base moved from
init-method to class-level so it's picked up by Sphinx.
Added new sconsign filenames to skip_entry_list in Scanner/Dir.py
- Change SCons.Scanner.Base to ScannerBase. Old name kept as an alias
but is now unused in SCons itself.
- Call Variables option converter consistently - the converter should
have access to the env if it needs to (issue #2064).
- Fixed the variables Add() method to accept a tuple for the variable
name the same way AddVariables() does (issue #3869).
- The premade validator PathIsDirCreate for for PathVariable now catches
the case where the directory could not be created due to permission
problems, allowing a more helpful error to be emitted (issue #2828)
- Maintenance: Python thread.setDaemon is deprecated in favor of
directly updating daemon attribute - update SCons to do this.
- Make sure when subst'ing a callable, the callable is called with
the correct for_signature value, previously it would be true even
if doing SUBST_RAW (issue #4037)
- Update Util/NodeList implementation to get rid of a workaround for
early Python 3 slicing issue that is no longer a problem.
- Rework some Java tests to skip rather than fail on CI systems, where
the working java is > v9, but a 1.8 or 9 was also found.
- Java updates: on Windows, detect more default JDK install locations.
On all platforms, more Java versions (up to 17.0 now). Add more information
on version selection to docs.
Update docs on JavaH tool in light of javah command dropped since 10.0.
Try to be better about preserving user's passed-in JAVA* construction vars.
- Start the deprecation of the qt tool, which refers to Qt3 (usupported
since around 2006). There's a deprecation warning added, initially
defaulting to disabled.
- Fix crash when scons is run from a python environement where a signal
is set from outside Python.
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
wangmy [Mon, 22 Nov 2021 14:59:33 +0000 (22:59 +0800)]
systemtap: upgrade 4.5 -> 4.6
support for 64-bit RISC-V architecture, liveness analysis for guru-mode write operations,
bpf syscall_any and abort() tapsets, bpf foreach iteration of multi-key arrays,
return of inter-cpu output ordering
Changelog is as follows:
= SystemTap frontend (stap) changes
- stap-prep now tries to download the main kernel debuginfo file from
a debuginfod server, if configured.
= SystemTap backend changes
- SystemTap has added support for the 64-bit RISC-V architecture.
- SystemTap now uses DynInst to perform a liveness analysis on
target variables and warn when a guru-mode modification to a variable
will have no effect. The liveness analysis is currently done on
x86_64, PowerPC, and AArch64.
- The kernel-user relayfs transport again sorts messages into a total
time order across CPUs. High output-volume scripts may need a
larger "-s BUF" parameter to reliably transfer. "-b" bulk mode
is also available again as an alternative.
- The bpf backend now supports foreach iteration in multi-key associative arrays.
= SystemTap tapset changes
- Updated syscall_any tapset mapping to include newer syscalls.
- syscall_any tapset can be used by the bpf backend.
- abort() tapset can be used by the bpf backend.
= Known issues with this release
- There are known issues on kernel 5.10+ after adapting to set_fs()
removal, with some memory accesses that previously returned valid data
instead returning -EFAULT (see PR26811).
- An sdt probe cannot parse a parameter that uses a segment register.
(PR13429)
- The presence of a line such as
*CFLAGS += $(call cc-option, -fno-var-tracking-assignments)
in older linux kernel Makefile unnecessarily reduces debuginfo quality,
consider removing that line if you build kernels. Linux 5.10+ fixes this.
= Bugs fixed for this release <https://sourceware.org/PR#####>
6562 $SYSTEMTAP_DEBUGINFO_PATH does not work
15724 stapdyn looking for libdyninstAPI_RT.a
26839 Systemtap build failures with clang
27820 abort() tapset not implemented in the bpf mode
27829 support for floating point values passed through sdt.h markers
27864 loc2stap.cxx assertion failure on loc_unavailable type location, rawhide
27881 failed to extend vma mapped entry when the address is adjacent
27903 handle f33 glibc $$parms
27932 List Python as a prerequisite in README
27933 Use of unitialized functioncall synthetic field in
27934 failure to attach statement
27940 The /* pc=0x... */ is no longer printed by "stap -v -L 'kernel.function("*")'
27942 testsuite/systemtap.base/perf.sh drop bashism
27984 stap skipping partially-inlined instance, but it is not inline function actually
28070 extend vma end address to the different module
28079 adapt to kernel 5.14 task_struct.__state change
28084 autoconf-x86-uniregs.c compile failled with -Werror cause STAPCONF_X86_UNIREGS missing
28140 kernel panic on tracepoint activation in stap module
28184 task_fd_lookup failed on linux 5.11
28244 linux objtool imposes symbol length limits on generated function names
28384 finish nfs_proc tapset port 4.3 string server_ip
28443 Provide syscall_any tapset for bpf
28449 loss of cross-cpu output ordering
28544 procfs_bpf.exp regression due to string handling error
28557 module kprobe insertion on modern kernels
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Mon, 22 Nov 2021 15:32:36 +0000 (15:32 +0000)]
buildhistory: Fix srcrevs output
The code was assuming that the a recipe with only one srcrev wouldn't "name"
it. This isn't the case as the glibc or bzip2 recipes show, you can have
a single srcrev which is named.
We can pull the data from the fetcher and in fact we already have it, we just
need to handle the "default" case and make that code the default for all srcrev
regardless of length.
[YOCTO #14017]
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Joshua Watt [Fri, 19 Nov 2021 02:12:49 +0000 (20:12 -0600)]
classes/crate-fetch: Ensure crate fetcher is available
Reworks the crate fetcher class to have it install the fetcher at recipe
finalization so that it is always available before SRC_URI is expanded.
In addition, override the value of SRCPV to also install the fetcher
when SRCPV is expanded so that AUTOREV works.
[YOCTO #10867]
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Process all systemd-sysusers configuration files in order to create
users/groups at build time. systemd-sysusers would try to create them at
run-time, but for read-only rootfs that's not possible and results in
warnings from different services:
systemd-udevd[166]: /lib/udev/rules.d/50-udev-default.rules:39 Unknown group 'render', ignoring
systemd-udevd[166]: /lib/udev/rules.d/50-udev-default.rules:40 Unknown group 'render', ignoring
systemd-udevd[166]: /lib/udev/rules.d/50-udev-default.rules:42 Unknown group 'sgx', ignoring
Signed-off-by: Vyacheslav Yurkov <uvv.mail@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Pgowda [Mon, 15 Nov 2021 14:03:40 +0000 (06:03 -0800)]
rust-cross: Replace TARGET_ARCH with TUNE_PKGARCH
rust-cross-* imported from meta-rust has incorrect signatures,
depending on MACHINEOVERRIDES making it effectively MACHINE_ARCH
as shown by sstate-diff-machines.sh:
Mingli Yu [Wed, 17 Nov 2021 02:16:23 +0000 (10:16 +0800)]
wic: use shutil.which
Use shutil.which to find the executable instead to silence the below warning:
$ cat tmp/work/intel_x86_64-poky-linux/core-image-base/1.0-r5/temp/log.do_image_wic
[snip]
DEBUG: Executing shell function do_image_wic
/path/layers/oe-core/scripts/wic:27: DeprecationWarning: The distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for potential alternatives
from distutils import spawn
INFO: Creating image(s)...
[snip]
[RP: Added conversion for missed function reference] Signed-off-by: Mingli Yu <mingli.yu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Andres Beltran [Thu, 18 Nov 2021 00:04:02 +0000 (00:04 +0000)]
create-spdx: Fix key errors in do_create_runtime_spdx
Currently, the do_create_runtime_spdx task fails with a Key Error if a
dependency is not contained in the package providers dictionary. Add a
check before using "dep" as a key in "providers".
Signed-off-by: Andres Beltran <abeltran@linux.microsoft.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Saul Wold [Wed, 17 Nov 2021 18:08:13 +0000 (10:08 -0800)]
create_spdx: ensure is_work_shared() is unique
There is a function with the same name is_work_shared() in the archiver class
this causes a conflict when both classes are included. Use work-shared as the
check in WORKDIR to allow for other packages beyond the kernel and gcc that
use a common shared-work source directory.
Signed-off-by: Saul Wold <saul.wold@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Daniel Gomez [Thu, 18 Nov 2021 22:06:09 +0000 (23:06 +0100)]
os-release: Add DISTRO_CODENAME as vardeps for do_compile
DISTRO_CODENAME is part of VERSION variable but not used as dependency
for do_compile task. Append it to the vardeps list to rebuild in case it
changes.
Signed-off-by: Daniel Gomez <daniel@qtec.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
busybox: drop 0001-Use-CC-when-linking-instead-of-LD-and-use-CFLAGS-and.patch
This was added 10 years ago, is almost certainly non-upstreamable
and it isn't clear what the issues it aims to fix are:
the AB revealed no problems when the patch is removed.
Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
