[OE-core] [PATCH 1/1] avahi: launch avahi-daemon after connman
From: Kai Kang When connman installed to image, /etc/resolv.conf is link to /etc/resolv-conf.connman. So launch avahi-daemon after connman too just same as after systemd-resolved.service. Signed-off-by: Kai Kang --- .../files/0001-Fix-opening-etc-resolv.conf-error.patch | 7 ++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/meta/recipes-connectivity/avahi/files/0001-Fix-opening-etc-resolv.conf-error.patch b/meta/recipes-connectivity/avahi/files/0001-Fix-opening-etc-resolv.conf-error.patch index 11e7e8a9bc..cb8b83fd23 100644 --- a/meta/recipes-connectivity/avahi/files/0001-Fix-opening-etc-resolv.conf-error.patch +++ b/meta/recipes-connectivity/avahi/files/0001-Fix-opening-etc-resolv.conf-error.patch @@ -19,6 +19,11 @@ is marked as OE specific. Upstream-Status: Inappropriate [OE Specific] Signed-off-by: Chen Qi + +When connman installed to image, /etc/resolv.conf is link to +/etc/resolv-conf.connman. So launch avahi-daemon after connman too. + +Signed-off-by: Kai Kang --- avahi-daemon/avahi-daemon.service.in | 1 + 1 file changed, 1 insertion(+) @@ -31,7 +36,7 @@ index 548c834..63e28e4 100644 [Unit] Description=Avahi mDNS/DNS-SD Stack Requires=avahi-daemon.socket -+After=systemd-resolved.service ++After=systemd-resolved.service connman.service [Service] Type=dbus -- 2.20.0 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 0/1] Fix avaihi daemon start error
From: Kai Kang It shows error message which causes oe-selftest case parselogs fails: Aug 29 13:50:23 qemux86 avahi-daemon[151]: ../../avahi-0.7/avahi-daemon/chroot.c: open() failed: No such file or directory Aug 29 13:50:23 qemux86 avahi-daemon[148]: Failed to open /etc/resolv.conf: Invalid argument Kai Kang (1): avahi: launch avahi-daemon after connman .../files/0001-Fix-opening-etc-resolv.conf-error.patch | 7 ++- 1 file changed, 6 insertions(+), 1 deletion(-) -- 2.20.0 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] libbsd: upgrade 0.9.1 -> 0.10.0
License-Update: copyright years updated.
Drop the backport patch.
Signed-off-by: Yi Zhao
---
.../0001-flopen-Add-missing-fcntl.h-include.patch | 46 --
.../libbsd/{libbsd_0.9.1.bb => libbsd_0.10.0.bb} | 11 ++
2 files changed, 4 insertions(+), 53 deletions(-)
delete mode 100644
meta/recipes-support/libbsd/libbsd/0001-flopen-Add-missing-fcntl.h-include.patch
rename meta/recipes-support/libbsd/{libbsd_0.9.1.bb => libbsd_0.10.0.bb} (79%)
diff --git
a/meta/recipes-support/libbsd/libbsd/0001-flopen-Add-missing-fcntl.h-include.patch
b/meta/recipes-support/libbsd/libbsd/0001-flopen-Add-missing-fcntl.h-include.patch
deleted file mode 100644
index 8abb876..000
---
a/meta/recipes-support/libbsd/libbsd/0001-flopen-Add-missing-fcntl.h-include.patch
+++ /dev/null
@@ -1,46 +0,0 @@
-From 13c32916b4baab58d93940d57fea9ff0777f1931 Mon Sep 17 00:00:00 2001
-From: Baruch Siach
-Date: Tue, 5 Jun 2018 19:21:46 +0300
-Subject: [PATCH] flopen: Add missing include
-MIME-Version: 1.0
-Content-Type: text/plain; charset=UTF-8
-Content-Transfer-Encoding: 8bit
-
-Commit 993828d84ee (Add flopenat() function from FreeBSD) dropped the
-fcntl.h header. This breaks the build with musl libc:
-
-flopen.c: In function ‘vflopenat’:
-flopen.c:60:14: error: ‘O_CREAT’ undeclared (first use in this function)
- if (flags & O_CREAT) {
- ^~~
-
-Restore the fcntl.h header include to fix the build.
-
-Fixes: commit 993828d84eed0468c6c15b2818e534e6b134b8e4
-Submitted-also-by: parazyd
-Signed-off-by: Baruch Siach
-Signed-off-by: Guillem Jover
-
-Upstream-Status: Backport
-[https://gitlab.freedesktop.org/libbsd/libbsd/commit/13c32916b4baab58d93940d57fea9ff0777f1931]
-
-Signed-off-by: Yi Zhao
- src/flopen.c | 1 +
- 1 file changed, 1 insertion(+)
-
-diff --git a/src/flopen.c b/src/flopen.c
-index b9972c9..ff20d07 100644
a/src/flopen.c
-+++ b/src/flopen.c
-@@ -32,6 +32,7 @@
- #include
-
- #include
-+#include
- #include
- #include
-
---
-2.7.4
-
diff --git a/meta/recipes-support/libbsd/libbsd_0.9.1.bb
b/meta/recipes-support/libbsd/libbsd_0.10.0.bb
similarity index 79%
rename from meta/recipes-support/libbsd/libbsd_0.9.1.bb
rename to meta/recipes-support/libbsd/libbsd_0.10.0.bb
index 2b75cdf..eaf244a 100644
--- a/meta/recipes-support/libbsd/libbsd_0.9.1.bb
+++ b/meta/recipes-support/libbsd/libbsd_0.10.0.bb
@@ -28,16 +28,13 @@ HOMEPAGE = "http://libbsd.freedesktop.org/wiki/;
# License: public-domain
# License: public-domain-Colin-Plumb
LICENSE = "BSD-4-Clause & ISC & PD"
-LIC_FILES_CHKSUM = "file://COPYING;md5=b552602fda69e34c753d26de383f33c5"
+LIC_FILES_CHKSUM = "file://COPYING;md5=2120be0173469a06ed185b688e0e1ae0"
SECTION = "libs"
-SRC_URI = " \
-http://libbsd.freedesktop.org/releases/${BPN}-${PV}.tar.xz \
-file://0001-flopen-Add-missing-fcntl.h-include.patch \
-"
+SRC_URI = "http://libbsd.freedesktop.org/releases/${BPN}-${PV}.tar.xz;
-SRC_URI[md5sum] = "a74b80c4143afa032c90226a4518fffe"
-SRC_URI[sha256sum] =
"56d835742327d69faccd16955a60b6dcf30684a8da518c4eca0ac713b9e0a7a4"
+SRC_URI[md5sum] = "ead96d240d02faa5b921c0aa50c812b5"
+SRC_URI[sha256sum] =
"34b8adc726883d0e85b3118fa13605e179a62b31ba51f676136ecb2d0bc1a887"
inherit autotools pkgconfig
--
2.7.4
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] Remove LSB support
On Fri, Aug 30, 2019 at 11:04:52AM +0800, Robert Yang wrote: > Hi Adrian, Hi Robert, > On 8/26/19 1:21 AM, Adrian Bunk wrote: > > The only part with some (marginal) usage is lsb_release, > > which is split from the lsb package into an own lsb-release > > package. > > > > Signed-off-by: Adrian Bunk > > --- > > https://github.com/AdrianBunk/meta-lsb contains a preliminary > > Do you have a plan to move it to git.yoctoproject.org or > git.openembedded.org, please? > > // Robert > > > meta-lsb layer, looking for a maintainer. >... I am hoping that someone who has an actual interest in LSB will adopt it, and then it's not up to me where it will be hosted. If you are interested, feel free to adopt it and host it wherever you want. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] linux-yocto_5.2.bb: Fix build races in kernel-selftests
I have these staged and they will be part of my next version of the 5.2 recipes.
Bruce
On Thu, Aug 29, 2019 at 8:22 AM Bruce Ashfield wrote:
>
> I'll merge this directly to the 5.2 branches, rather than patches (but
> you knew I'd say that). I'll queue it and run some tests ASAP.
>
> Bruce
>
> On Thu, Aug 29, 2019 at 12:53 AM Khem Raj wrote:
> >
> > Signed-off-by: Khem Raj
> > Cc: Bruce Ashfield
> > ---
> > ...x-test_verifier-test_maps-make-depen.patch | 58 +
> > ...ructure-test_-progs-maps-verifier-te.patch | 86 +++
> > meta/recipes-kernel/linux/linux-yocto_5.2.bb | 3 +
> > 3 files changed, 147 insertions(+)
> > create mode 100644
> > meta/recipes-kernel/linux/files/0001-selftests-bpf-fix-test_verifier-test_maps-make-depen.patch
> > create mode 100644
> > meta/recipes-kernel/linux/files/0002-selftests-bpf-structure-test_-progs-maps-verifier-te.patch
> >
> > diff --git
> > a/meta/recipes-kernel/linux/files/0001-selftests-bpf-fix-test_verifier-test_maps-make-depen.patch
> >
> > b/meta/recipes-kernel/linux/files/0001-selftests-bpf-fix-test_verifier-test_maps-make-depen.patch
> > new file mode 100644
> > index 00..e397b10cb4
> > --- /dev/null
> > +++
> > b/meta/recipes-kernel/linux/files/0001-selftests-bpf-fix-test_verifier-test_maps-make-depen.patch
> > @@ -0,0 +1,58 @@
> > +From 08a2303803397c98e0f279bb6fb22afc673786a3 Mon Sep 17 00:00:00 2001
> > +From: Andrii Nakryiko
> > +Date: Tue, 16 Jul 2019 12:38:36 -0700
> > +Subject: [PATCH 1/2] selftests/bpf: fix test_verifier/test_maps make
> > + dependencies
> > +
> > +e46fc22e60a4 ("selftests/bpf: make directory prerequisites order-only")
> > +exposed existing problem in Makefile for test_verifier and test_maps tests:
> > +their dependency on auto-generated header file with a list of all tests
> > wasn't
> > +recorded explicitly. This patch fixes these issues.
> > +
> > +Fixes: 51a0e301a563 ("bpf: Add BPF_MAP_TYPE_SK_STORAGE test to test_maps")
> > +Fixes: 6b7b6995c43e ("selftests: bpf: tests.h should depend on .c files,
> > not the output")
> > +Cc: Ilya Leoshkevich
> > +Cc: Stanislav Fomichev
> > +Cc: Martin KaFai Lau
> > +Signed-off-by: Andrii Nakryiko
> > +Signed-off-by: Alexei Starovoitov
> > +---
> > + tools/testing/selftests/bpf/Makefile | 6 +++---
> > + 1 file changed, 3 insertions(+), 3 deletions(-)
> > +
> > +diff --git a/tools/testing/selftests/bpf/Makefile
> > b/tools/testing/selftests/bpf/Makefile
> > +index b9e88ccc289b..cd12bf414056 100644
> > +--- a/tools/testing/selftests/bpf/Makefile
> > b/tools/testing/selftests/bpf/Makefile
> > +@@ -77,8 +77,6 @@ all: $(TEST_CUSTOM_PROGS)
> > + $(OUTPUT)/urandom_read: $(OUTPUT)/%: %.c
> > + $(CC) -o $@ $< -Wl,--build-id
> > +
> > +-$(OUTPUT)/test_maps: map_tests/*.c
> > +-
> > + BPFOBJ := $(OUTPUT)/libbpf.a
> > +
> > + $(TEST_GEN_PROGS): $(BPFOBJ)
> > +@@ -242,9 +240,10 @@ MAP_TESTS_DIR = $(OUTPUT)/map_tests
> > + $(MAP_TESTS_DIR):
> > + mkdir -p $@
> > + MAP_TESTS_H := $(MAP_TESTS_DIR)/tests.h
> > ++MAP_TESTS_FILES := $(wildcard map_tests/*.c)
> > + test_maps.c: $(MAP_TESTS_H)
> > + $(OUTPUT)/test_maps: CFLAGS += $(TEST_MAPS_CFLAGS)
> > +-MAP_TESTS_FILES := $(wildcard map_tests/*.c)
> > ++$(OUTPUT)/test_maps: test_maps.c $(MAP_TESTS_H) $(MAP_TESTS_FILES)
> > + $(MAP_TESTS_H): $(MAP_TESTS_DIR) $(MAP_TESTS_FILES)
> > + $(shell ( cd map_tests/; \
> > + echo '/* Generated header, do not edit */'; \
> > +@@ -261,6 +260,7 @@ $(MAP_TESTS_H): $(MAP_TESTS_DIR) $(MAP_TESTS_FILES)
> > + VERIFIER_TESTS_H := $(OUTPUT)/verifier/tests.h
> > + test_verifier.c: $(VERIFIER_TESTS_H)
> > + $(OUTPUT)/test_verifier: CFLAGS += $(TEST_VERIFIER_CFLAGS)
> > ++$(OUTPUT)/test_verifier: test_verifier.c $(VERIFIER_TESTS_H)
> > +
> > + VERIFIER_TESTS_DIR = $(OUTPUT)/verifier
> > + $(VERIFIER_TESTS_DIR):
> > +--
> > +2.23.0
> > +
> > diff --git
> > a/meta/recipes-kernel/linux/files/0002-selftests-bpf-structure-test_-progs-maps-verifier-te.patch
> >
> > b/meta/recipes-kernel/linux/files/0002-selftests-bpf-structure-test_-progs-maps-verifier-te.patch
> > new file mode 100644
> > index 00..36692088b0
> > --- /dev/null
> > +++
> > b/meta/recipes-kernel/linux/files/0002-selftests-bpf-structure-test_-progs-maps-verifier-te.patch
> > @@ -0,0 +1,86 @@
> > +From 2fd88b60e6255206d46baa543a637aa1e1cc6186 Mon Sep 17 00:00:00 2001
> > +From: Andrii Nakryiko
> > +Date: Tue, 16 Jul 2019 12:38:37 -0700
> > +Subject: [PATCH 2/2] selftests/bpf: structure test_{progs, maps, verifier}
> > + test runners uniformly
> > +
> > +It's easier to follow the logic if it's structured the same.
> > +There is just slight difference between test_progs/test_maps and
> > +test_verifier. test_verifier's verifier/*.c files are not really compilable
> > +C files (they are more of include headers), so they can't be specified as
> > +explicit dependencies of test_verifier.
> > +
> > +Cc: Alexei Starovoitov
> > +Signed-off-by: Andrii Nakryiko
> >
Re: [OE-core] [PATCH 1/5] kernel-devsrc: tweak for v5.3+
On Thu, Aug 29, 2019 at 10:13 PM Mittal, Anuj wrote: > > On Thu, 2019-08-29 at 08:27 -0400, Bruce Ashfield wrote: > > On Thu, Aug 29, 2019 at 5:17 AM Mittal, Anuj > > wrote: > > > On Wed, 2019-08-14 at 11:31 -0400, bruce.ashfi...@gmail.com wrote: > > > > From: Bruce Ashfield > > > > > > > > The 5.3 kernel has two changes that require tweaks to the minimal > > > > kernel-devsrc package. > > > > > > > > - 4ce97317f [x86/purgatory: Do not use __builtin_memcpy and > > > > __builtin_memset] > > > > > > > > This change removes the need for arch/x86/purgatory/string.c > > > > and > > > > instead reuses a copy in arch/x86/boot/compressed/, so we can't > > > > copy > > > > the file anymore. To support older kernels, we make the copy > > > > survive > > > > the non-existence of the file. > > > > > > > > > > This change was merged in 4.19 stable kernel as well. Can this be > > > merged in our stable branches as well please? > > > > It already is (just not pushed), I just wasn't doing -stable updates > > along with 5.2 intro .. there's only so many things I can debug and > > regression test at one time. Hopefully I'll get through the 5.2 work > > soon and finish the rest of my queue. > > Thank you Bruce. I meant that this kernel-devsrc fix should be merged > in yocto stable branch, warrior, regardless of the 4.19 kernel version > there. Aha. gotcha. I'll send it along to -stable once we've sorted out the current set of issues. Bruce > > Thanks, > > Anuj -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] spp: optimize strip_common_prefix function
This needs to go to the linux-yocto list.
Cheers,
Bruce
On Thu, Aug 29, 2019 at 10:42 PM Zhaolong Zhang wrote:
>
> strip_common_prefix() is the hot path that executes on every input file.
> This patch sorts and uniqs the $include_paths by length descreasingly.
> And with the sorted $include_paths, the for-loop inside strip_common_prefix
> can break earlier, thus kernel_metadata task can be sped up by multiple times.
>
> Signed-off-by: Zhaolong Zhang
> ---
> tools/spp | 12
> 1 file changed, 12 insertions(+)
>
> diff --git a/tools/spp b/tools/spp
> index 1150ff3..cba52bb 100755
> --- a/tools/spp
> +++ b/tools/spp
> @@ -125,6 +125,7 @@ strip_common_prefix()
> if [ $this_len -lt $out_len ]; then
> relocated_name=$t
> out_len=$this_len
> + break
> fi
> # add a trailing slash to get corner cases where one may
> # have been added or not dropped
> @@ -133,6 +134,7 @@ strip_common_prefix()
> if [ $this_len -lt $out_len ]; then
> relocated_name=$t
> out_len=$this_len
> + break
> fi
> done
>
> @@ -297,6 +299,16 @@ infiles=$@
>
> processed_files=""
>
> +# this function also removes duplicated lines by `sort -u`
> +sort_by_len_dec()
> +{
> +for i in $@; do
> +echo $i
> +done | sort -u | awk '{ print length($0) " " $0; }' | sort -nr | cut
> -d ' ' -f 2-
> +}
> +
> +include_paths=$(sort_by_len_dec $include_paths)
> +
> ##
> ## create variables for use in scripts
> ##
> --
> 1.9.1
>
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] spp: optimize strip_common_prefix function
On a Haswell Xeon 3.2GHz machine, iteration on each include_path costs ~12.5ms.
And the total time we can save at best is (0.0125s * n_patches *
n_include_paths)
On 8/30/19 10:39 AM, Zhaolong Zhang wrote:
strip_common_prefix() is the hot path that executes on every input file.
This patch sorts and uniqs the $include_paths by length descreasingly.
And with the sorted $include_paths, the for-loop inside strip_common_prefix
can break earlier, thus kernel_metadata task can be sped up by multiple times.
Signed-off-by: Zhaolong Zhang
---
tools/spp | 12
1 file changed, 12 insertions(+)
diff --git a/tools/spp b/tools/spp
index 1150ff3..cba52bb 100755
--- a/tools/spp
+++ b/tools/spp
@@ -125,6 +125,7 @@ strip_common_prefix()
if [ $this_len -lt $out_len ]; then
relocated_name=$t
out_len=$this_len
+ break
fi
# add a trailing slash to get corner cases where one may
# have been added or not dropped
@@ -133,6 +134,7 @@ strip_common_prefix()
if [ $this_len -lt $out_len ]; then
relocated_name=$t
out_len=$this_len
+ break
fi
done
@@ -297,6 +299,16 @@ infiles=$@
processed_files=""
+# this function also removes duplicated lines by `sort -u`
+sort_by_len_dec()
+{
+for i in $@; do
+echo $i
+done | sort -u | awk '{ print length($0) " " $0; }' | sort -nr | cut
-d ' ' -f 2-
+}
+
+include_paths=$(sort_by_len_dec $include_paths)
+
##
## create variables for use in scripts
##
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] Remove LSB support
Hi Adrian,
On 8/26/19 1:21 AM, Adrian Bunk wrote:
The only part with some (marginal) usage is lsb_release,
which is split from the lsb package into an own lsb-release
package.
Signed-off-by: Adrian Bunk
---
https://github.com/AdrianBunk/meta-lsb contains a preliminary
Do you have a plan to move it to git.yoctoproject.org or git.openembedded.org,
please?
// Robert
meta-lsb layer, looking for a maintainer.
---
README.LSB| 29 -
meta/conf/distro/include/distro_alias.inc | 6 -
meta/conf/distro/include/maintainers.inc | 6 +-
meta/lib/oeqa/manual/bsp-hw.json | 2 +-
meta/lib/oeqa/manual/compliance-test.json | 32 +-
.../lib/oeqa/manual/toaster-managed-mode.json | 14 +-
.../packagegroups/packagegroup-self-hosted.bb | 2 +-
.../bootchart2/bootchart2_0.14.8.bb | 2 +-
.../images/core-image-lsb-dev.bb | 7 -
.../images/core-image-lsb-sdk.bb | 12 -
.../recipes-extended/images/core-image-lsb.bb | 14 -
...e-to-work-with-busybox-head-and-find.patch | 0
meta/recipes-extended/lsb/lsb-release_1.4.bb | 37 ++
meta/recipes-extended/lsb/lsb/init-functions | 44 --
meta/recipes-extended/lsb/lsb/lsb_killproc| 6 -
meta/recipes-extended/lsb/lsb/lsb_log_message | 27 -
meta/recipes-extended/lsb/lsb/lsb_pidofproc | 6 -
.../recipes-extended/lsb/lsb/lsb_start_daemon | 45 --
meta/recipes-extended/lsb/lsb_5.0.bb | 136 -
...exit-1-which-causes-init-scripts-to-.patch | 21 -
.../lsb/lsbinitscripts/functions.patch| 33 --
.../lsb/lsbinitscripts_9.79.bb| 31 --
meta/recipes-extended/lsb/lsbtest/LSB_Test.sh | 525 --
.../lsb/lsbtest/packages_list | 49 --
meta/recipes-extended/lsb/lsbtest/session | 176 --
meta/recipes-extended/lsb/lsbtest_1.0.bb | 49 --
.../packagegroups/packagegroup-core-lsb.bb| 240
meta/recipes.txt | 2 +-
28 files changed, 50 insertions(+), 1503 deletions(-)
delete mode 100644 README.LSB
delete mode 100644 meta/recipes-extended/images/core-image-lsb-dev.bb
delete mode 100644 meta/recipes-extended/images/core-image-lsb-sdk.bb
delete mode 100644 meta/recipes-extended/images/core-image-lsb.bb
rename meta/recipes-extended/lsb/{lsb =>
lsb-release}/0001-fix-lsb_release-to-work-with-busybox-head-and-find.patch (100%)
create mode 100644 meta/recipes-extended/lsb/lsb-release_1.4.bb
delete mode 100755 meta/recipes-extended/lsb/lsb/init-functions
delete mode 100755 meta/recipes-extended/lsb/lsb/lsb_killproc
delete mode 100755 meta/recipes-extended/lsb/lsb/lsb_log_message
delete mode 100755 meta/recipes-extended/lsb/lsb/lsb_pidofproc
delete mode 100755 meta/recipes-extended/lsb/lsb/lsb_start_daemon
delete mode 100644 meta/recipes-extended/lsb/lsb_5.0.bb
delete mode 100644
meta/recipes-extended/lsb/lsbinitscripts/0001-functions-avoid-exit-1-which-causes-init-scripts-to-.patch
delete mode 100644 meta/recipes-extended/lsb/lsbinitscripts/functions.patch
delete mode 100644 meta/recipes-extended/lsb/lsbinitscripts_9.79.bb
delete mode 100644 meta/recipes-extended/lsb/lsbtest/LSB_Test.sh
delete mode 100644 meta/recipes-extended/lsb/lsbtest/packages_list
delete mode 100644 meta/recipes-extended/lsb/lsbtest/session
delete mode 100644 meta/recipes-extended/lsb/lsbtest_1.0.bb
delete mode 100644
meta/recipes-extended/packagegroups/packagegroup-core-lsb.bb
diff --git a/README.LSB b/README.LSB
deleted file mode 100644
index fecbe548b7..00
--- a/README.LSB
+++ /dev/null
@@ -1,29 +0,0 @@
-OE-Core aims to be able to provide basic LSB compatible images. There
-are some challenges for OE as LSB isn't always 100% relevant to its
-target embedded and IoT audiences.
-
-One challenge is that the LSB spec is no longer being actively
-developed [https://github.com/LinuxStandardBase/lsb] and has
-components which are end of life or significantly dated. OE
-therefore provides compatibility with the following caveats:
-
-* Qt4 is provided by the separate meta-qt4 layer. Its noted that Qt4
- is end of life and this isn't something the core project regularly
- tests any longer. Users are recommended to group together to support
- maintenance of that layer.
[http://git.yoctoproject.org/cgit/cgit.cgi/meta-qt4/]
-
-* GTK+ 2 is provided by meta-oe. It is noted that GTK+ 2 is end of life
- and use of GTK+ 2 isn't recommended.
-
-* mailx has been dropped since its no longer being developed upstream
- and there are better, more modern replacements such as s-nail
- (http://sdaoden.eu/code.html) or mailutils (http://mailutils.org/).
-
-* A few perl modules that were required by LSB 4.x aren't provided:
- libclass-isa, libenv, libdumpvalue, libfile-checktree,
- libi18n-collate, libpod-plainer.
-
-* libpng 1.2 isn't provided; oe-core includes the latest release of libpng
- instead.
-
-* pax (POSIX
[OE-core] ✗ patchtest: failure for spp: optimize strip_common_prefix function
== Series Details == Series: spp: optimize strip_common_prefix function Revision: 1 URL : https://patchwork.openembedded.org/series/19578/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the proposed series by patchtest resulting in the following failures: * Issue Series does not apply on top of target branch [test_series_merge_on_head] Suggested fixRebase your series on top of targeted branch Targeted branch master (currently at c8f329fc56) If you believe any of these test results are incorrect, please reply to the mailing list (openembedded-core@lists.openembedded.org) raising your concerns. Otherwise we would appreciate you correcting the issues and submitting a new version of the patchset if applicable. Please ensure you add/increment the version number when sending the new version (i.e. [PATCH] -> [PATCH v2] -> [PATCH v3] -> ...). --- Guidelines: https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] spp: optimize strip_common_prefix function
strip_common_prefix() is the hot path that executes on every input file.
This patch sorts and uniqs the $include_paths by length descreasingly.
And with the sorted $include_paths, the for-loop inside strip_common_prefix
can break earlier, thus kernel_metadata task can be sped up by multiple times.
Signed-off-by: Zhaolong Zhang
---
tools/spp | 12
1 file changed, 12 insertions(+)
diff --git a/tools/spp b/tools/spp
index 1150ff3..cba52bb 100755
--- a/tools/spp
+++ b/tools/spp
@@ -125,6 +125,7 @@ strip_common_prefix()
if [ $this_len -lt $out_len ]; then
relocated_name=$t
out_len=$this_len
+ break
fi
# add a trailing slash to get corner cases where one may
# have been added or not dropped
@@ -133,6 +134,7 @@ strip_common_prefix()
if [ $this_len -lt $out_len ]; then
relocated_name=$t
out_len=$this_len
+ break
fi
done
@@ -297,6 +299,16 @@ infiles=$@
processed_files=""
+# this function also removes duplicated lines by `sort -u`
+sort_by_len_dec()
+{
+for i in $@; do
+echo $i
+done | sort -u | awk '{ print length($0) " " $0; }' | sort -nr | cut
-d ' ' -f 2-
+}
+
+include_paths=$(sort_by_len_dec $include_paths)
+
##
## create variables for use in scripts
##
--
1.9.1
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 1/5] kernel-devsrc: tweak for v5.3+
On Thu, 2019-08-29 at 08:27 -0400, Bruce Ashfield wrote: > On Thu, Aug 29, 2019 at 5:17 AM Mittal, Anuj > wrote: > > On Wed, 2019-08-14 at 11:31 -0400, bruce.ashfi...@gmail.com wrote: > > > From: Bruce Ashfield > > > > > > The 5.3 kernel has two changes that require tweaks to the minimal > > > kernel-devsrc package. > > > > > > - 4ce97317f [x86/purgatory: Do not use __builtin_memcpy and > > > __builtin_memset] > > > > > > This change removes the need for arch/x86/purgatory/string.c > > > and > > > instead reuses a copy in arch/x86/boot/compressed/, so we can't > > > copy > > > the file anymore. To support older kernels, we make the copy > > > survive > > > the non-existence of the file. > > > > > > > This change was merged in 4.19 stable kernel as well. Can this be > > merged in our stable branches as well please? > > It already is (just not pushed), I just wasn't doing -stable updates > along with 5.2 intro .. there's only so many things I can debug and > regression test at one time. Hopefully I'll get through the 5.2 work > soon and finish the rest of my queue. Thank you Bruce. I meant that this kernel-devsrc fix should be merged in yocto stable branch, warrior, regardless of the 4.19 kernel version there. Thanks, Anuj -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 3/4] qemu: switch to '-vga std' emulated hardware from vmware/cirrus for x86/mips
Hi Alex, On Wed, 2019-08-28 at 17:24 +0200, Alexander Kanavin wrote: ... > diff --git a/meta/conf/machine/qemuarm64.conf > b/meta/conf/machine/qemuarm64.conf > index ec2a887bddf..05f0ee5e66f 100644 > --- a/meta/conf/machine/qemuarm64.conf > +++ b/meta/conf/machine/qemuarm64.conf > @@ -17,7 +17,7 @@ QB_CPU_KVM = "-cpu host" > # Standard Serial console > QB_KERNEL_CMDLINE_APPEND = "console=ttyAMA0" > # For graphics to work we need to define the VGA device as well as > the necessary USB devices > -QB_OPT_APPEND = "-show-cursor -device VGA,edid=on" > +QB_OPT_APPEND = "-show-cursor" Was this intentional? This is reverting an earlier fix: https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/meta/conf/machine/qemuarm64.conf?h=master-next=b181bf92e2bc51a808478c12fe62177d966f2a85 https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/meta/conf/machine/qemuarm64.conf?h=master-next=ff35b6c57a380ca4dc158c5104a6137f8faea5cd I'm not sure if this is the reason but master-next build is also showing problems when running X with qemuarm: https://autobuilder.yoctoproject.org/typhoon/#/builders/38/builds/978/steps/8/logs/step1c ... > diff --git a/meta/lib/oeqa/runtime/cases/parselogs.py > b/meta/lib/oeqa/runtime/cases/parselogs.py > index 19c9c52a0a9..0002730d46f 100644 > --- a/meta/lib/oeqa/runtime/cases/parselogs.py > +++ b/meta/lib/oeqa/runtime/cases/parselogs.py > @@ -55,7 +55,11 @@ common_errors = [ > "Failed to read /var/lib/nfs/statd/state: Success", > "error retry time-out =", > "logind: cannot setup systemd-logind helper (-61), using legacy > fallback", > -"Error changing net interface name 'eth0' to " > +"Error changing net interface name 'eth0' to ", > +"modeset(0): Failed to initialize the DRI2 extension", > +"uvesafb: cannot reserve video memory at", > +"uvesafb: probe of uvesafb.0 failed with error", > +"glamor initialization failed" > ] > parselogs test is used not only for qemu but for other MACHINES as well including genericx86 on actual hardware where glamor initialization error might need looking into. Perhaps this should be added to qemu specific parts of this test only? Thanks, Anuj -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] meta: add missing descriptions and homepage in bsp
Signed-off-by: Maxime Roussin-Bélanger
---
meta/recipes-bsp/acpid/acpid.inc | 5 +
meta/recipes-bsp/formfactor/formfactor_0.0.bb | 3 +++
meta/recipes-bsp/grub/grub-bootconf_1.00.bb | 5 +
meta/recipes-bsp/u-boot/u-boot-common.inc | 4
meta/recipes-bsp/usbinit/usbinit.bb | 4
5 files changed, 21 insertions(+)
diff --git a/meta/recipes-bsp/acpid/acpid.inc b/meta/recipes-bsp/acpid/acpid.inc
index 766ed4f89e..ee9f2c0ece 100644
--- a/meta/recipes-bsp/acpid/acpid.inc
+++ b/meta/recipes-bsp/acpid/acpid.inc
@@ -1,4 +1,9 @@
SUMMARY = "A daemon for delivering ACPI events"
+DESCRIPTION = "In recent linux kernels, the /proc/acpi/event interface has \
+been deprecated. The same information (and more) is available via netlink \
+(a way for the kernel to communicate with userspace that is usually used \
+for networking) and the input layer (mouse, keyboard, power button, etc...). \
+This version of acpid supports netlink and the input layer."
HOMEPAGE = "http://sourceforge.net/projects/acpid2;
BUGTRACKER = "http://sourceforge.net/p/acpid2/tickets/?source=navbar;
SECTION = "base"
diff --git a/meta/recipes-bsp/formfactor/formfactor_0.0.bb
b/meta/recipes-bsp/formfactor/formfactor_0.0.bb
index 53cf1cf774..919fb1fbba 100644
--- a/meta/recipes-bsp/formfactor/formfactor_0.0.bb
+++ b/meta/recipes-bsp/formfactor/formfactor_0.0.bb
@@ -1,4 +1,7 @@
SUMMARY = "Device formfactor information"
+DESCRIPTION = "A formfactor configuration file provides information about the /
+target hardware for which the image is being built and information that the /
+build system cannot obtain from other sources such as the kernel."
SECTION = "base"
LICENSE = "MIT"
LIC_FILES_CHKSUM =
"file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
diff --git a/meta/recipes-bsp/grub/grub-bootconf_1.00.bb
b/meta/recipes-bsp/grub/grub-bootconf_1.00.bb
index 750f8c808a..57e0eddb67 100644
--- a/meta/recipes-bsp/grub/grub-bootconf_1.00.bb
+++ b/meta/recipes-bsp/grub/grub-bootconf_1.00.bb
@@ -1,6 +1,11 @@
LICENSE = "MIT"
LIC_FILES_CHKSUM =
"file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
SUMMARY = "Basic grub.cfg for use in EFI systems"
+DESCRIPTION = "The grub.cfg file contains Bash-like code and a list of
installed \
+kernels in an array ordered by sequence of installation. For example, if you \
+have four installed kernels, the most recent kernel will be at index 0, the \
+previous kernel will be at index 1, and the oldest kernel will be index 3."
+HOMEPAGE =
"https://www.gnu.org/software/grub/manual/grub/grub.html#Configuration;
RPROVIDES_${PN} += "virtual/grub-bootconf"
diff --git a/meta/recipes-bsp/u-boot/u-boot-common.inc
b/meta/recipes-bsp/u-boot/u-boot-common.inc
index ad043dbcde..a056eae8ce 100644
--- a/meta/recipes-bsp/u-boot/u-boot-common.inc
+++ b/meta/recipes-bsp/u-boot/u-boot-common.inc
@@ -1,4 +1,8 @@
HOMEPAGE = "http://www.denx.de/wiki/U-Boot/WebHome;
+DESCRIPTION = "U-Boot, a boot loader for Embedded boards based on PowerPC, \
+ARM, MIPS and several other processors, which can be installed in a boot \
+ROM and used to initialize and test the hardware or to download and run \
+application code."
SECTION = "bootloaders"
DEPENDS += "flex-native bison-native"
diff --git a/meta/recipes-bsp/usbinit/usbinit.bb
b/meta/recipes-bsp/usbinit/usbinit.bb
index aba44b4068..c93f5faee5 100644
--- a/meta/recipes-bsp/usbinit/usbinit.bb
+++ b/meta/recipes-bsp/usbinit/usbinit.bb
@@ -1,4 +1,8 @@
SUMMARY = "Initscript for enabling USB gadget Ethernet"
+DESCRIPTION = "This module allows ethernet emulation over USB, allowing for /
+all sorts of nifty things like SSH and NFS in one go plus charging over the /
+same wire, at higher speeds than most Wifi connections."
+HOMEPAGE = "http://linux-sunxi.org/USB_Gadget/Ethernet;
LICENSE = "GPLv2"
LIC_FILES_CHKSUM =
"file://${WORKDIR}/COPYING.GPL;md5=751419260aa954499f7abaabaa882bbe"
--
2.20.1
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] go-dep: update to 0.5.4
Signed-off-by: Oleksandr Kravchuk
---
meta/recipes-devtools/go/{go-dep_0.5.0.bb => go-dep_0.5.4.bb} | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
rename meta/recipes-devtools/go/{go-dep_0.5.0.bb => go-dep_0.5.4.bb} (90%)
diff --git a/meta/recipes-devtools/go/go-dep_0.5.0.bb
b/meta/recipes-devtools/go/go-dep_0.5.4.bb
similarity index 90%
rename from meta/recipes-devtools/go/go-dep_0.5.0.bb
rename to meta/recipes-devtools/go/go-dep_0.5.4.bb
index a4d631f8ea..ead87870e2 100644
--- a/meta/recipes-devtools/go/go-dep_0.5.0.bb
+++ b/meta/recipes-devtools/go/go-dep_0.5.4.bb
@@ -8,8 +8,7 @@ SRC_URI = "git://${GO_IMPORT} \
file://0001-Add-support-for-mips-mips64.patch;patchdir=src/github.com/golang/dep
\
"
-# Points to 0.5.0 tag
-SRCREV = "224a564abe296670b692fe08bb63a3e4c4ad7978"
+SRCREV = "1f7c19e5f52f49ffb9f956f64c010be14683468b"
inherit go
--
2.17.1
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] runqemu: Change to use -device virtio-gpu-pci instead of -vga virtio
> Can you please look into why that error happens on arm, but not on > x86? -vga virtio is the officially documented option, so I would > rather use that everywhere. Accoding to https://wiki.qemu.org/Documentation/Platforms/ARM#virt_machine_graphics , we should use '-device virtio-gpu-pci' if given '-M virt' to qemu- system-aarch64 or qemu-system-arm. On Wed, 2019-08-28 at 08:54 +0200, Alexander Kanavin wrote: > On Wed, 28 Aug 2019 at 06:36, > wrote: > > If using qemu-system-aarch64 or qemu-system-arm with the options, > > an error > > occured as follows: > > > > qemu-system-aarch64: Virtio VGA not available > > > > this commit fixes the error to use -device virtio-gpu-pci instead > > of > > -vga virtio. > > Can you please look into why that error happens on arm, but not on > x86? -vga virtio is the officially documented option, so I would > rather use that everywhere. > > Alex -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] ell: update to 0.22
Changelog:
- Fix issue with DHCP and T1 timeout handling.
- Fix issue with escape characters in peer identity string.
- Add support for setting peer certificate's subject CN mask.
Signed-off-by: Oleksandr Kravchuk
---
meta/recipes-core/ell/{ell_0.21.bb => ell_0.22.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-core/ell/{ell_0.21.bb => ell_0.22.bb} (83%)
diff --git a/meta/recipes-core/ell/ell_0.21.bb
b/meta/recipes-core/ell/ell_0.22.bb
similarity index 83%
rename from meta/recipes-core/ell/ell_0.21.bb
rename to meta/recipes-core/ell/ell_0.22.bb
index 487fbccab5..b3942fc30e 100644
--- a/meta/recipes-core/ell/ell_0.21.bb
+++ b/meta/recipes-core/ell/ell_0.22.bb
@@ -14,8 +14,8 @@ DEPENDS = "dbus"
inherit autotools pkgconfig
SRC_URI =
"https://mirrors.edge.kernel.org/pub/linux/libs/${BPN}/${BPN}-${PV}.tar.xz;
-SRC_URI[md5sum] = "f94f8c812b0426b0c30b651fa5142dd9"
-SRC_URI[sha256sum] =
"a0db4e3057ba41035637354b6af2aa4c74f83509e0c3e563d682df9d72eaff17"
+SRC_URI[md5sum] = "a4e7d74404f11e71775b89f53a8f1c33"
+SRC_URI[sha256sum] =
"3c1d6d997e17dfcbe4ebcd1331d9a7be5c64f2f0a0813bc223790e570d8da2e3"
do_configure_prepend () {
mkdir -p ${S}/build-aux
--
2.17.1
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] libevdev: update to 1.8.0
Signed-off-by: Oleksandr Kravchuk
---
.../libevdev/{libevdev_1.7.0.bb => libevdev_1.8.0.bb}| 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
rename meta/recipes-support/libevdev/{libevdev_1.7.0.bb => libevdev_1.8.0.bb}
(74%)
diff --git a/meta/recipes-support/libevdev/libevdev_1.7.0.bb
b/meta/recipes-support/libevdev/libevdev_1.8.0.bb
similarity index 74%
rename from meta/recipes-support/libevdev/libevdev_1.7.0.bb
rename to meta/recipes-support/libevdev/libevdev_1.8.0.bb
index abd6f386b8..84274987d7 100644
--- a/meta/recipes-support/libevdev/libevdev_1.7.0.bb
+++ b/meta/recipes-support/libevdev/libevdev_1.8.0.bb
@@ -7,8 +7,7 @@ LIC_FILES_CHKSUM =
"file://COPYING;md5=75aae0d38feea6fda97ca381cb9132eb \
file://libevdev/libevdev.h;endline=21;md5=7ff4f0b5113252c2f1a828e0bbad98d1"
SRC_URI = "http://www.freedesktop.org/software/libevdev/${BP}.tar.xz;
-
-SRC_URI[md5sum] = "fabe87d8d7d7f7cdb4a26e5dc99fc517"
-SRC_URI[sha256sum] =
"11dbe1f2b1d03a51f3e9a196757a75c3a999042ce34cf1fdc00a2363e5a2e369"
+SRC_URI[md5sum] = "879631080be18526737e33b63d848039"
+SRC_URI[sha256sum] =
"20d3cae4efd277f485abdf8f2a7c46588e539998b5a08c2c4d368218379d4211"
inherit autotools pkgconfig
--
2.17.1
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] libsolv: update to 0.7.6
Signed-off-by: Oleksandr Kravchuk
---
.../libsolv/{libsolv_0.7.5.bb => libsolv_0.7.6.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-extended/libsolv/{libsolv_0.7.5.bb => libsolv_0.7.6.bb}
(93%)
diff --git a/meta/recipes-extended/libsolv/libsolv_0.7.5.bb
b/meta/recipes-extended/libsolv/libsolv_0.7.6.bb
similarity index 93%
rename from meta/recipes-extended/libsolv/libsolv_0.7.5.bb
rename to meta/recipes-extended/libsolv/libsolv_0.7.6.bb
index 80ce76b45f..3df8993089 100644
--- a/meta/recipes-extended/libsolv/libsolv_0.7.5.bb
+++ b/meta/recipes-extended/libsolv/libsolv_0.7.6.bb
@@ -10,7 +10,7 @@ DEPENDS = "expat zlib"
SRC_URI = "git://github.com/openSUSE/libsolv.git \
"
-SRCREV = "2cab7ea00d08390374b25b11d969f3740c4660f4"
+SRCREV = "17ce4bc4fb52a0b32964f3b7d491c18177980be1"
UPSTREAM_CHECK_GITTAGREGEX = "(?P\d+(\.\d+)+)"
--
2.17.1
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] devtool: Avoid failure for recipes with S == WORKDIR and no local files
When extracting the sources for a recipe that has S == WORKDIR and no
local files in the SRC_URI (which, e.g., can happen for a recipe with
a URI that has the unpack=false attribute), the extraction fails with
the following backtrace:
Traceback (most recent call last):
File ".../scripts/devtool", line 344, in
ret = main()
File ".../scripts/devtool", line 331, in main
ret = args.func(args, config, basepath, workspace)
File ".../poky/scripts/lib/devtool/standard.py", line 762, in
modify
initial_rev, _ = _extract_source(srctree, args.keep_temp,
args.branch, False, config, basepath, workspace,
args.fixed_setup, rd, tinfoil, no_overrides=args.no_overrides)
File ".../poky/scripts/lib/devtool/standard.py", line 647, in
_extract_source
bb.process.run('git %s commit -a -m "Committing local file
symlinks\n\n%s"' % (' '.join(useroptions),
oe.patch.GitApplyTree.ignore_commit_prefix), cwd=srctree)
File ".../poky/bitbake/lib/bb/process.py", line 178, in run
raise ExecutionError(cmd, pipe.returncode, stdout, stderr)
bb.process.ExecutionError: Execution of 'git commit -a -m
"Committing local file symlinks
%% ignore"' failed with exit code 1:
On branch devtool
nothing to commit, working tree clean
This is because no files were found in the oe-local-files directory
and consequently no symbolic links were added using `git add`, but the
`git commit` command was still executed.
Signed-off-by: Peter Kjellerstedt
---
scripts/lib/devtool/standard.py | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/scripts/lib/devtool/standard.py b/scripts/lib/devtool/standard.py
index 96af488798..9eeaefb79c 100644
--- a/scripts/lib/devtool/standard.py
+++ b/scripts/lib/devtool/standard.py
@@ -482,9 +482,9 @@ def symlink_oelocal_files_srctree(rd,srctree):
addfiles.append(os.path.join(relpth, fn))
if addfiles:
bb.process.run('git add %s' % ' '.join(addfiles), cwd=srctree)
-useroptions = []
-oe.patch.GitApplyTree.gitCommandUserOptions(useroptions, d=rd)
-bb.process.run('git %s commit -a -m "Committing local file
symlinks\n\n%s"' % (' '.join(useroptions),
oe.patch.GitApplyTree.ignore_commit_prefix), cwd=srctree)
+useroptions = []
+oe.patch.GitApplyTree.gitCommandUserOptions(useroptions, d=rd)
+bb.process.run('git %s commit -m "Committing local file
symlinks\n\n%s"' % (' '.join(useroptions),
oe.patch.GitApplyTree.ignore_commit_prefix), cwd=srctree)
def _extract_source(srctree, keep_temp, devbranch, sync, config, basepath,
workspace, fixed_setup, d, tinfoil, no_overrides=False):
--
2.21.0
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [oe-core][master][PATCH] Introduce mechanism to keep nativesdk* sstate in esdk
ping
> -Original Message-
> From: Jaewon Lee
> Sent: Monday, April 1, 2019 5:07 PM
> To: openembedded-core@lists.openembedded.org; Alejandro Enedino
> Hernandez Samaniego ; Manjukumar Harthikote
> Matha ; Bruce Ashfield
> Cc: Jaewon Lee
> Subject: [oe-core][master][PATCH] Introduce mechanism to keep nativesdk*
> sstate in esdk
>
> Using SDK_INCLUDE_NATIVESDK flag to toggle inclusion of all nativesdk*
> sstate into esdk Currently locked-sigs.inc is generated during
> do_sdk_depends which doesn't pull in nativesdk packages. Generating
> another locked-sigs.inc in do_populate_sdk_ext and pruning it to only
> nativesdk* packages by using a modified version of the already existing
> function prune_locked_sigs and merging it with the current locked-sigs.inc
> Also adding SDK_INCLUDE_NATIVESDK tasklistfn to the logic surrounding
> setting tasklist file to not prune esdk sstate during creation
>
> Signed-off-by: Jaewon Lee
> ---
> meta/classes/populate_sdk_ext.bbclass | 28
> +++-
> meta/lib/oe/copy_buildsystem.py | 8 ++--
> 2 files changed, 33 insertions(+), 3 deletions(-)
>
> diff --git a/meta/classes/populate_sdk_ext.bbclass
> b/meta/classes/populate_sdk_ext.bbclass
> index 40b0375..d98b0e5 100644
> --- a/meta/classes/populate_sdk_ext.bbclass
> +++ b/meta/classes/populate_sdk_ext.bbclass
> @@ -20,6 +20,7 @@ SDK_EXT_task-populate-sdk-ext = "-ext"
> SDK_EXT_TYPE ?= "full"
> SDK_INCLUDE_PKGDATA ?= "0"
> SDK_INCLUDE_TOOLCHAIN ?= "${@'1' if d.getVar('SDK_EXT_TYPE') == 'full'
> else '0'}"
> +SDK_INCLUDE_NATIVESDK ?= "0"
>
> SDK_RECRDEP_TASKS ?= ""
>
> @@ -401,9 +402,27 @@ python copy_buildsystem () {
> excluded_targets = get_sdk_install_targets(d, images_only=True)
> sigfile = d.getVar('WORKDIR') + '/locked-sigs.inc'
> lockedsigs_pruned = baseoutpath + '/conf/locked-sigs.inc'
> +#nativesdk-only sigfile to merge into locked-sigs.inc
> +sdk_include_nativesdk = (d.getVar("SDK_INCLUDE_NATIVESDK") == '1')
> +nativesigfile = d.getVar('WORKDIR') + '/locked-sigs_nativesdk.inc'
> +nativesigfile_pruned = d.getVar('WORKDIR') + '/locked-
> sigs_nativesdk_pruned.inc'
> +
> +if sdk_include_nativesdk:
> +oe.copy_buildsystem.prune_lockedsigs([],
> + excluded_targets.split(),
> + nativesigfile,
> + True,
> + nativesigfile_pruned)
> +
> +oe.copy_buildsystem.merge_lockedsigs([],
> + sigfile,
> + nativesigfile_pruned,
> + sigfile)
> +
> oe.copy_buildsystem.prune_lockedsigs([],
> excluded_targets.split(),
> sigfile,
> + False,
> lockedsigs_pruned)
>
> sstate_out = baseoutpath + '/sstate-cache'
> @@ -414,7 +433,7 @@ python copy_buildsystem () {
>
> sdk_include_toolchain = (d.getVar('SDK_INCLUDE_TOOLCHAIN') == '1')
> sdk_ext_type = d.getVar('SDK_EXT_TYPE')
> -if sdk_ext_type != 'minimal' or sdk_include_toolchain or derivative:
> +if (sdk_ext_type != 'minimal' or sdk_include_toolchain or derivative) and
> not sdk_include_nativesdk:
> # Create the filtered task list used to generate the sstate cache
> shipped
> with the SDK
> tasklistfn = d.getVar('WORKDIR') + '/tasklist.txt'
> create_filtered_tasklist(d, baseoutpath, tasklistfn, conf_initpath)
> @@ -
> 658,9 +677,16 @@ fakeroot python do_populate_sdk_ext() {
> d.setVar('SDKDEPLOYDIR', '${SDKEXTDEPLOYDIR}')
> # ESDKs have a libc from the buildtools so ensure we don't ship linguas
> twice
> d.delVar('SDKIMAGE_LINGUAS')
> +if d.getVar("SDK_INCLUDE_NATIVESDK") == '1':
> +generate_nativesdk_lockedsigs(d)
> populate_sdk_common(d)
> }
>
> +def generate_nativesdk_lockedsigs(d):
> +import oe.copy_buildsystem
> +sigfile = d.getVar('WORKDIR') + '/locked-sigs_nativesdk.inc'
> +oe.copy_buildsystem.generate_locked_sigs(sigfile, d)
> +
> def get_ext_sdk_depends(d):
> # Note: the deps varflag is a list not a string, so we need to specify
> expand=False
> deps = d.getVarFlag('do_image_complete', 'deps', False) diff --git
> a/meta/lib/oe/copy_buildsystem.py b/meta/lib/oe/copy_buildsystem.py
> index 7cb784c..5bc728e 100644
> --- a/meta/lib/oe/copy_buildsystem.py
> +++ b/meta/lib/oe/copy_buildsystem.py
> @@ -168,7 +168,7 @@ def generate_locked_sigs(sigfile, d):
> tasks = ['%s.%s' % (v[2], v[1]) for v in depd.values()]
> bb.parse.siggen.dump_lockedsigs(sigfile, tasks)
>
> -def prune_lockedsigs(excluded_tasks, excluded_targets, lockedsigs,
> pruned_output):
> +def prune_lockedsigs(excluded_tasks, excluded_targets, lockedsigs,
>
[OE-core] ✗ patchtest: failure for oeqa: reproducible: Do two clean builds
== Series Details == Series: oeqa: reproducible: Do two clean builds Revision: 1 URL : https://patchwork.openembedded.org/series/19569/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the proposed series by patchtest resulting in the following failures: * Issue Series does not apply on top of target branch [test_series_merge_on_head] Suggested fixRebase your series on top of targeted branch Targeted branch master (currently at fb064356af) If you believe any of these test results are incorrect, please reply to the mailing list (openembedded-core@lists.openembedded.org) raising your concerns. Otherwise we would appreciate you correcting the issues and submitting a new version of the patchset if applicable. Please ensure you add/increment the version number when sending the new version (i.e. [PATCH] -> [PATCH v2] -> [PATCH v3] -> ...). --- Guidelines: https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 0/5] kernel-yocto: misc build / config changes
> > FWIW: lttng-ust builds fine for me with the 5.2 kernel + 5.2 headers, > it is one of the things I build and test as part of > core-image-kernel-dev. Even on ppc? It seems related to the y2038 safe socket merge (a98dc6aee784a5daf84a4781dcf02feab9ad5999) from the kernel but from the code I cannot find a reason why SO_SNDTIMEO would be missing. The powerpc socket header relies on the generic one for proper backward definition of SO_SNDTIMEO: #define SO_SNDTIMEO (sizeof(time_t) == sizeof(__kernel_long_t) ? SO_SNDTIMEO_OLD : SO_SNDTIMEO_NEW) Not sure what is going on here. > I just rebuilt it here this morning and didn't see any errors. > > > > > > > qemuarm is erroring due to /dev/fb0 disappearing, which is probably > > > kernel? > > > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/53/builds/975 > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/38/builds/976 > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/47/builds/986 > > > > > > and we also have an unintended side effect multilib build failure: > > > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/44/builds/995 > > > > > > which might be due to changed dependencies, I need to check into that one > > > further. > > > > > > Cheers, > > > > > > Richard > > > > > > > > > > > > -- > > - Thou shalt not follow the NULL pointer, for chaos and madness await > > thee at its end > > - "Use the force Harry" - Gandalf, Star Trek II > > > > -- > - Thou shalt not follow the NULL pointer, for chaos and madness await > thee at its end > - "Use the force Harry" - Gandalf, Star Trek II -- Jonathan Rajotte-Julien EfficiOS -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 0/5] kernel-yocto: misc build / config changes
On Thu, Aug 29, 2019 at 11:31 AM Bruce Ashfield wrote: > > On Thu, Aug 29, 2019 at 11:28 AM Jonathan Rajotte-Julien > wrote: > > > > > > > > FWIW: lttng-ust builds fine for me with the 5.2 kernel + 5.2 headers, > > > it is one of the things I build and test as part of > > > core-image-kernel-dev. > > > > Even on ppc? > > > > yup. I build all arches for core-image-kernel-dev, which includes all of > lttng. but I've recently switched to RP's master-next branch, so hopefully a difference in the configs will pop out. Bruce > > Bruce > > > It seems related to the y2038 safe socket merge > > (a98dc6aee784a5daf84a4781dcf02feab9ad5999) from the kernel but from the > > code I cannot find a reason why SO_SNDTIMEO would be missing. The powerpc > > socket header relies on the generic one for proper backward definition of > > SO_SNDTIMEO: > > > > #define SO_SNDTIMEO (sizeof(time_t) == sizeof(__kernel_long_t) ? > > SO_SNDTIMEO_OLD : SO_SNDTIMEO_NEW) > > > > Not sure what is going on here. > > > > > > > I just rebuilt it here this morning and didn't see any errors. > > > > > > > > > > > > > > > qemuarm is erroring due to /dev/fb0 disappearing, which is probably > > > > > kernel? > > > > > > > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/53/builds/975 > > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/38/builds/976 > > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/47/builds/986 > > > > > > > > > > and we also have an unintended side effect multilib build failure: > > > > > > > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/44/builds/995 > > > > > > > > > > which might be due to changed dependencies, I need to check into that > > > > > one further. > > > > > > > > > > Cheers, > > > > > > > > > > Richard > > > > > > > > > > > > > > > > > > > > > > -- > > > > - Thou shalt not follow the NULL pointer, for chaos and madness await > > > > thee at its end > > > > - "Use the force Harry" - Gandalf, Star Trek II > > > > > > > > > > > > -- > > > - Thou shalt not follow the NULL pointer, for chaos and madness await > > > thee at its end > > > - "Use the force Harry" - Gandalf, Star Trek II > > > > -- > > Jonathan Rajotte-Julien > > EfficiOS > > > > -- > - Thou shalt not follow the NULL pointer, for chaos and madness await > thee at its end > - "Use the force Harry" - Gandalf, Star Trek II -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH v2 1/2] uboot-sign: Refactor do_deploy prefunc to do_deploy_prepend
When inherited by the u-boot recipe (UBOOT_PN), uboot-sign.bbclass adds
a concat_dtb step, which places additional files into ${DEPLOYDIR}
before do_deploy.
The use of prefuncs for this prevents us from adding
do_deploy[cleandirs] = "${DEPLOYDIR}"
because that would remove the files produced by the prefunc.
Thus, it seems good to make concat_dtb a part of do_deploy, such that it
runs after removal of do_deploy's cleandirs. As before, care is taken to
not interfere with the kernel's do_deploy definition, since concat_dtb
was only needed for u-boot.
I tested this with poky, putting the following in local.conf:
UBOOT_SIGN_ENABLE = "1"
KERNEL_CLASSES = " kernel-fitimage "
KERNEL_IMAGETYPE = "fitImage"
and then doing
bitbake core-image-minimal
bitbake u-boot
It built successfully and concat_dtb was still called.
Signed-off-by: Daniel Klauer
---
meta/classes/uboot-sign.bbclass | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/meta/classes/uboot-sign.bbclass b/meta/classes/uboot-sign.bbclass
index 982ed46d01..713196df41 100644
--- a/meta/classes/uboot-sign.bbclass
+++ b/meta/classes/uboot-sign.bbclass
@@ -117,15 +117,16 @@ do_install_append() {
fi
}
+do_deploy_prepend_pn-${UBOOT_PN}() {
+ if [ "${UBOOT_SIGN_ENABLE}" = "1" -a -n "${UBOOT_DTB_BINARY}" ]; then
+ concat_dtb
+ fi
+}
+
python () {
if d.getVar('UBOOT_SIGN_ENABLE') == '1' and d.getVar('PN') ==
d.getVar('UBOOT_PN') and d.getVar('UBOOT_DTB_BINARY'):
kernel_pn = d.getVar('PREFERRED_PROVIDER_virtual/kernel')
# Make "bitbake u-boot -cdeploy" deploys the signed u-boot.dtb
d.appendVarFlag('do_deploy', 'depends', ' %s:do_deploy' % kernel_pn)
-
-# kernerl's do_deploy is a litle special, so we can't use
-# do_deploy_append, otherwise it would override
-# kernel_do_deploy.
-d.appendVarFlag('do_deploy', 'prefuncs', ' concat_dtb')
}
--
2.17.1
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] oeqa: reproducible: Do two clean builds
Perform two clean builds without sstate instead of one partial rebuild
with sstate and one clean build without. There are some classes of
reproducibility issues that this solves, and while we would like to
resolve them in the long term the direction to do so is not currently
clear.
Signed-off-by: Joshua Watt
---
meta/lib/oeqa/selftest/cases/reproducible.py | 48
1 file changed, 28 insertions(+), 20 deletions(-)
diff --git a/meta/lib/oeqa/selftest/cases/reproducible.py
b/meta/lib/oeqa/selftest/cases/reproducible.py
index c6cc0b7d0eb..b3bbb70158b 100644
--- a/meta/lib/oeqa/selftest/cases/reproducible.py
+++ b/meta/lib/oeqa/selftest/cases/reproducible.py
@@ -123,45 +123,53 @@ class ReproducibleTests(OESelftestTestCase):
def test_reproducible_builds(self):
capture_vars = ['DEPLOY_DIR_' + c.upper() for c in
self.package_classes]
+# Build native utilities
+self.write_config('')
+bitbake("diffutils-native -c addto_recipe_sysroot")
+diffutils_sysroot = get_bb_var("RECIPE_SYSROOT_NATIVE",
"diffutils-native")
+
+# Reproducible builds should not pull from sstate or mirrors, but
+# sharing DL_DIR is fine
common_config = textwrap.dedent('''\
INHERIT += "reproducible_build"
PACKAGE_CLASSES = "%s"
+SSTATE_DIR = "${TMPDIR}/sstate"
+SSTATE_MIRROR = ""
''') % (' '.join('package_%s' % c for c in self.package_classes))
-# Do an initial build. It's acceptable for this build to use sstate
-self.write_config(common_config)
-vars_reference = get_bb_vars(capture_vars)
-bitbake(' '.join(self.images))
+# Perform a build.
+reproducibleA_tmp = os.path.join(self.topdir, 'reproducibleA', 'tmp')
+if os.path.exists(reproducibleA_tmp):
+bb.utils.remove(reproducibleA_tmp, recurse=True)
-# Build native utilities
-bitbake("diffutils-native -c addto_recipe_sysroot")
-diffutils_sysroot = get_bb_var("RECIPE_SYSROOT_NATIVE",
"diffutils-native")
+self.write_config((textwrap.dedent('''\
+TMPDIR = "%s"
+''') % reproducibleA_tmp) + common_config)
+vars_A = get_bb_vars(capture_vars)
+bitbake(' '.join(self.images))
-reproducible_tmp = os.path.join(self.topdir, 'reproducible', 'tmp')
-if os.path.exists(reproducible_tmp):
-bb.utils.remove(reproducible_tmp, recurse=True)
+# Perform another build.
+reproducibleB_tmp = os.path.join(self.topdir, 'reproducibleB', 'tmp')
+if os.path.exists(reproducibleB_tmp):
+bb.utils.remove(reproducibleB_tmp, recurse=True)
-# Perform another build. This build should *not* share sstate or pull
-# from any mirrors, but sharing a DL_DIR is fine
self.write_config((textwrap.dedent('''\
TMPDIR = "%s"
-SSTATE_DIR = "${TMPDIR}/sstate"
-SSTATE_MIRROR = ""
-''') % reproducible_tmp) + common_config)
-vars_test = get_bb_vars(capture_vars)
+''') % reproducibleB_tmp) + common_config)
+vars_B = get_bb_vars(capture_vars)
bitbake(' '.join(self.images))
-# NOTE: The temp directory from the reproducible build is purposely
+# NOTE: The temp directories from the reproducible build are purposely
# kept after the build so it can be diffed for debugging.
for c in self.package_classes:
with self.subTest(package_class=c):
package_class = 'package_' + c
-deploy_reference = vars_reference['DEPLOY_DIR_' + c.upper()]
-deploy_test = vars_test['DEPLOY_DIR_' + c.upper()]
+deploy_A = vars_A['DEPLOY_DIR_' + c.upper()]
+deploy_B = vars_B['DEPLOY_DIR_' + c.upper()]
-result = self.compare_packages(deploy_reference, deploy_test,
diffutils_sysroot)
+result = self.compare_packages(deploy_A, deploy_B,
diffutils_sysroot)
self.logger.info('Reproducibility summary for %s: %s' % (c,
result))
--
2.21.0
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 0/5] kernel-yocto: misc build / config changes
On Thu, Aug 29, 2019 at 11:28 AM Jonathan Rajotte-Julien wrote: > > > > > FWIW: lttng-ust builds fine for me with the 5.2 kernel + 5.2 headers, > > it is one of the things I build and test as part of > > core-image-kernel-dev. > > Even on ppc? > yup. I build all arches for core-image-kernel-dev, which includes all of lttng. Bruce > It seems related to the y2038 safe socket merge > (a98dc6aee784a5daf84a4781dcf02feab9ad5999) from the kernel but from the > code I cannot find a reason why SO_SNDTIMEO would be missing. The powerpc > socket header relies on the generic one for proper backward definition of > SO_SNDTIMEO: > > #define SO_SNDTIMEO (sizeof(time_t) == sizeof(__kernel_long_t) ? > SO_SNDTIMEO_OLD : SO_SNDTIMEO_NEW) > > Not sure what is going on here. > > > > I just rebuilt it here this morning and didn't see any errors. > > > > > > > > > > > qemuarm is erroring due to /dev/fb0 disappearing, which is probably > > > > kernel? > > > > > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/53/builds/975 > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/38/builds/976 > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/47/builds/986 > > > > > > > > and we also have an unintended side effect multilib build failure: > > > > > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/44/builds/995 > > > > > > > > which might be due to changed dependencies, I need to check into that > > > > one further. > > > > > > > > Cheers, > > > > > > > > Richard > > > > > > > > > > > > > > > > > -- > > > - Thou shalt not follow the NULL pointer, for chaos and madness await > > > thee at its end > > > - "Use the force Harry" - Gandalf, Star Trek II > > > > > > > > -- > > - Thou shalt not follow the NULL pointer, for chaos and madness await > > thee at its end > > - "Use the force Harry" - Gandalf, Star Trek II > > -- > Jonathan Rajotte-Julien > EfficiOS -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] btrfs-tools: Add PACKAGECONFIG knob for controlling python support
Signed-off-by: Jacob Kroon
---
.../btrfs-tools/btrfs-tools_5.2.1.bb| 17 +++--
1 file changed, 11 insertions(+), 6 deletions(-)
diff --git a/meta/recipes-devtools/btrfs-tools/btrfs-tools_5.2.1.bb
b/meta/recipes-devtools/btrfs-tools/btrfs-tools_5.2.1.bb
index 647516cf92..a364cf53ed 100644
--- a/meta/recipes-devtools/btrfs-tools/btrfs-tools_5.2.1.bb
+++ b/meta/recipes-devtools/btrfs-tools/btrfs-tools_5.2.1.bb
@@ -10,7 +10,7 @@ HOMEPAGE = "https://btrfs.wiki.kernel.org;
LICENSE = "GPLv2"
LIC_FILES_CHKSUM = "file://COPYING;md5=fcb02dc552a041dee27e4b85c7396067"
SECTION = "base"
-DEPENDS = "util-linux attr e2fsprogs lzo acl python3-setuptools-native"
+DEPENDS = "util-linux attr e2fsprogs lzo acl"
DEPENDS_append_class-target = " udev"
RDEPENDS_${PN} = "libgcc"
@@ -19,13 +19,16 @@ SRC_URI =
"git://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git \
file://0001-Add-a-possibility-to-specify-where-python-modules-ar.patch \
"
-inherit autotools-brokensep pkgconfig manpages distutils3-base
-
-CLEANBROKEN = "1"
-
+PACKAGECONFIG ??= "python"
PACKAGECONFIG[manpages] = "--enable-documentation, --disable-documentation,
asciidoc-native xmlto-native"
+PACKAGECONFIG[python] =
"--enable-python,--disable-python,python3-setuptools-native"
PACKAGECONFIG[zstd] = "--enable-zstd,--disable-zstd,zstd"
+inherit autotools-brokensep pkgconfig manpages
+inherit ${@bb.utils.contains('PACKAGECONFIG', 'python', 'distutils3-base', '',
d)}
+
+CLEANBROKEN = "1"
+
EXTRA_OECONF_append_libc-musl = " --disable-backtrace "
EXTRA_PYTHON_CFLAGS = "${DEBUG_PREFIX_MAP}"
EXTRA_PYTHON_CFLAGS_class-native = ""
@@ -41,7 +44,9 @@ do_configure_prepend() {
S = "${WORKDIR}/git"
do_install_append() {
-oe_runmake 'DESTDIR=${D}'
'PYTHON_SITEPACKAGES_DIR=${PYTHON_SITEPACKAGES_DIR}' install_python
+if [ "${@bb.utils.filter('PACKAGECONFIG', 'python', d)}" ]; then
+oe_runmake 'DESTDIR=${D}'
'PYTHON_SITEPACKAGES_DIR=${PYTHON_SITEPACKAGES_DIR}' install_python
+fi
}
BBCLASSEXTEND = "native"
--
2.21.0
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH v2] serial-getty@.service: Allow device to fast fail if it does not exist
Some BSPs use a USB serial port which may or may not actually be plugged all the time. It is quite useful to have a USB serial port have a getty running but it does not make sense to wait for it for 90 seconds before completing the system startup if it might never get plugged in. The typical example is that a USB serial device might only need to be plugged in when debugging, upgrading, or initially configuring a device. This change is somewhat subtle. Systemd uses the "BindsTo" directive to ensure existence of the device in order to start the service as well as to terminate the service if the device goes away. The "After" directive makes that same relationship stronger. When used together this has the undesired side effect that systemd will wait until its internal time out value of 90 seconds for the device to come on line before executing a fail operation or letting other tasks and groups continue. This is certainly the kind of behavior we want for a disk, but not for serial ports in general. The "BindsTo" directive is replaced by the combination of the "PartOf" and the "ConditionPathExists" directives. The "After" directive is unchanged because that will wait for the udev rules to process. The "PartOf" directive will issue a stop to the getty service if the device goes away, similar to the "BindsTo" directive. The "ConditionPathExists" is what allows the service to fail fast vs waiting for the timeout. When a USB device is not plugged in at boot you would find a message in the system journal like: systemd[1]: Condition check resulted in Serial Getty on \ ttyUSB0 being skipped. If you want to observe the problem with qemu, it is easy to replicate. Simply add the following line to your local.conf for a x86-64 qemu build. SERIAL_CONSOLES="115200;ttyS0 115200;ttyUSB0" Login right after the system boots and observe: root@qemux86-64:~# systemctl list-jobs |cat JOB UNIT TYPE STATE 1 multi-user.targetstart waiting 69 serial-getty@ttyUSB0.service start waiting 64 getty.target start waiting 71 dev-ttyUSB0.device start running 62 systemd-update-utmp-runlevel.service start waiting 5 jobs listed. You can see above that the dev-ttyUSB0.device will block for 1min 30 seconds. While that might not be a problem for this reference build. It is certainly a problem for images that have software watchdogs that verify the system booted up all the way to systemd completion in less than 90 seconds. This other nice effect of this change is that the fast fail device extend to additional serial ports that may not exist on ARM BSPs or that might be configured in or out by the dtb files on different boards. Signed-off-by: Jason Wessel --- .../systemd/systemd-serialgetty/serial-getty@.service | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/meta/recipes-core/systemd/systemd-serialgetty/serial-getty@.service b/meta/recipes-core/systemd/systemd-serialgetty/serial-getty@.service index e8b027e97d..15af16a9f8 100644 --- a/meta/recipes-core/systemd/systemd-serialgetty/serial-getty@.service +++ b/meta/recipes-core/systemd/systemd-serialgetty/serial-getty@.service @@ -9,7 +9,8 @@ Description=Serial Getty on %I Documentation=man:agetty(8) man:systemd-getty-generator(8) Documentation=http://0pointer.de/blog/projects/serial-console.html -BindsTo=dev-%i.device +PartOf=dev-%i.device +ConditionPathExists=/dev/%i After=dev-%i.device systemd-user-sessions.service plymouth-quit-wait.service After=rc-local.service -- 2.21.0 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] ca-certificates: Fix reproducibilty and multilib issue
This command was dependent on the order of files on the disk and for multilib
builds
could result in:
Error: Transaction check error:
file /etc/ca-certificates.conf conflicts between attempted installs of
ca-certificates-20190110-r0.core2_32 and
lib64-ca-certificates-20190110-r0.x86_64
Sorting the file makes things deterministic.
Signed-off-by: Richard Purdie
---
.../recipes-support/ca-certificates/ca-certificates_20190110.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-support/ca-certificates/ca-certificates_20190110.bb
b/meta/recipes-support/ca-certificates/ca-certificates_20190110.bb
index efd9eaa71e4..7d87da10bb5 100644
--- a/meta/recipes-support/ca-certificates/ca-certificates_20190110.bb
+++ b/meta/recipes-support/ca-certificates/ca-certificates_20190110.bb
@@ -53,7 +53,7 @@ do_install () {
echo "# Lines starting with ! will remove certificate on next update"
echo "#"
find ${D}${datadir}/ca-certificates -type f -name '*.crt' | \
-sed 's,^${D}${datadir}/ca-certificates/,,'
+sed 's,^${D}${datadir}/ca-certificates/,,' | sort
} >${D}${sysconfdir}/ca-certificates.conf
}
--
2.20.1
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 2/2] qemu: Fix dependency of PACKAGECONFIG libcurl
From: He Zhe When PACKAGECONFIG libcurl is enabled, we would get the following build failure. ERROR: Nothing PROVIDES 'libcurl' (but perf.bb DEPENDS on or otherwise requires it). Close matches: The dependency should be curl. Signed-off-by: He Zhe --- meta/recipes-devtools/qemu/qemu.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-devtools/qemu/qemu.inc b/meta/recipes-devtools/qemu/qemu.inc index 3eeba6e..241f9db 100644 --- a/meta/recipes-devtools/qemu/qemu.inc +++ b/meta/recipes-devtools/qemu/qemu.inc @@ -132,7 +132,7 @@ PACKAGECONFIG[xen] = "--enable-xen,--disable-xen,xen,xen-libxenstore xen-libxenc PACKAGECONFIG[vnc-sasl] = "--enable-vnc --enable-vnc-sasl,--disable-vnc-sasl,cyrus-sasl," PACKAGECONFIG[vnc-jpeg] = "--enable-vnc --enable-vnc-jpeg,--disable-vnc-jpeg,jpeg," PACKAGECONFIG[vnc-png] = "--enable-vnc --enable-vnc-png,--disable-vnc-png,libpng," -PACKAGECONFIG[libcurl] = "--enable-curl,--disable-curl,libcurl," +PACKAGECONFIG[libcurl] = "--enable-curl,--disable-curl,curl," PACKAGECONFIG[nss] = "--enable-smartcard,--disable-smartcard,nss," PACKAGECONFIG[curses] = "--enable-curses,--disable-curses,ncurses," PACKAGECONFIG[gtk+] = "--enable-gtk,--disable-gtk,gtk+3 gettext-native" -- 2.7.4 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/2] qemu: Add pkg-config handling for libgcrypt
From: He Zhe
When PACKAGECONFIG libgcrypt is enabled, we would get the following error.
ERROR: /usr/bin/libgcrypt-config should not be used, use an alternative such as
pkg-config
In oe-core, libgcrypt has been turned to be configured with pkg-config instead
of libgcrypt-config, but qemu configure script does not contain pkg-config
related part for libgcrypt to handle it.
Signed-off-by: He Zhe
---
meta/recipes-devtools/qemu/qemu.inc| 1 +
...ure-Add-pkg-config-handling-for-libgcrypt.patch | 93 ++
2 files changed, 94 insertions(+)
create mode 100644
meta/recipes-devtools/qemu/qemu/0010-configure-Add-pkg-config-handling-for-libgcrypt.patch
diff --git a/meta/recipes-devtools/qemu/qemu.inc
b/meta/recipes-devtools/qemu/qemu.inc
index d2dd2bc..3eeba6e 100644
--- a/meta/recipes-devtools/qemu/qemu.inc
+++ b/meta/recipes-devtools/qemu/qemu.inc
@@ -22,6 +22,7 @@ SRC_URI = "https://download.qemu.org/${BPN}-${PV}.tar.xz \
file://0007-apic-fixup-fallthrough-to-PIC.patch \
file://0008-linux-user-Fix-webkitgtk-hangs-on-32-bit-x86-target.patch \
file://0009-Fix-webkitgtk-builds.patch \
+ file://0010-configure-Add-pkg-config-handling-for-libgcrypt.patch \
"
UPSTREAM_CHECK_REGEX = "qemu-(?P\d+(\.\d+)+)\.tar"
diff --git
a/meta/recipes-devtools/qemu/qemu/0010-configure-Add-pkg-config-handling-for-libgcrypt.patch
b/meta/recipes-devtools/qemu/qemu/0010-configure-Add-pkg-config-handling-for-libgcrypt.patch
new file mode 100644
index 000..a8ab7da
--- /dev/null
+++
b/meta/recipes-devtools/qemu/qemu/0010-configure-Add-pkg-config-handling-for-libgcrypt.patch
@@ -0,0 +1,93 @@
+From 5214dd4461f2090ef0965b4d2518f49927d61cbc Mon Sep 17 00:00:00 2001
+From: He Zhe
+Date: Wed, 28 Aug 2019 19:56:28 +0800
+Subject: [Qemu-devel] [PATCH] configure: Add pkg-config handling for libgcrypt
+
+libgcrypt may also be controlled by pkg-config, this patch adds pkg-config
+handling for libgcrypt.
+
+Upstream-Status: Denied
[https://lists.nongnu.org/archive/html/qemu-devel/2019-08/msg06333.html]
+
+Signed-off-by: He Zhe
+---
+ configure | 48
+ 1 file changed, 40 insertions(+), 8 deletions(-)
+
+diff --git a/configure b/configure
+index e44e454..0f362a7 100755
+--- a/configure
b/configure
+@@ -2875,6 +2875,30 @@ has_libgcrypt() {
+ return 0
+ }
+
++has_libgcrypt_pkgconfig() {
++if ! has $pkg_config ; then
++return 1
++fi
++
++if ! $pkg_config --list-all | grep libgcrypt > /dev/null 2>&1 ; then
++return 1
++fi
++
++if test -n "$cross_prefix" ; then
++host=$($pkg_config --variable=host libgcrypt)
++if test "${host%-gnu}-" != "${cross_prefix%-gnu}" ; then
++print_error "host($host) does not match
cross_prefix($cross_prefix)"
++return 1
++fi
++fi
++
++if ! $pkg_config --atleast-version=1.5.0 libgcrypt ; then
++print_error "libgcrypt version is $($pkg_config --modversion
libgcrypt)"
++return 1
++fi
++
++return 0
++}
+
+ if test "$nettle" != "no"; then
+ pass="no"
+@@ -2902,7 +2926,14 @@ fi
+
+ if test "$gcrypt" != "no"; then
+ pass="no"
+-if has_libgcrypt; then
++if has_libgcrypt_pkgconfig; then
++gcrypt_cflags=$($pkg_config --cflags libgcrypt)
++if test "$static" = "yes" ; then
++gcrypt_libs=$($pkg_config --libs --static libgcrypt)
++else
++gcrypt_libs=$($pkg_config --libs libgcrypt)
++fi
++elif has_libgcrypt; then
+ gcrypt_cflags=$(libgcrypt-config --cflags)
+ gcrypt_libs=$(libgcrypt-config --libs)
+ # Debian has removed -lgpg-error from libgcrypt-config
+@@ -2912,15 +2943,16 @@ if test "$gcrypt" != "no"; then
+ then
+ gcrypt_libs="$gcrypt_libs -lgpg-error"
+ fi
++fi
+
+-# Link test to make sure the given libraries work (e.g for static).
+-write_c_skeleton
+-if compile_prog "" "$gcrypt_libs" ; then
+-LIBS="$gcrypt_libs $LIBS"
+-QEMU_CFLAGS="$QEMU_CFLAGS $gcrypt_cflags"
+-pass="yes"
+-fi
++# Link test to make sure the given libraries work (e.g for static).
++write_c_skeleton
++if compile_prog "" "$gcrypt_libs" ; then
++ LIBS="$gcrypt_libs $LIBS"
++ QEMU_CFLAGS="$QEMU_CFLAGS $gcrypt_cflags"
++ pass="yes"
+ fi
++
+ if test "$pass" = "yes"; then
+ gcrypt="yes"
+ cat > $TMPC << EOF
+--
+2.7.4
+
--
2.7.4
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 4/8] kernel-devsrc: remove python2 dependency
On Thu, 29 Aug 2019 at 14:54, Adrian Bunk wrote: > > It is an unexpected meaning of "zero risk" when this excludes > breakages with kernels other than the ones in master. > > One of the non-python changes to perf blew up the build for me even when > trying with a kernel that is only a few months behind on the 4.19 branch, > so there's some patches for me to send next month. > This is part and parcel of using the master branch with various 'other' layers. Things can and do break in those other layers, and have to be fixed after the fact of the breaking changes landing in master. If this is not acceptable, then stable branches are far more conservative. Alex -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 1/2] uboot-sign: Refactor do_deploy prefunc to do_deploy_prepend
On Thu, 2019-08-29 at 11:05 +0200, Daniel Klauer wrote:
> > That commit message isn't correct.
> >
> > It removes cleandirs for the prefunc at the start of the prefunc and
> > cleandirs for the main function at the start of that main function.
>
> Oh ok, so the prefuncs/postfuncs can have their own [cleandirs], that's
> interesting.
>
> How about the following (trying to find a good way to explain it):
Yes, that sounds fine. The bit in brackets probably isn't needed.
Cheers,
Richard
>
> -
> When inherited by the u-boot recipe (UBOOT_PN), uboot-sign.bbclass adds
> a concat_dtb step, which places additional files into ${DEPLOYDIR}
> before do_deploy.
>
> The use of prefuncs for this prevents us from adding
> do_deploy[cleandirs] = "${DEPLOYDIR}"
> because that would remove the files produced by the prefunc.
> (Each of prefuncs/task/postfuncs functions has their own cleandirs, and
> each function's cleandirs are removed at the start of that function.)
>
> Thus, it seems good to make concat_dtb a part of do_deploy, such that it
> runs after removal of do_deploy's cleandirs. As before, care is taken to
> not interfere with the kernel's do_deploy definition, since concat_dtb
> was only needed for u-boot.
> -
>
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 4/8] kernel-devsrc: remove python2 dependency
On Thu, Aug 29, 2019 at 08:23:58AM -0400, Bruce Ashfield wrote: > On Thu, Aug 29, 2019 at 2:32 AM Adrian Bunk wrote: > > > > On Wed, Aug 28, 2019 at 06:06:04PM -0400, Bruce Ashfield wrote: > > > On Wed, Aug 28, 2019 at 5:58 PM Adrian Bunk wrote: > > > > > > > > On Wed, Aug 28, 2019 at 04:11:43PM -0400, Bruce Ashfield wrote: > > > > >... > > > > > There's zero risk to these, and no reason to sit on them. > > > > > > > > What range of LTS kernels is covered by the "zero risk"? > > > > > > It has nothing to do with LTS kernels. >... > > How do your changes interact with a BSP layer that provides > > the upstream maintained LTS kernel 4.4? > > As mentioned in other parts of the threads, we test against the > reference kernel's in master. Other versions can either bbappend, or > send patches. That's unfortunately how it has to be. It is an unexpected meaning of "zero risk" when this excludes breakages with kernels other than the ones in master. One of the non-python changes to perf blew up the build for me even when trying with a kernel that is only a few months behind on the 4.19 branch, so there's some patches for me to send next month. > Cheers, > > Bruce cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 0/5] kernel-yocto: misc build / config changes
On Thu, Aug 29, 2019 at 8:25 AM Bruce Ashfield wrote: > > On Thu, Aug 29, 2019 at 5:29 AM wrote: > > > > On Wed, 2019-08-14 at 11:31 -0400, bruce.ashfi...@gmail.com wrote: > > > From: Bruce Ashfield > > > > > > Hi all, > > > > > > This pull request is a collection of smaller fixes that I've been > > > collecting > > > while I work through the 5.2/5.3 kernel intro, new libc-headers, etc. > > > There's > > > no reason to make them wait while I finish that work, so here they > > > are in a > > > single branch. > > > > > > There's nothing major here, just a some legwork changes, licensing > > > update > > > and a short term workaround for embedded host paths in the kernel > > > binaries. > > > > There appear to be a few issues with the new headers. ppc looks to have > > particular issues: > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/70/builds/976 > > > > Hmmm. Those must be packages not covered in my build testing. I will > have a look .. but for some of these packages, I really have no idea > and just search up the error and hope upstream has a fix :D > > Cheers, > > Bruce > > > eudev: > > > > util.lo ../../../eudev-3.2.8/src/shared/sysctl-util.c > > | ../../../eudev-3.2.8/src/shared/log.c: In function 'create_log_socket': > > | ../../../eudev-3.2.8/src/shared/log.c:123:43: error: 'SO_SNDTIMEO' > > undeclared (first use in this function); did you mean 'SO_TXTIME'? > > | 123 | (void) setsockopt(fd, SOL_SOCKET, SO_SNDTIMEO, , > > sizeof(tv)); > > | | ^~~ > > | | SO_TXTIME > > | ../../../eudev-3.2.8/src/shared/log.c:123:43: note: each undeclared > > identifier is reported only once for each function it appears in > > > > neard: > > > > ../neard-0.16/plugins/p2p.c: In function 'p2p_connect_blocking': > > ../neard-0.16/plugins/p2p.c:324:33: error: 'SO_RCVTIMEO' undeclared (first > > use in this function); did you mean 'SO_RCVTIMEO_OLD'? > > 324 | if (setsockopt(fd, SOL_SOCKET, SO_RCVTIMEO, (char *), > > | ^~~ > > | SO_RCVTIMEO_OLD > > ../neard-0.16/plugins/p2p.c:324:33: note: each undeclared identifier is > > reported only once for each function it appears in > > ../neard-0.16/plugins/p2p.c:328:33: error: 'SO_SNDTIMEO' undeclared (first > > use in this function); did you mean 'SO_TXTIME'? > > 328 | if (setsockopt(fd, SOL_SOCKET, SO_SNDTIMEO, (char *), > > | ^~~ > > | SO_TXTIME > > ../neard-0.16/plugins/p2p.c: In function 'p2p_connect': > > ../neard-0.16/plugins/p2p.c:555:33: error: 'SO_RCVTIMEO' undeclared (first > > use in this function); did you mean 'SO_RCVTIMEO_OLD'? > > 555 | if (setsockopt(fd, SOL_SOCKET, SO_RCVTIMEO, (char *), > > | ^~~ > > | SO_RCVTIMEO_OLD > > ../neard-0.16/plugins/p2p.c:559:33: error: 'SO_SNDTIMEO' undeclared (first > > use in this function); did you mean 'SO_TXTIME'? > > 559 | if (setsockopt(fd, SOL_SOCKET, SO_SNDTIMEO, (char *), > > | ^~~ > > | SO_TXTIME > > Makefile:1973: recipe for target 'plugins/src_neard-p2p.o' failed > > make[1]: *** [plugins/src_neard-p2p.o] Error 1 > > > > and errors from lttng-ust (cc'd Jonathan). FWIW: lttng-ust builds fine for me with the 5.2 kernel + 5.2 headers, it is one of the things I build and test as part of core-image-kernel-dev. I just rebuilt it here this morning and didn't see any errors. Bruce > > > > qemuarm is erroring due to /dev/fb0 disappearing, which is probably kernel? > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/53/builds/975 > > https://autobuilder.yoctoproject.org/typhoon/#/builders/38/builds/976 > > https://autobuilder.yoctoproject.org/typhoon/#/builders/47/builds/986 > > > > and we also have an unintended side effect multilib build failure: > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/44/builds/995 > > > > which might be due to changed dependencies, I need to check into that one > > further. > > > > Cheers, > > > > Richard > > > > > > > -- > - Thou shalt not follow the NULL pointer, for chaos and madness await > thee at its end > - "Use the force Harry" - Gandalf, Star Trek II -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH v2] linux-yocto: introduce 5.2 recipes
On Thu, Aug 29, 2019 at 8:39 AM Alexander Kanavin wrote: > > On Wed, 28 Aug 2019 at 22:10, wrote: >> >> +KERNEL_FEATURES_append_qemuall=" cfg/virtio.scc" >> +KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc" >> +KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc cfg/paravirt_kvm.scc" > > > The new kernels are missing the drm-bochs tweaks done recently to previous > kernels: > http://git.yoctoproject.org/cgit.cgi/poky/commit/?h=master=0e0589f81a66f92519e1fbb0d0ab6db22e0e591e > > Perhaps we should put them into a common include? We could, but I just made my new recipes and completely forgot (human error). That was the only window that it could happen and there's no way it would happen again. Thanks for pointing that out, I'll update the recipes and send them out with my next version. After everything settled, I can look into moving them to a feature include. Bruce > > Alex -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH v2] linux-yocto: introduce 5.2 recipes
On Wed, 28 Aug 2019 at 22:10, wrote: > +KERNEL_FEATURES_append_qemuall=" cfg/virtio.scc" > +KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc" > +KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc cfg/paravirt_kvm.scc" > The new kernels are missing the drm-bochs tweaks done recently to previous kernels: http://git.yoctoproject.org/cgit.cgi/poky/commit/?h=master=0e0589f81a66f92519e1fbb0d0ab6db22e0e591e Perhaps we should put them into a common include? Alex -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 1/5] kernel-devsrc: tweak for v5.3+
On Thu, Aug 29, 2019 at 5:17 AM Mittal, Anuj wrote: > > On Wed, 2019-08-14 at 11:31 -0400, bruce.ashfi...@gmail.com wrote: > > From: Bruce Ashfield > > > > The 5.3 kernel has two changes that require tweaks to the minimal > > kernel-devsrc package. > > > > - 4ce97317f [x86/purgatory: Do not use __builtin_memcpy and > > __builtin_memset] > > > > This change removes the need for arch/x86/purgatory/string.c and > > instead reuses a copy in arch/x86/boot/compressed/, so we can't > > copy > > the file anymore. To support older kernels, we make the copy > > survive > > the non-existence of the file. > > > > This change was merged in 4.19 stable kernel as well. Can this be > merged in our stable branches as well please? It already is (just not pushed), I just wasn't doing -stable updates along with 5.2 intro .. there's only so many things I can debug and regression test at one time. Hopefully I'll get through the 5.2 work soon and finish the rest of my queue. Cheers, Bruce > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.19.y=e0d262a57fc741a9b362e458c714e37a77ddb62d > > Thanks, > > Anuj -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 0/5] kernel-yocto: misc build / config changes
On Thu, Aug 29, 2019 at 5:29 AM wrote: > > On Wed, 2019-08-14 at 11:31 -0400, bruce.ashfi...@gmail.com wrote: > > From: Bruce Ashfield > > > > Hi all, > > > > This pull request is a collection of smaller fixes that I've been > > collecting > > while I work through the 5.2/5.3 kernel intro, new libc-headers, etc. > > There's > > no reason to make them wait while I finish that work, so here they > > are in a > > single branch. > > > > There's nothing major here, just a some legwork changes, licensing > > update > > and a short term workaround for embedded host paths in the kernel > > binaries. > > There appear to be a few issues with the new headers. ppc looks to have > particular issues: > > https://autobuilder.yoctoproject.org/typhoon/#/builders/70/builds/976 > Hmmm. Those must be packages not covered in my build testing. I will have a look .. but for some of these packages, I really have no idea and just search up the error and hope upstream has a fix :D Cheers, Bruce > eudev: > > util.lo ../../../eudev-3.2.8/src/shared/sysctl-util.c > | ../../../eudev-3.2.8/src/shared/log.c: In function 'create_log_socket': > | ../../../eudev-3.2.8/src/shared/log.c:123:43: error: 'SO_SNDTIMEO' > undeclared (first use in this function); did you mean 'SO_TXTIME'? > | 123 | (void) setsockopt(fd, SOL_SOCKET, SO_SNDTIMEO, , > sizeof(tv)); > | | ^~~ > | | SO_TXTIME > | ../../../eudev-3.2.8/src/shared/log.c:123:43: note: each undeclared > identifier is reported only once for each function it appears in > > neard: > > ../neard-0.16/plugins/p2p.c: In function 'p2p_connect_blocking': > ../neard-0.16/plugins/p2p.c:324:33: error: 'SO_RCVTIMEO' undeclared (first > use in this function); did you mean 'SO_RCVTIMEO_OLD'? > 324 | if (setsockopt(fd, SOL_SOCKET, SO_RCVTIMEO, (char *), > | ^~~ > | SO_RCVTIMEO_OLD > ../neard-0.16/plugins/p2p.c:324:33: note: each undeclared identifier is > reported only once for each function it appears in > ../neard-0.16/plugins/p2p.c:328:33: error: 'SO_SNDTIMEO' undeclared (first > use in this function); did you mean 'SO_TXTIME'? > 328 | if (setsockopt(fd, SOL_SOCKET, SO_SNDTIMEO, (char *), > | ^~~ > | SO_TXTIME > ../neard-0.16/plugins/p2p.c: In function 'p2p_connect': > ../neard-0.16/plugins/p2p.c:555:33: error: 'SO_RCVTIMEO' undeclared (first > use in this function); did you mean 'SO_RCVTIMEO_OLD'? > 555 | if (setsockopt(fd, SOL_SOCKET, SO_RCVTIMEO, (char *), > | ^~~ > | SO_RCVTIMEO_OLD > ../neard-0.16/plugins/p2p.c:559:33: error: 'SO_SNDTIMEO' undeclared (first > use in this function); did you mean 'SO_TXTIME'? > 559 | if (setsockopt(fd, SOL_SOCKET, SO_SNDTIMEO, (char *), > | ^~~ > | SO_TXTIME > Makefile:1973: recipe for target 'plugins/src_neard-p2p.o' failed > make[1]: *** [plugins/src_neard-p2p.o] Error 1 > > and errors from lttng-ust (cc'd Jonathan). > > qemuarm is erroring due to /dev/fb0 disappearing, which is probably kernel? > > https://autobuilder.yoctoproject.org/typhoon/#/builders/53/builds/975 > https://autobuilder.yoctoproject.org/typhoon/#/builders/38/builds/976 > https://autobuilder.yoctoproject.org/typhoon/#/builders/47/builds/986 > > and we also have an unintended side effect multilib build failure: > > https://autobuilder.yoctoproject.org/typhoon/#/builders/44/builds/995 > > which might be due to changed dependencies, I need to check into that one > further. > > Cheers, > > Richard > > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 4/8] kernel-devsrc: remove python2 dependency
On Thu, Aug 29, 2019 at 2:32 AM Adrian Bunk wrote: > > On Wed, Aug 28, 2019 at 06:06:04PM -0400, Bruce Ashfield wrote: > > On Wed, Aug 28, 2019 at 5:58 PM Adrian Bunk wrote: > > > > > > On Wed, Aug 28, 2019 at 04:11:43PM -0400, Bruce Ashfield wrote: > > > >... > > > > There's zero risk to these, and no reason to sit on them. > > > > > > What range of LTS kernels is covered by the "zero risk"? > > > > It has nothing to do with LTS kernels. > > virtual/kernel is special since real products have this provided by > a BSP layer instead of using the kernels for the reference platforms > that ship with Yocto. I'm quite aware of what virtual/kernel is, and how it is used. > > How do your changes interact with a BSP layer that provides > the upstream maintained LTS kernel 4.4? As mentioned in other parts of the threads, we test against the reference kernel's in master. Other versions can either bbappend, or send patches. That's unfortunately how it has to be. Cheers, Bruce > > > Cheers, > > > > Bruce > > cu > Adrian > > -- > >"Is there not promise of rain?" Ling Tan asked suddenly out > of the darkness. There had been need of rain for many days. >"Only a promise," Lao Er said. >Pearl S. Buck - Dragon Seed > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] linux-yocto_5.2.bb: Fix build races in kernel-selftests
I'll merge this directly to the 5.2 branches, rather than patches (but
you knew I'd say that). I'll queue it and run some tests ASAP.
Bruce
On Thu, Aug 29, 2019 at 12:53 AM Khem Raj wrote:
>
> Signed-off-by: Khem Raj
> Cc: Bruce Ashfield
> ---
> ...x-test_verifier-test_maps-make-depen.patch | 58 +
> ...ructure-test_-progs-maps-verifier-te.patch | 86 +++
> meta/recipes-kernel/linux/linux-yocto_5.2.bb | 3 +
> 3 files changed, 147 insertions(+)
> create mode 100644
> meta/recipes-kernel/linux/files/0001-selftests-bpf-fix-test_verifier-test_maps-make-depen.patch
> create mode 100644
> meta/recipes-kernel/linux/files/0002-selftests-bpf-structure-test_-progs-maps-verifier-te.patch
>
> diff --git
> a/meta/recipes-kernel/linux/files/0001-selftests-bpf-fix-test_verifier-test_maps-make-depen.patch
>
> b/meta/recipes-kernel/linux/files/0001-selftests-bpf-fix-test_verifier-test_maps-make-depen.patch
> new file mode 100644
> index 00..e397b10cb4
> --- /dev/null
> +++
> b/meta/recipes-kernel/linux/files/0001-selftests-bpf-fix-test_verifier-test_maps-make-depen.patch
> @@ -0,0 +1,58 @@
> +From 08a2303803397c98e0f279bb6fb22afc673786a3 Mon Sep 17 00:00:00 2001
> +From: Andrii Nakryiko
> +Date: Tue, 16 Jul 2019 12:38:36 -0700
> +Subject: [PATCH 1/2] selftests/bpf: fix test_verifier/test_maps make
> + dependencies
> +
> +e46fc22e60a4 ("selftests/bpf: make directory prerequisites order-only")
> +exposed existing problem in Makefile for test_verifier and test_maps tests:
> +their dependency on auto-generated header file with a list of all tests
> wasn't
> +recorded explicitly. This patch fixes these issues.
> +
> +Fixes: 51a0e301a563 ("bpf: Add BPF_MAP_TYPE_SK_STORAGE test to test_maps")
> +Fixes: 6b7b6995c43e ("selftests: bpf: tests.h should depend on .c files, not
> the output")
> +Cc: Ilya Leoshkevich
> +Cc: Stanislav Fomichev
> +Cc: Martin KaFai Lau
> +Signed-off-by: Andrii Nakryiko
> +Signed-off-by: Alexei Starovoitov
> +---
> + tools/testing/selftests/bpf/Makefile | 6 +++---
> + 1 file changed, 3 insertions(+), 3 deletions(-)
> +
> +diff --git a/tools/testing/selftests/bpf/Makefile
> b/tools/testing/selftests/bpf/Makefile
> +index b9e88ccc289b..cd12bf414056 100644
> +--- a/tools/testing/selftests/bpf/Makefile
> b/tools/testing/selftests/bpf/Makefile
> +@@ -77,8 +77,6 @@ all: $(TEST_CUSTOM_PROGS)
> + $(OUTPUT)/urandom_read: $(OUTPUT)/%: %.c
> + $(CC) -o $@ $< -Wl,--build-id
> +
> +-$(OUTPUT)/test_maps: map_tests/*.c
> +-
> + BPFOBJ := $(OUTPUT)/libbpf.a
> +
> + $(TEST_GEN_PROGS): $(BPFOBJ)
> +@@ -242,9 +240,10 @@ MAP_TESTS_DIR = $(OUTPUT)/map_tests
> + $(MAP_TESTS_DIR):
> + mkdir -p $@
> + MAP_TESTS_H := $(MAP_TESTS_DIR)/tests.h
> ++MAP_TESTS_FILES := $(wildcard map_tests/*.c)
> + test_maps.c: $(MAP_TESTS_H)
> + $(OUTPUT)/test_maps: CFLAGS += $(TEST_MAPS_CFLAGS)
> +-MAP_TESTS_FILES := $(wildcard map_tests/*.c)
> ++$(OUTPUT)/test_maps: test_maps.c $(MAP_TESTS_H) $(MAP_TESTS_FILES)
> + $(MAP_TESTS_H): $(MAP_TESTS_DIR) $(MAP_TESTS_FILES)
> + $(shell ( cd map_tests/; \
> + echo '/* Generated header, do not edit */'; \
> +@@ -261,6 +260,7 @@ $(MAP_TESTS_H): $(MAP_TESTS_DIR) $(MAP_TESTS_FILES)
> + VERIFIER_TESTS_H := $(OUTPUT)/verifier/tests.h
> + test_verifier.c: $(VERIFIER_TESTS_H)
> + $(OUTPUT)/test_verifier: CFLAGS += $(TEST_VERIFIER_CFLAGS)
> ++$(OUTPUT)/test_verifier: test_verifier.c $(VERIFIER_TESTS_H)
> +
> + VERIFIER_TESTS_DIR = $(OUTPUT)/verifier
> + $(VERIFIER_TESTS_DIR):
> +--
> +2.23.0
> +
> diff --git
> a/meta/recipes-kernel/linux/files/0002-selftests-bpf-structure-test_-progs-maps-verifier-te.patch
>
> b/meta/recipes-kernel/linux/files/0002-selftests-bpf-structure-test_-progs-maps-verifier-te.patch
> new file mode 100644
> index 00..36692088b0
> --- /dev/null
> +++
> b/meta/recipes-kernel/linux/files/0002-selftests-bpf-structure-test_-progs-maps-verifier-te.patch
> @@ -0,0 +1,86 @@
> +From 2fd88b60e6255206d46baa543a637aa1e1cc6186 Mon Sep 17 00:00:00 2001
> +From: Andrii Nakryiko
> +Date: Tue, 16 Jul 2019 12:38:37 -0700
> +Subject: [PATCH 2/2] selftests/bpf: structure test_{progs, maps, verifier}
> + test runners uniformly
> +
> +It's easier to follow the logic if it's structured the same.
> +There is just slight difference between test_progs/test_maps and
> +test_verifier. test_verifier's verifier/*.c files are not really compilable
> +C files (they are more of include headers), so they can't be specified as
> +explicit dependencies of test_verifier.
> +
> +Cc: Alexei Starovoitov
> +Signed-off-by: Andrii Nakryiko
> +Signed-off-by: Alexei Starovoitov
> +---
> + tools/testing/selftests/bpf/Makefile | 24 ++--
> + 1 file changed, 10 insertions(+), 14 deletions(-)
> +
> +diff --git a/tools/testing/selftests/bpf/Makefile
> b/tools/testing/selftests/bpf/Makefile
> +index cd12bf414056..b76c43eb5d4f 100644
> +--- a/tools/testing/selftests/bpf/Makefile
>
[OE-core] [PATCH] libxcrypt: Fix the build with -Os
| In file included from ../git/lib/alg-des.c:66:
| ../git/lib/alg-des.c: In function '_crypt_des_set_key':
| ../git/lib/byteorder.h:24:1: error: inlining failed in call to 'be32_to_cpu':
call is unlikely and code size would grow [-Werror=inline]
| be32_to_cpu (const unsigned char *buf)
| ^~~
| ../git/lib/alg-des.c:81:13: note: called from here
|rawkey1 = be32_to_cpu ([4]);
| ^
Signed-off-by: Adrian Bunk
---
meta/recipes-core/libxcrypt/libxcrypt_4.4.6.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-core/libxcrypt/libxcrypt_4.4.6.bb
b/meta/recipes-core/libxcrypt/libxcrypt_4.4.6.bb
index 893f5e7379..5270e58c2b 100644
--- a/meta/recipes-core/libxcrypt/libxcrypt_4.4.6.bb
+++ b/meta/recipes-core/libxcrypt/libxcrypt_4.4.6.bb
@@ -26,8 +26,8 @@ FILES_${PN} = "${libdir}/libcrypt*.so.* \
S = "${WORKDIR}/git"
BUILD_CPPFLAGS = "-I${STAGING_INCDIR_NATIVE}"
-TARGET_CPPFLAGS = "-I${STAGING_DIR_TARGET}${includedir}
-Wno-error=missing-attributes"
-CPPFLAGS_append_class-nativesdk = " -Wno-error=missing-attributes"
+TARGET_CPPFLAGS = "-I${STAGING_DIR_TARGET}${includedir} -Wno-error"
+CPPFLAGS_append_class-nativesdk = " -Wno-error"
API = "--disable-obsolete-api"
EXTRA_OECONF += "${API}"
--
2.17.1
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 0/5] kernel-yocto: misc build / config changes
On Wed, 2019-08-14 at 11:31 -0400, bruce.ashfi...@gmail.com wrote: > From: Bruce Ashfield > > Hi all, > > This pull request is a collection of smaller fixes that I've been > collecting > while I work through the 5.2/5.3 kernel intro, new libc-headers, etc. > There's > no reason to make them wait while I finish that work, so here they > are in a > single branch. > > There's nothing major here, just a some legwork changes, licensing > update > and a short term workaround for embedded host paths in the kernel > binaries. There appear to be a few issues with the new headers. ppc looks to have particular issues: https://autobuilder.yoctoproject.org/typhoon/#/builders/70/builds/976 eudev: util.lo ../../../eudev-3.2.8/src/shared/sysctl-util.c | ../../../eudev-3.2.8/src/shared/log.c: In function 'create_log_socket': | ../../../eudev-3.2.8/src/shared/log.c:123:43: error: 'SO_SNDTIMEO' undeclared (first use in this function); did you mean 'SO_TXTIME'? | 123 | (void) setsockopt(fd, SOL_SOCKET, SO_SNDTIMEO, , sizeof(tv)); | | ^~~ | | SO_TXTIME | ../../../eudev-3.2.8/src/shared/log.c:123:43: note: each undeclared identifier is reported only once for each function it appears in neard: ../neard-0.16/plugins/p2p.c: In function 'p2p_connect_blocking': ../neard-0.16/plugins/p2p.c:324:33: error: 'SO_RCVTIMEO' undeclared (first use in this function); did you mean 'SO_RCVTIMEO_OLD'? 324 | if (setsockopt(fd, SOL_SOCKET, SO_RCVTIMEO, (char *), | ^~~ | SO_RCVTIMEO_OLD ../neard-0.16/plugins/p2p.c:324:33: note: each undeclared identifier is reported only once for each function it appears in ../neard-0.16/plugins/p2p.c:328:33: error: 'SO_SNDTIMEO' undeclared (first use in this function); did you mean 'SO_TXTIME'? 328 | if (setsockopt(fd, SOL_SOCKET, SO_SNDTIMEO, (char *), | ^~~ | SO_TXTIME ../neard-0.16/plugins/p2p.c: In function 'p2p_connect': ../neard-0.16/plugins/p2p.c:555:33: error: 'SO_RCVTIMEO' undeclared (first use in this function); did you mean 'SO_RCVTIMEO_OLD'? 555 | if (setsockopt(fd, SOL_SOCKET, SO_RCVTIMEO, (char *), | ^~~ | SO_RCVTIMEO_OLD ../neard-0.16/plugins/p2p.c:559:33: error: 'SO_SNDTIMEO' undeclared (first use in this function); did you mean 'SO_TXTIME'? 559 | if (setsockopt(fd, SOL_SOCKET, SO_SNDTIMEO, (char *), | ^~~ | SO_TXTIME Makefile:1973: recipe for target 'plugins/src_neard-p2p.o' failed make[1]: *** [plugins/src_neard-p2p.o] Error 1 and errors from lttng-ust (cc'd Jonathan). qemuarm is erroring due to /dev/fb0 disappearing, which is probably kernel? https://autobuilder.yoctoproject.org/typhoon/#/builders/53/builds/975 https://autobuilder.yoctoproject.org/typhoon/#/builders/38/builds/976 https://autobuilder.yoctoproject.org/typhoon/#/builders/47/builds/986 and we also have an unintended side effect multilib build failure: https://autobuilder.yoctoproject.org/typhoon/#/builders/44/builds/995 which might be due to changed dependencies, I need to check into that one further. Cheers, Richard -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 1/5] kernel-devsrc: tweak for v5.3+
On Wed, 2019-08-14 at 11:31 -0400, bruce.ashfi...@gmail.com wrote: > From: Bruce Ashfield > > The 5.3 kernel has two changes that require tweaks to the minimal > kernel-devsrc package. > > - 4ce97317f [x86/purgatory: Do not use __builtin_memcpy and > __builtin_memset] > > This change removes the need for arch/x86/purgatory/string.c and > instead reuses a copy in arch/x86/boot/compressed/, so we can't > copy > the file anymore. To support older kernels, we make the copy > survive > the non-existence of the file. > This change was merged in 4.19 stable kernel as well. Can this be merged in our stable branches as well please? https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.19.y=e0d262a57fc741a9b362e458c714e37a77ddb62d Thanks, Anuj -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 1/2] uboot-sign: Refactor do_deploy prefunc to do_deploy_prepend
> That commit message isn't correct.
>
> It removes cleandirs for the prefunc at the start of the prefunc and
> cleandirs for the main function at the start of that main function.
Oh ok, so the prefuncs/postfuncs can have their own [cleandirs], that's
interesting.
How about the following (trying to find a good way to explain it):
-
When inherited by the u-boot recipe (UBOOT_PN), uboot-sign.bbclass adds
a concat_dtb step, which places additional files into ${DEPLOYDIR}
before do_deploy.
The use of prefuncs for this prevents us from adding
do_deploy[cleandirs] = "${DEPLOYDIR}"
because that would remove the files produced by the prefunc.
(Each of prefuncs/task/postfuncs functions has their own cleandirs, and
each function's cleandirs are removed at the start of that function.)
Thus, it seems good to make concat_dtb a part of do_deploy, such that it
runs after removal of do_deploy's cleandirs. As before, care is taken to
not interfere with the kernel's do_deploy definition, since concat_dtb
was only needed for u-boot.
-
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] ltp: move from python 2.x to python 3.x
On Thu, 29 Aug 2019 at 10:09, Yi Zhao wrote: > > I had sent a similar patch to upstream and it had been merged. You could > backport it. > Thanks, I think we can simply remove my patch when ltp is updated. Alex -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] ltp: move from python 2.x to python 3.x
Hi Alexander, On 8/29/19 4:50 AM, Alexander Kanavin wrote: Signed-off-by: Alexander Kanavin --- ...thon3-everywhere-to-run-python-scrip.patch | 161 ++ meta/recipes-extended/ltp/ltp_20190517.bb | 3 +- 2 files changed, 163 insertions(+), 1 deletion(-) create mode 100644 meta/recipes-extended/ltp/ltp/0001-testcases-use-python3-everywhere-to-run-python-scrip.patch diff --git a/meta/recipes-extended/ltp/ltp/0001-testcases-use-python3-everywhere-to-run-python-scrip.patch b/meta/recipes-extended/ltp/ltp/0001-testcases-use-python3-everywhere-to-run-python-scrip.patch new file mode 100644 index 000..f4f87f38ab7 --- /dev/null +++ b/meta/recipes-extended/ltp/ltp/0001-testcases-use-python3-everywhere-to-run-python-scrip.patch @@ -0,0 +1,161 @@ +From 0463d793566772a606255957915f99d166d5740c Mon Sep 17 00:00:00 2001 +From: Alexander Kanavin +Date: Wed, 28 Aug 2019 18:30:23 +0200 +Subject: [PATCH] testcases: use python3 everywhere to run python scripts + +The scripts themselves have #!/usr/bin/python3 in them, +so I trust they are already py3-compatible. + +Upstream-Status: Pending I had sent a similar patch to upstream and it had been merged. You could backport it. https://github.com/linux-test-project/ltp/commit/fc606bf2a9fdd356c593cc7b37217cae18100ffc //Yi +Signed-off-by: Alexander Kanavin +--- + testcases/kernel/power_management/runpwtests05.sh | 2 +- + .../power_management/runpwtests_exclusive01.sh | 2 +- + .../power_management/runpwtests_exclusive02.sh | 2 +- + .../power_management/runpwtests_exclusive03.sh | 2 +- + .../power_management/runpwtests_exclusive04.sh | 2 +- + .../power_management/runpwtests_exclusive05.sh | 2 +- + testcases/network/nfsv4/acl/runtest| 14 +++--- + testcases/realtime/func/pi-tests/run_auto.sh | 6 +++--- + 8 files changed, 16 insertions(+), 16 deletions(-) + +diff --git a/testcases/kernel/power_management/runpwtests05.sh b/testcases/kernel/power_management/runpwtests05.sh +index 8a7d0f6e0..43e234d01 100755 +--- a/testcases/kernel/power_management/runpwtests05.sh b/testcases/kernel/power_management/runpwtests05.sh +@@ -35,7 +35,7 @@ else + max_sched_smt=1 + fi + +-tst_test_cmds python ++tst_test_cmds python3 + + if ! grep sched_debug -qw /proc/cmdline ; then + tst_brkm TCONF "Kernel cmdline parameter 'sched_debug' needed," \ +diff --git a/testcases/kernel/power_management/runpwtests_exclusive01.sh b/testcases/kernel/power_management/runpwtests_exclusive01.sh +index ec78319e2..9fefcbf6e 100755 +--- a/testcases/kernel/power_management/runpwtests_exclusive01.sh b/testcases/kernel/power_management/runpwtests_exclusive01.sh +@@ -35,7 +35,7 @@ else + max_sched_smt=1 + fi + +-tst_test_cmds python ++tst_test_cmds python3 + + hyper_threaded=$(is_hyper_threaded) + multi_socket=$(is_multi_socket) +diff --git a/testcases/kernel/power_management/runpwtests_exclusive02.sh b/testcases/kernel/power_management/runpwtests_exclusive02.sh +index e107fce35..2cd0ecb05 100755 +--- a/testcases/kernel/power_management/runpwtests_exclusive02.sh b/testcases/kernel/power_management/runpwtests_exclusive02.sh +@@ -33,7 +33,7 @@ else + max_sched_smt=1 + fi + +-tst_test_cmds python ++tst_test_cmds python3 + + hyper_threaded=$(is_hyper_threaded) + multi_socket=$(is_multi_socket) +diff --git a/testcases/kernel/power_management/runpwtests_exclusive03.sh b/testcases/kernel/power_management/runpwtests_exclusive03.sh +index 490344bb3..ab3a5d11d 100755 +--- a/testcases/kernel/power_management/runpwtests_exclusive03.sh b/testcases/kernel/power_management/runpwtests_exclusive03.sh +@@ -35,7 +35,7 @@ else + max_sched_smt=1 + fi + +-tst_test_cmds python ++tst_test_cmds python3 + + hyper_threaded=$(is_hyper_threaded) + multi_socket=$(is_multi_socket) +diff --git a/testcases/kernel/power_management/runpwtests_exclusive04.sh b/testcases/kernel/power_management/runpwtests_exclusive04.sh +index 978ca02ae..438ef603f 100755 +--- a/testcases/kernel/power_management/runpwtests_exclusive04.sh b/testcases/kernel/power_management/runpwtests_exclusive04.sh +@@ -27,7 +27,7 @@ export TST_TOTAL=2 + # Checking test environment + check_kervel_arch + +-tst_test_cmds python ++tst_test_cmds python3 + + hyper_threaded=$(is_hyper_threaded) + multi_socket=$(is_multi_socket) +diff --git a/testcases/kernel/power_management/runpwtests_exclusive05.sh b/testcases/kernel/power_management/runpwtests_exclusive05.sh +index a0dad5834..3a9afdbf2 100755 +--- a/testcases/kernel/power_management/runpwtests_exclusive05.sh b/testcases/kernel/power_management/runpwtests_exclusive05.sh +@@ -35,7 +35,7 @@ else + max_sched_smt=1 + fi + +-tst_test_cmds python ++tst_test_cmds python3 + + hyper_threaded=$(is_hyper_threaded) + multi_socket=$(is_multi_socket) +diff --git a/testcases/network/nfsv4/acl/runtest b/testcases/network/nfsv4/acl/runtest +index d2e1b4c49..a859e85bc 100755 +---
Re: [OE-core] [PATCH] common-licenses: update BSD-2-CLAUSE license text
On Wed, 2019-08-28 at 11:13 -0700, Andre McCurdy wrote: > On Wed, Aug 28, 2019 at 3:05 AM Christophe PRIOUZEAU > wrote: > > Using the generic BSD-2-CLAUSE license as specified on > > https://opensource.org/licenses/BSD-2-Clause > > Fixing these kind of issues has been discussed before. I think the > consensus was that a wider ranging cleanup is needed. The thread > starts here: > > > http://lists.openembedded.org/pipermail/openembedded-core/2018-June/270475.html I agree there is probably more cleanup needed but this patch seems like a step in the right direction... Cheers, Richard -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] bind: fix build with python3 PACKAGECONFIG enabled
ping
On 08/23/2019 04:56 PM, Chen Qi wrote:
If the PACKAGECONFIG item, python3, is enabled, we get the following
QA issue when multilib is enabled.
ERROR: bind-9.11.5-P4-r0 do_package: QA Issue: bind: Files/directories were
installed but not shipped in any package:
/usr/lib
/usr/lib/python3.7
/usr/lib/python3.7/site-packages
/usr/lib/python3.7/site-packages/isc-2.0-py3.7.egg-info
/usr/lib/python3.7/site-packages/isc
/usr/lib/python3.7/site-packages/isc/policy.py
[snip]
The thing is, when --with-python is specified with a path instead of 'yes',
the --with-python-install-dir is in fact ignored.
Fix this issue by specifying the correct arguments.
Signed-off-by: Chen Qi
---
meta/recipes-connectivity/bind/bind_9.11.5-P4.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-connectivity/bind/bind_9.11.5-P4.bb
b/meta/recipes-connectivity/bind/bind_9.11.5-P4.bb
index 93c406f778..69b1174073 100644
--- a/meta/recipes-connectivity/bind/bind_9.11.5-P4.bb
+++ b/meta/recipes-connectivity/bind/bind_9.11.5-P4.bb
@@ -39,7 +39,7 @@ PACKAGECONFIG[httpstats] =
"--with-libxml2=${STAGING_DIR_HOST}${prefix},--withou
PACKAGECONFIG[readline] = "--with-readline=-lreadline,,readline"
PACKAGECONFIG[libedit] = "--with-readline=-ledit,,libedit"
PACKAGECONFIG[urandom] =
"--with-randomdev=/dev/urandom,--with-randomdev=/dev/random,,"
-PACKAGECONFIG[python3] = "--with-python=${PYTHON}
--with-python-install-dir=${D}/${PYTHON_SITEPACKAGES_DIR} , --without-python,
python3-ply-native,"
+PACKAGECONFIG[python3] = "--with-python=yes
--with-python-install-dir=${PYTHON_SITEPACKAGES_DIR} , --without-python,
python3-ply-native,"
ENABLE_IPV6 = "--enable-ipv6=${@bb.utils.contains('DISTRO_FEATURES', 'ipv6', 'yes', 'no', d)}"
EXTRA_OECONF = " ${ENABLE_IPV6} --with-libtool --enable-threads \
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 4/8] kernel-devsrc: remove python2 dependency
On Wed, Aug 28, 2019 at 06:06:04PM -0400, Bruce Ashfield wrote: > On Wed, Aug 28, 2019 at 5:58 PM Adrian Bunk wrote: > > > > On Wed, Aug 28, 2019 at 04:11:43PM -0400, Bruce Ashfield wrote: > > >... > > > There's zero risk to these, and no reason to sit on them. > > > > What range of LTS kernels is covered by the "zero risk"? > > It has nothing to do with LTS kernels. virtual/kernel is special since real products have this provided by a BSP layer instead of using the kernels for the reference platforms that ship with Yocto. How do your changes interact with a BSP layer that provides the upstream maintained LTS kernel 4.4? > Cheers, > > Bruce cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
