Drop add-with-bisonlocaledir.patch as upstream (gnulib, not bison)
now determines the directory from datadir.
(From OE-Core rev: 8a89c77e5b5a7915b9cce4979ee8caa593847e51)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The latter is needed for pango update.
(From OE-Core rev: ee9f4567563a61e9f614e9405cf5480411890719)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Some of our tests may run NFS over UDP, so we don't want udp
support disabled.
Turn off that setting, and we can revisit if any side effects
are noticed.
(From OE-Core rev: 9f89fe4209850c46eedd4e3dd52104d1d5d423d2)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Integrating the following commit(s) to linux-yocto/5.8:
912adf166eb0 selftests/bpf: Prevent runqslower from racing on building bpftool
(From OE-Core rev: 57ffe4d073d27f410dbf0ac57ff6e4dcea8ab1e4)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Integrating the following commit(s) to linux-yocto-rt/5.8:
commit baee1af811ec9bd3e64990543b7cc85e77c8f50c (HEAD -> master)
Author: Bruce Ashfield <bruce.ashfield@gmail.com>
Date: Sun Aug 23 22:50:30 2020 -0400
linux-yocto/rt: enable kprobes by default
Traditionally kprobes and -rt haven't mixed well, but recent -rt
kernels support kprobes without issues.
lttng now requires kprobes to be enabled, or the following error
is thrown:
|
build/tmp/work/qemux86_64-poky-linux/lttng-modules/2.12.2-r0/lttng-modules-2.12.2/wrapper/kallsyms.c:20:3:
error: #error "LTTng-modules requires CONFIG_KPROBES on kernels >= 5.7.0"
| 20 | # error "LTTng-modules requires CONFIG_KPROBES on kernels >= 5.7.0"
| | ^~~~~
| make[3]: ***
[build/tmp/work-shared/qemux86-64/kernel-source/scripts/Makefile.build:280:
build/tmp/work/qemux86_64-poky-linux/lttng-modules/2.12.2-r0/lttng-modules-2.12.2/wrapper/kallsyms.o]
Error 1
By including the kprobes fragment into the -rt kernel by default, we
fix the issue.
(From OE-Core rev: 0ebbcbefc8c1a6731b81b7f1aba695a3665a256e)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Integrating the following commit(s) to linux-yocto/5.8:
5d66d1a67c8d arm64/perf: Fix wrong cast that may cause wrong truncation
Khem reported in some configurations that CONFIG_SCSI_VIRTIO was
throwing a warning in the final .config. That was due to the fact that
if debug or not is enabled, it switches between built-in and a module.
Either configuration is correct, so we add it to the non-hardware file
to inhibit it being reported by deefault.
The following meta branch commit resolves the issue:
commit 96e8f5e330f5a8f87deda0f1bae71af31c578ce9 (HEAD -> master)
Author: Bruce Ashfield <bruce.ashfield@gmail.com>
Date: Sat Aug 22 22:19:13 2020 -0400
virtio: declare CONFIG_SCSI_VIRTIO as non-hw
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
(From OE-Core rev: 74188412ae3019235151f3e606a470ff27c7ed63)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Now that the 5.8 recipes are available, we bump the default versions
to use them.
(From OE-Core rev: 61b7d0c61b5fce319a8a1fc2c4ff38299d41202e)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Its becomming clear the upstream server doesn't like this, drop these
two urls from the test, not sure we need them here anyway.
(Bitbake rev: ab2ef942dc21f9639793c972f2e546edf9444783)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Hongxu Jia reported a problem where the bb_cache files were not always being
written out correctly. This was due to the sync thread being terminated
prematurely.
Whilst the preceeding changes mean the exit handler for this thread is now
correctly called since we switch to using sys.exit() instead of os._exit(),
this write can happen after we drop the bitbake lock, leading to potential
races. Avoid that headache by adding in explicit thread join() calls before
we drop the lock (which atexit or Finalize can't do).
(Bitbake rev: afd1900939f7b042297558f4cb01f50f3a299267)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Each run through the parser would leak a thread from the queue created to
shut the parser down. Close this down correctly and clean up the code flow
slightly whilst in the area, making sure this thread does shut down correctly
(we don't care if it loses data).
(Bitbake rev: 51ba35e9bbd4da8b5f3b3b5b8213cb634a6b0f06)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The buffering parameter was removed in python 3.1 and made default
so we can clean up the code. This removes weird looking double
exceptions when connections fail.
(Bitbake rev: 06b7bafbd18a47c8db2f7b943dc535c65df176bf)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
