After update to 2.7.0, it fails to start ptest of ruby with errors:
| ./test/runner.rb:11:in `require_relative': cannot load such file --
/usr/lib64/ruby/ptest/tool/test/runner (LoadError)
and
| test/rdoc/test_rdoc_attr.rb: cannot load such file -- rdoc/version
| test/did_you_mean/spell_checking/test_key_name_check.rb: cannot load
such file -- /usr/lib64/ruby/ptest/lib/did_you_mean
Install the required files for the ptest.
(From OE-Core rev: be161be40c88fbac8ac17776daf3bf178a2e8f5e)
Signed-off-by: Kai Kang <kai.kang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Only md5sum and sha256sum are currently provided by HOSTTOOLS. Trying
to use any other checksum conversion will result in a build failure.
Fix it by adding other supported checksum utilities to HOSTTOOLS.
(From OE-Core rev: 78155e5fcff9362049b576d20e31c3519c48485b)
Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We've found we need a way to cause a change in signatures and move
to a new hash 'namespace' with hashequiv. This introduces a variable
which allows us to do this.
(From OE-Core rev: 1c2d5aeae2fa2dfc16bc60b6cf0b310f826337fd)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
file /usr/share/man/man3/history.3 conflicts between attempted installs of libedit-doc-20191231+3.1-r0.corei7_64 and readline-doc-8.0-r0.corei7_64
(From OE-Core rev: 23ad05b98a2e1ced47aac3b1d7689c7146ff8c91)
Signed-off-by: Jeremy A. Puhlman <jpuhlman@mvista.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This can be useful with a more specific, targeted and robust set of ptest
packages; the benefit is that ptest regressions are caught as they happen
and can be more easily traced to changes that caused them.
The existing AB ptest image continues to be expected to fail, my observation
of the AB runs is that the full set of ptests is not robust enough
(particularly around socket/network related tests) and sporadically fails
in random places. This can probably be addressed by making ptests exclusive
to a worker (e.g. there is no other workload happening at the same time as
ptests).
(From OE-Core rev: 102afcc7ea7d7673183f272a29ab233084ad168b)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Switch to using the tarballs of tagged releases.
WHENCE changed due to firmware filename changes.
(From OE-Core rev: 746438e5e75d9fd4ccb461f92887a7b02a1c27d1)
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Even versions are shipped in Ubuntu LTS and Debian releases.
(From OE-Core rev: e190bf44ed2aef03ce8922dfbb0bb90a762bb41d)
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Sadly, meson makes it very difficult to install tests: the test
configuration is written into host-specific binary files, which
can't be transferred to the target. (unlike autotools where
at least everything happens via Makefiles which can be patched
and tweaked via sed and env vars)
So the configuration has to be entirely recreated in shell.
I managed this for wayland, but weston proved too difficult.
I had filed bugs asking upstream to make the tests installable:
https://gitlab.freedesktop.org/wayland/wayland/issues/146https://gitlab.freedesktop.org/wayland/weston/issues/368
(From OE-Core rev: 296ee10bb8491278f050fb9d55f42b0bcf663382)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
ClutterActors can crash with strange segfaults when built without the GDK
backend but run ontop of GDK. To fix this let's add a PACKAGECONFIG to
enable/disable GDK backend support and enable it by default.
(From OE-Core rev: cb03ccec2926eae6d8eaf1606a7d11fcc54f1820)
Signed-off-by: Alistair Francis <alistair@alistair23.me>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This reverts commit 52971eeaaf.
The original problem was later fix by
psmisc: revert to default autopoint exclusion
(From OE-Core rev: 007df9bba56f885dd847b2f8b24fb250bcdd386f)
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There are no users left in OE-core.
(From OE-Core rev: 2c5d140a8a2b794b36ed9535afc278cec2ef306f)
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Avoid:
qemux86-64 psplash-systemd[135]: Error unable to open fifo
by adding the missing dependency on /run/ where the fifo resides.
Also, psplash-systemd requires psplash-start, not the other way around
as the splash creates the fifo which the other then needs to open.
(From OE-Core rev: e31ad1b58e8dbac2e299bc0cb872c3a82db14717)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Make use of the recently added systemd support in psplash. The utility
psplash-systemd communicates boot progress to the splash screen. The
splash is disabled once systemd consideres the system fully booted
(progress is at 1.0). Note that this can take a while if systemd is
stuck on a failing unit.
This change adds two systemd services. One service starts psplash itself
(psplash-start.service) and the second service starts the helper utility
psplash-systemd (psplash-systemd.service). The units are written such
that psplash-systemd.service can be used indepenendenly. This is useful
when starting psplash in initramfs (not using systemd).
(From OE-Core rev: b4063b16082604554c7c19b369ebddd27061f372)
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Several variables used by the task are not included in the hash, as highlighted
by recent changes to MAINTAINERS not causing rebuilds. Fix this.
(From OE-Core rev: 0bfb2e984062e2a00f8989d26aebb89b112d81d2)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Ensure that the plain variable X is also added to the dependencies
as well as X_<pkg>.
Allow the funciton to be called with a different variable list too.
(From OE-Core rev: c392401e10ff43d10b7e57c9d552522a02c91878)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There are two primary reasons for this:
1. mdadm test suite tends to work like this
do_action
sleep arbitrary_amount
check_result
This is unreliable, and arbitrary_amount may or may not be enough.
I have confirmed this by increasing the amount, and seeing more tests
pass than before.
2. The test suite aborts half way through because one of the mdadm binaries
segfaults. This indicates that upstream isn't actually running the suite
anymore, and in this situation we shouldn't be relying on it either.
(From OE-Core rev: e21021dc00ec76c76cc361e15bc83a89083c9e72)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Particularly:
1. set $dir, so supplementary utilities can be found
2. disable integrity checks as they take more time than any other test
(From OE-Core rev: a8983d659b27219a0d70e56882727ceddd0f4331)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
valgrind's test suite isn't generally run by upstream on arm64,
so let's simply disable the failing test and establish a set
that works.
(From OE-Core rev: f9c953295a44f74c6394d155dfa080384f637806)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This addresses a ptest failure in particular that the submitted
patch caused.
(From OE-Core rev: 4e9d46a570f7d7d1981a24f90c5e919b1f73c8b5)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
5.4 is the next LTS kernel, so we drop the 4.19 recipes from master.
(From OE-Core rev: bb5c2b8d6a875a773271d7cae08f55f0fd8e9156)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This avoids warnings due to kernel version mismatches
(From meta-yocto rev: 4d8122bca9e5a8788521537610411fe59b1ba8a6)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the SRCREVs for the h/w references to v5.4.20, which includes
the binutils fix for perf.
(From meta-yocto rev: 9fcac872e5f2cc05409cb06640c0f625bea6e8ba)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
5.4 is the new LTS kernel, so we drop the 4.19 bbappens as the 4.19
kernel will be removed.
(From meta-yocto rev: 36e7756b89a2adb0df470e862a71fbfda98a8682)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Ensure that the 5.4 LTS kernel is the preferred version for all poky
boards.
(From meta-yocto rev: 966faa29f0540f9262704621b9f639fb1129a781)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Tested with cortex-a9 machine
* before this patch -> no gir
* after: gir was built without issues
(From OE-Core rev: 0f4f69d1b238b2c22c30ef306358a055d3aa39cb)
Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
To make the native python3 always used,
- Use sed one-liner instead
- Add substitution for ${S}/scripts/bpf_helpers_doc.py to fix the
following warning.
File "/usr/lib/python3.6/sysconfig.py", line 421, in _init_posix
_temp = __import__(name, globals(), locals(), ['build_time_vars'], 0)
ModuleNotFoundError: No module named '_sysconfigdata'
This issue is first reported by Joel Stanley <joel@jms.id.au>
The sed one-liner is credited to Anuj Mittal <anuj.mittal@intel.com>
(From OE-Core rev: 3f93173130a94310255389cfc62c67102a4fb21b)
Signed-off-by: He Zhe <zhe.he@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This override was applying to binutils-native meaning it would behave differently
depending upon the host it was building on. This is not a good idea and we have
tests to detect it which failed:
oe-selftest -r sstatetests.SStateTests.test_sstate_32_64_same_hash
binutils-native already enables all targets so we can avoid issues by not setting this
option in the native case.
(From OE-Core rev: bbf9e8ae5e0ce2968e4fef071d3de3ddfdc7463c)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Details of changelog [1]
Removing bfd/ld patch to enable PE targets, instead use
specific emulations via --enable-targets for x86_64
Re-arrange/forward-port patches and upgrade libctf configure to libtool 2.4 patch
rpaths are no longer emitted into elfedit/readelf therefore no need of
chrpath anymore
Instead of pre-generating configure scripts and house them in libtool
patch, generate them during configure. This also ensures that we do not
patch configure directly but rather the sources which generate it
Package newly added libctf library
[1] https://lists.gnu.org/archive/html/info-gnu/2020-02/msg00000.html
(From OE-Core rev: 82f7d5cfc2ab02f39b69c0f8697d660936422d4a)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Cc: Christopher Clark <christopher.clark6@baesystems.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Drop amd64 patch, the bsfq has been replaced with bsfl for count_trailing_zeros
Forward port rest of patches to 6.2.0
(From OE-Core rev: 35c052db4e081d363bcca350383adb0ac8c321d3)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Installing on centos7, which the extended version of the
buildtools tarball is supposed to fix and with reproducable
builds turned on, all the time stamps are for epoch. This
results in the following output for every file:
tar: ./sysroots/x86_64-pokysdk-linux/usr/include/c++/9.2.0/cstdalign: implausibly old time stamp 1969-12-31 16:00:00
tar: ./sysroots/x86_64-pokysdk-linux/usr/lib/libstdc++.so.6: implausibly old time stamp 1969-12-31 16:00:00
Ignore the timestamps during the uncompession step.
(From OE-Core rev: 319ca22ea4465c56c63730847378a7aee4f5935a)
Signed-off-by: Jeremy Puhlman <jpuhlman@mvista.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I spotted this by noticing ptests started to unexpectedly pass,
which shouldn't happen yet.
(From OE-Core rev: 1cd6e9a8fdfef927916c6cea2371fc0430b1ffdf)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Now that the 5.4 recipes are available, we bump the default versions
to use them.
(From OE-Core rev: c250dbd2a68048f83837e7cbdfb53bc38623e4a2)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Integrating the -rt11 changes into the linux-yocto-rt branches:
e3a0470f1ebe (HEAD -> v5.4/standard/preempt-rt/base, origin/v5.4/standard/preempt-rt/base) v5.4.19-rt11
2748be173948 bpf/stackmap: Don't trylock mmap_sem with PREEMPT_RT and interrupts disabled
d721d73cb752 bpf, lpm: Make locking RT friendly
dc53d4c7fad3 bpf: Prepare hashtab locking for PREEMPT_RT
a13a53a8ae75 bpf: Factor out hashtab bucket lock operations
96a25d8a5a2d bpf: Use migrate_disable() in sys_bpf()
bb8a96d7e701 bpf: Use migrate_disable() in hashtab code
615cc5998661 bpf: Use migrate_disable/enable in array macros and cgroup/lirc code.
c3a06a1ab3d4 bpf/tests: Use migrate disable instead of preempt disable
0717741a61e6 trace/bpf: Use migrate disable in trace_call_bpf()
b528161bf4e0 bpf: Use BPF_PROG_RUN_PIN_ON_CPU() at simple call sites.
a3b5b903f04f bpf: Replace cant_sleep() with cant_migrate()
dd708fd4fb18 bpf: Provide BPF_PROG_RUN_PIN_ON_CPU() macro
6ccad68939c7 bpf: Don't iterate over possible CPUs with interrupts disabled
055b62ad0b2c perf/bpf: Remove preempt disable around BPF invocation
7848f4a45054 bpf/tracing: Remove redundant preempt_disable() in __bpf_trace_run()
caf8a5d6b42f bpf: Update locking comment in hashtab code
2ddd1653369d sched: Provide cant_migrate()
37b6c8361d28 sched: Provide migrate_disable/enable() inlines
2a1c4980a1e6 drm/i915/gt: use a LOCAL_IRQ_LOCK in __timeline_mark_lock()
84a119be5c68 v5.4.19-rt10
bb5e8418fb66 v5.4.17-rt9
bf976f5d86e7 locallock: Include header for the `current' macro
7a00b04683bd mm/memcontrol: Move misplaced local_unlock_irqrestore()
b647f8807169 sched: migrate_enable: Remove __schedule() call
2b321530c794 sched: migrate_enable: Use per-cpu cpu_stop_work
22b448083286 locking: Percpu-rwsem rewrite
f5d550cc9950 v5.4.17-rt8
(From OE-Core rev: dd407673d7091cb49ed41bef750c33bbcb53a1c3)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
