Use oe.path.canonicalize() to canonicalize the paths in
PSEUDO_IGNORE_PATHS before passing them to pseudo. This is needed since
pseudo will compare them to paths that are canonicalized.
(From OE-Core rev: 1f2a497daa09cf3459e27ad6e0e8513938b52c79)
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
oe.path.canonicalize() is used to canonicalize paths (i.e., remove
symbolic links and "..", and make them absolute). It takes a string
with paths separated by commas, and returns the canonicalized path in
the same format.
(From OE-Core rev: 282b19c0e27488ec119f00fb2542ffdc1af54e2a)
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
None is a bad choice of return value for functions used in variables
(strings) as a failure results in concatination errors. Use a string
with a clear meaning that can be searched for instead.
(From OE-Core rev: c04f04e714ede5d3904058ec82459139ed5e42fa)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The get_hash() function is used to decide if the base configuration has changed
and hence whether a reparse is required. The vardepvalue flag's value was not
expanded but it is often used in contexts like:
METADATA_REVISION = "${@base_detect_revision(d)}"
METADATA_REVISION[vardepvalue] = "${METADATA_REVISION}"
which in it's unexpanded form means reparsing doesn't happen when it should
as the data appears unchanged. Update get_hash to expand the values of
vardepvalue so reparsing works as expected. This avoids basehash mismatch
errors such as the one recently caused by using METADATA_REVISION in poky.conf's
DISTRO_VERSION variable. The issue there could be exposed by a recipe using
DISTRO_VERSION with the sequence:
bitbake os-release
<change the revision of the metadata with a dummy commit>
bitbake os-release -C install
which was caused because METADATA_REVISION changed but the metadata didn't reparse.
(Bitbake rev: 26ccf1575aef2d6e2d7717d3bd10b1ed0d5a777d)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a package for libopcodes, since, like libbfd, it is needed by
perf. Without separate packages for these libraries, all of the
binutil tools get added as well.
(From OE-Core rev: 514b595bda487ff74ae16539d716628a1d0be8af)
Signed-off-by: Alan Perry <alanp@snowmoose.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
lttng-modules doesn't currently build against the lastest 5.10-rc
versions.
Upstream lttng does have fixes for the issues, but hasn't done a
release that contains them yet. There are other patches on the
2.12.x branch, but I've skipped them for now as they aren't
necessary for 5.10 builds, and can be picked up with the next
full update.
We also bump the dev-upstream hash to make them easier to pickup
for those building from git.
(From OE-Core rev: 47201e98bb293d59c5d41986d066fd7614b914fa)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Integrating the following commit(s):
375e7ee20260 Linux 5.4.78-rt44
c948a34d2755 Linux 5.4.77-rt43
8189406f8f2b Linux 5.4.74-rt42
0856261877e2 timers: Don't block on ->expiry_lock for TIMER_IRQSAFE
416edb155e5d ptrace: fix ptrace_unfreeze_traced() race with rt-lock
6bd85935ab11 mm/memcontrol: Disable preemption in __mod_memcg_lruvec_state()
57ada856a2a8 net: Properly annotate the try-lock for the seqlock
1c80ecf69d2d Linux 5.4.74-rt41
d4318c110dc6 Linux 5.4.70-rt40
bdfc6168388d Linux 5.4.69-rt39
b6e0ef250594 Linux 5.4.66-rt38
151876f794fc Linux 5.4.61-rt37
4bdac3f47b53 Linux 5.4.59-rt36
cf9b41798238 Linux 5.4.58-rt35
631b98ae597b Linux 5.4.55-rt34
77d701a69ebb Linux 5.4.54-rt33
130cf1b82691 rwsem: Provide down_read_non_owner() and up_read_non_owner() for -RT
6ab4141069fc net: phy: fixed_phy: Remove unused seqcount
291d163db65a Bluetooth: Acquire sk_lock.slock without disabling interrupts
4c9f5d78fed4 workqueue: Sync with upstream
(From OE-Core rev: dfae903dd2538d57cc75e3b8b731515deb7f5526)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(From OE-Core rev: bb433833d2ae7b87d18dfae5635eac9097ecc9b7)
Signed-off-by: Mark Jonas <toertel@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This ensures that busybox init can generate matching tty's in inittab as
system defines, secondly resepcts USE_VT for creating virtual ttys
(From OE-Core rev: 7dddda7a00108f9a61da4a869514a32b9f42d16a)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
qemuriscv enables hvc0 along with ttyS0, however its not enabled in
/proc/consoles, getty tries to enable it in inittab and erroring out
Fixes below message with sysvinit
INIT: Id "hvc0" respawning too fast: disabled for 5 minutes
(From OE-Core rev: 8a6559f1561ca6b7719bb46fc446db46d8086ea3)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Otherwise, valgrind significantly slows them down, and actually
even causes ptest timeouts on arm64.
(From OE-Core rev: 483ca253cc25f928759263f9f3f2b3699e82252b)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The tests' output is non-deterministic and sometimes
doesn't match the sample output. This has been reported at
https://bugs.kde.org/show_bug.cgi?id=430321
(see also an earlier related bug https://bugs.kde.org/show_bug.cgi?id=358213)
Until upstream figures out how to fix this, let's not run the tests.
(From OE-Core rev: 7f7d2fa18267090891754d976cbc3e628324d3dd)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Because the name of CVE patch is wrong, cve-check-tool cannot get the correct CVE result. Rename the patch name.
(From OE-Core rev: 422f9af7d0f7de7a2e933154853e7a281f98ab93)
Signed-off-by: Zang Ruochen <zangrc.fnst@cn.fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Currently there's no easy way to override this part as it's hardcoded
into the EXTRA_OEMAKE var. This change makes it possible to manipulate
the list of subdirs in a more fine graned and future oriented manner.
(From OE-Core rev: 1ca2b21cb7d638f36860bd16a90c1fb8238d4552)
Signed-off-by: Anatol Belski <anbelski@linux.microsoft.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Engines are installed in a slightly different path, and
the host type doesn't precisely match in x86_64
Co-authored-by: Paul Eggleton <paul.eggleton@microsoft.com>
Co-authored-by: Deepak Rawat <derawa@microsoft.com>
(From OE-Core rev: 166bb89f6d97495b6522786182b4f9623acd7ff4)
Signed-off-by: Luca Boccassi <luca.boccassi@microsoft.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These both now work on arm64, so add them to the dependencies.
(From OE-Core rev: 6b350db4ef9eaff10ee274ff7d28d2e6761c532a)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
systemd-boot works on 32-bit and 64-bit Arm targets (assuming the
firmware does EFI, obviously), so allow it to be built.
(From OE-Core rev: 3325992e66e8fbd80292beb4b0ffd50beca138d8)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Also build and deploy the EFI stub. SYSTEMD_BOOT_EFI_ARCH can be dropped
as image-uefi.conf now sets EFI_ARCH.
Changes originally taken from meta-intel.
(From OE-Core rev: 00191504bd9321334a5c01b95179ed15b063f1b6)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Refactor EFI_BOOT_IMAGE so that the EFI name for the architecture
is exposed as EFI_ARCH, so that other recipes (such as bootloaders)
can reuse it.
(From OE-Core rev: d3bf2d0fbd50309d7cf8f066c258ba1ebdb05f47)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If we're not building syslinux, then there's no point building
syslinux-native.
(From OE-Core rev: 152dbd05c099ce50701466336a9c9642c98e4fe0)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Currently the syslinux recipe set COMPATIBLE_HOST to 32/64-bit x86.
Whilst this makes sense for the target binaries as syslinux is
x86-specific, this also affects the native recipe which should be able
to be built on non-x86 build hosts (for example, arm64 build host,
qemux86 target).
syslinux itself has a somewhat fragile build system but with care it is
possible to build the installer for native/nativesdk, and the bootloader
for target.
(From OE-Core rev: 7273e131bfc7de83df9e90697e7983d54b713798)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Upstream release notes:
'''
* 20.8 - 2020-12-11
- Revert back to setuptools for compatibility purposes for some Linux
distros (:issue:`363`)
- Do not insert an underscore in wheel tags when the interpreter version
number is more than 2 digits (:issue:`372`)
* 20.7 - 2020-11-28
- No unreleased changes.
* 20.6 - 2020-11-28
- Note:
This release was subsequently yanked, and these changes were included in
20.7.
- Fix flit configuration, to include LICENSE files (:issue:`357`)
- Make intel a recognized CPU architecture for the universal macOS
platform tag (:issue:`361`)
- Add some missing type hints to packaging.requirements (issue:350)
* 20.5 - 2020-11-27
- Officially support Python 3.9 (:issue:`343`)
- Deprecate the LegacyVersion and LegacySpecifier classes (:issue:`321`)
- Handle OSError on non-dynamic executables when attempting to resolve the
glibc version string.
"""
(From OE-Core rev: 7a074958be6e166e2de98bd39dc203f0d67a8d93)
Signed-off-by: Tim Orling <timothy.t.orling@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When using coreutils nativesdk (e.g. with buildtools-tarball) for
running oe-core builds, a number of recipes/classes/etc. expect xattr
support. This requirement is also expressed by the existing
PACKAGECONFIG_class-native default including xattrs.
(From OE-Core rev: 80d7debffdeed165006b26dcb89cffafaaecca06)
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
By default ncurses includes the values of LDFLAGS in its output
pkgconfig .pc files. This causes issues because OE includes options that
are specific to either the build host, or build configuration. These
options are not expected to be embedded in the pkgconfig output that is
installed.
Specifically this change resolves issues with uninative, where uninative
includes '-Wl,--dynamic-linker=' in LDFLAGS in order to force the
building and execution of native binaries against the dynamic linker
provided by uninative. This path is specific to TMPDIR at the time of
build, such that the installed files (and the associated sstate) have
this path. This prevents the sstate from being portable across build
directories/hosts.
(From OE-Core rev: ef960d14bd9cecb9a3b50994636fbd455f06104a)
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add the seccomp PACKAGECONFIG option to allow building seccomp features
in QEMU. The libseccomp library is available in additional layers (e.g.
meta-security).
Additionally this serves as a way to disable seccomp by default to avoid
the configure of QEMU automatically finding it (via pkg-config) on the
build host when building qemu-system-native and auto enabling the
feature.
(From OE-Core rev: 7c8245f41d43b5a267d51f3c7784536eee23fca2)
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
go 1.15 has reworked internal linker, which has resulted in regressions
in OE where native binaries generated using internal linker in some
cases result in corruption during populate_sysroot e.g. glide-native
crashing when used after relocation.
This improved reliability of native binaries working especially when
they use cgo or pie build modes
(From OE-Core rev: daf4856ea3ccafc05c808a34d4c6af2bfafea12f)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Cc: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: Konrad Weihmann <kweihmann@outlook.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When compiling gcc-runtime for i686 libatomic, libgomp and libitm are
compiled with additional '-march' and '-mtune' overrides. This typically
does not cause build errors (e.g. core2-32 tune), and results in less
optimally tuned outputs. However with specific TUNE_CCARGS (e.g. has
'-mfpmath=sse' but not '-msse*'), the build errors with conflicting
'-mfpmath' options.
This is caused by gcc-runtime specific configure scripts and Makefile
options that override by adding additional '-march'/'-mtune' args. OE
builds gcc-runtime differently to other build systems, and provides
target specific arch/tune options directly. As such, this change adds a
patch for gcc to remove the specific cases where the args are added.
(From OE-Core rev: d39b686cc5fcc89405ffeb560ea64b5d305b0608)
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Following other examples, only depend on syslinux when targetting x86.
(From OE-Core rev: c58fcc1379ca5755a5b670f79b75e94370d4943c)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This function is primarily *appending* configuration entries to the
overrides, it only gets it to ensure it's set at all, so doesn't belong
in the vardeps. Having a dependency on OVERRIDES means you cannot use a
bbclass like distrooverrides without changing the signatures of recipes
using this class.
(From OE-Core rev: fef74d3651d432977caef8fea54fc54bf2784a74)
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This function is primarily *appending* configuration entries to the
overrides, it only gets it to ensure it's set at all, so doesn't belong
in the vardeps. Having a dependency on OVERRIDES means you cannot use a
bbclass like distrooverrides without changing the signatures of recipes
using this class.
(From OE-Core rev: 8fad5db8c3275a0dc9fdb37761f2e9381e1413da)
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Include link to upstream report and the last autobuilder failure [1]
so it's easy to identify why this is needed in future.
[1] https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/1160/steps/8/logs/step1c
(From OE-Core rev: 28647f8e4fb5fe2e56f0609900187bc658ba9ccf)
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
On one of my buildservers I noticed perl do_install failing with the
following message:
| rm: cannot remove '<OEROOT>/tmp-rpb-glibc/work/armv8-2a-linaro-linux/perl/5.32.0-r0/image//usr/lib/perl5/5.32.0/*/CORE/libperl.so': No such file or directory
I tracked this down to shell being dash rather than bash not being able
to expand this glob in the middle of the filename. So replace the glob
expansion with the simpler one which works in all cases.
(From OE-Core rev: d1ea1b5c12120abdd085dc4eb69120af9258a99b)
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Refresh patches to apply to this update
Brings in following fixes
* 1e4204d5 use libc-internal malloc for newlocale/freelocale
* 36246b34 drop use of pthread_once in newlocale
* 37fcc13c lift locale lock out of internal __get_locale
* c53e9b23 fix misleading comment in strstr
* b67d56c7 drop use of pthread_once for aio thread stack size init
* 90ff0169 fix omission of non-stub pthread_mutexattr_getprotocol
* 56f0631d riscv64: fix inconsistent ucontext_t struct tag
* 50c7935c fix failure to preserve r6 in s390x asm; per ABI it is call-saved
* 738c4e94 s390x: derive float_t from compiler or default to float
* 821083ac implement reallocarray
* 29ff7599 implement realpath directly instead of using procfs readlink
* 5d464f52 fix mallocng regression in malloc_usable_size with null argument
* d046ec92 configure: do not use obsolescent form of test -a|o
* c5d118eb fix segfault in lutimes when tv argument is NULL
* 67f77462 netinet/in.h: add IP_RECVERR_4884 from linux v5.9
* d078f836 sys/fanotify.h: add new FAN_* macros from linux v5.9
* 3ba370fe bits/syscall.h: add __NR_close_range from linux v5.9
* badc5bb2 add missing personality values
* 6e989248 arm fabs and sqrt: support single-precision-only fpu variants
* c8c3e341 fix typo in INSTALL
* e2fa720b work around linux bug in readlink syscall with zero buffer size
* c17cda6d parse v3 or future-unknown zoneinfo file versions as v2+
* 585a0a78 explicitly prefer 64-bit/v2 zoneinfo tables
* debbddf7 fix regression in pthread_exit
* 3ab2a4e0 rewrite wcsnrtombs to fix buffer overflow and other bugs
* 233bb697 protect destruction of process-shared mutexes against robust list races
* d26e0774 pthread_exit: don't __vm_wait under thread list lock
* 167390f0 lift child restrictions after multi-threaded fork
* 34952fe5 convert malloc use under libc-internal locks to use internal allocator
* 8d37958d give libc access to its own malloc even if public malloc is interposed
* c1e5d243 drop use of getdelim/stdio in dynamic linker
* cbecda0b dlerror: don't gratuitously hold freebuf_queue lock while freeing
* 4ffa7068 fix vector types in aarch64 register file structures
(From OE-Core rev: b70b875c2f405f6481b1179419cf0f086fa31f53)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
destdir.patch
removed since it is included in 0.3.112
modify system-linkage.patch
(From OE-Core rev: 3b94e8c369960b0ed1e2949204a587a2952edf79)
Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
