The default CONNECTIVITY_CHECK_URIS uses "https://yoctoproject.org/connectivity.html"
which redirect to "https://www.yoctoproject.org/connectivity.html".
Some network configurations with proxies or restricted internet access
don't handle HTTP redirects properly during the sanity check phase,
causing build failures with:
ERROR: OE-core's config sanity checker detected a potential misconfiguration.
Either fix the cause of this error or at your own risk disable the checker (see sanity.conf).
Following is the list of potential problems / advisories:
Fetcher failure for URL: 'https://yoctoproject.org/connectivity.html'. URL doesn't work.
Updated the default URL to use the final destination directly to avoid
redirect-related connectivity check failures.
Also updated SDK test cases in https.py to use the corrected URL for
consistency.
(From OE-Core rev: bd624ebbcf4e6d7a24c4ab232ca2e138b1ac3433)
Signed-off-by: Deepak Rathore <deeratho@cisco.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(cherry picked from commit 60cdf960a3560f391babd559737f1afb31fb2c5c)
Signed-off-by: Deepak Rathore <deeratho@cisco.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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
Most ptests run on on riscv64 but for some reason python3 hangs. Move
it to the problem list until this is resolved so we can establish a
"known to work" baseline.
(was still going after 42000s, long after everything else finished)
(From OE-Core rev: adc448b19e80f6343050f4c527acc63a161c88ca)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is needed for rpm reproducibility, as otherwise libmagic
will call an external lzip executable, which is both
non-threadsafe, and non-deterministic w.r.t sysroot presence.
(From OE-Core rev: 0e4bde86e1aa499274fc85d01d36a74c3401762e)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
With changes to gcc-runtime around improving debugging, python modules
are needed but this pulls in bash which breaks the tests.
Add an exclusion to the no-gplv3 include file to handle this.
(From OE-Core rev: 803060fa4e8fe98ac8f987b80162110d06788946)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Create a no-gplv3.inc file based upon knowledge currently encoded into one
of the selftests.
There is a risk that people try and take this idea too far, or have unrealistic
expectations. That said, it would be better to collect this knowledge together
in one location rather than handling it piecemeal.
Therefore move the configuration information from the test into a common
incude file.
(From OE-Core rev: fb822fb2029c69934cf43073f95b396c2d60298e)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There are two types of cases: executables and POSIX shell scripts.
All test cases PASS.
Add xz-ptest to PTESTS_FAST because test duration less than 30s
on qemux86-64.
root@qemux86-64:~# ptest-runner xz
START: ptest-runner
2024-01-26T03:32
BEGIN: /usr/lib/xz/ptest
=== test_bcj_exact_size.c ===
PASS: test_exact_size
PASS: test_empty_block
(From OE-Core rev: 2704983f972e4fe1d4e0bee8491a07eb4f629346)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
1. Patch changes:
0004-Move-sysusers.d-sysctl.d-binfmt.d-modules-load.d-to-.patch
is removed because it has no real effect now. The /lib is now
/usr/lib because 'usrmerge' is a required distro feature for systemd.
0002-binfmt-Don-t-install-dependency-links-at-install-tim.patch is
refreshed for the new version to avoid patch-fuzz issue.
2. root user's home directory now defaults to "/root":
The sysuers.d/basic.conf is still modified to respect the ROOT_HOME
value, so if users set ROOT_HOME to "/home/root", the behavior is the
same as before. However, this is only for backward compatibility. With
this patch, The ROOT_HOME value is set to "/root" in init-manager-systemd.inc.
This is because systemd's source codes are hardcoding "/root", and other
values are not officially supported. See the list below.
$ grep -rl '"/root"' src/ | grep -v 'src/test'
src/core/namespace.c
src/basic/user-util.c
src/nss-systemd/nss-systemd.c
src/nspawn/nspawn.c
src/firstboot/firstboot.c
src/shared/userdb.c
src/shared/user-record.c
$ grep -rl /root network/ factory/ sysctl.d/ sysusers.d/ rules.d/ tmpfiles.d/ units/ xorg/ tools/
sysusers.d/basic.conf.in
tmpfiles.d/provision.conf
units/emergency.service.in
units/rescue.service.in
tools/list-discoverable-partitions.py
Previously, the recipe was just substituting sysusers.d/basic.conf.in,
which is not enough to be treated as 'fully support'. I deliberately put
a warning message in do_install to warn users about non "/root" ROOT_HOME
value. Don't remove it until all above places are handled.
3. cgroupv2 is now the default.
cgroupv2 is the default for systemd for many years and it's the default
for distros such as ubuntu and fedora. Let's also use it as the default.
(From OE-Core rev: ebafe463799b39025a0b24a0a14a2f02b6de9bac)
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add recipe for yamllint. There is an upcoming change in u-boot where
the binman tool is now configured to call yamllint to verify the configs
during compile time.
There was a previous patch a year ago from Trevor Woerner that never
made it into oe-core. This patch is a reworking of his patch but
pointing to a newer version.
(From OE-Core rev: 128cfc5222752a6337a9cbb9bc9023c13ee19f2f)
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We can drop the mips workaround patch since there were fixes in 8.2.0.
The build system changed and we should drop cross.patch and replace it with
explicit settings for cross-prefix, and host-cc. To make that work we need
to indicate we don't use a cross pkg-config.
PIE isn't availale for mingw so tweak PACKAGECONFIG accordingly.
(From OE-Core rev: 8917fa10b8afb1413b34a6134beea129e416f8c6)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
As agreed upon in the bug triage meeting, disable mdadm ptest for the time being
Related: [Yocto #15181] [Yocto #15159] [Yocto #15308] [Yocto #15309]
(From OE-Core rev: 22ae573aa1a1244d4dea498d4fa4fcdf195bedf8)
Signed-off-by: Pavel Zhukov <pavel@zhukoff.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This reverts commit d2b445384d.
Revert this commit since:
- some systems using oe-core master may still be using kernels from
before 5.6 pulled in the rng-tools algorithm, and
- some hardware platforms may not have a hardware random number generator
and could therefore need to run rngd to avoid long boot-time initialization
due to a depleted entropy pool.
(From OE-Core rev: 828afafb3bff54079fcba9bdab2ec87ac13e4ce6)
Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Nothing in oe-core depends on rng-tools anymore:
e7e1bc43ca rng-tools: splitting the rng-tools systemd/sysvinit serivce as a package
so move it to meta-oe for people who still want to run rngd
as a service for some reason or for those who want to run rng-test.
(From OE-Core rev: 9a651e5bc2492cf864261e8f17e4cbe34d6d48ce)
Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
shadow 4.14.x adds a number of libraries it dynamically links with
(md, bsd, attr). This causes troubles in setscene tasks where
shadow executables are used (such as useradd), as pulling in
the needed dynamic libraries needs unpleasant special-casing.
(From OE-Core rev: 495ff95eae14a91c94187f78a0b30c7957c9b168)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
