Re: [OE-core] [PATCH] busybox: 1.29.3 -> 1.30.1
Hello Richard
I have set-up new build (master-next):
Build Configuration:
BB_VERSION = "1.40.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "qemuarm"
DISTRO = "poky"
DISTRO_VERSION = "2.6+snapshot-20190215"
TUNE_FEATURES= "arm armv5 thumb dsp"
TARGET_FPU = "soft"
meta
meta-poky
meta-yocto-bsp =
"master-next:227617e923ce25ee266df51828ac4cce4524d95a"
Building tooks lot of hours from scratch. I have expected the same
error, but build was successful.
DEBUG: Python function do_rootfs finished
Is it possible to provide some more detailed error log, to identify,
what's really going there.
Thanks,
Andrej
On 2/15/19 12:25 PM, Richard Purdie wrote:
> On Fri, 2019-02-15 at 09:22 +0100, Andrej Valek wrote:
>> - update to last stable version 1.30.1
>> - remove and refresh already merged patches
>>
>> Signed-off-by: Andrej Valek
>> ---
>> ...inittab_1.29.3.bb => busybox-inittab_1.30.1.bb} | 0
>> ...te-check-CONFIG_DESKTOP-before-using-od-t.patch | 83
>> --
>> ...-testsuite-check-uudecode-before-using-it.patch | 6 +-
>> .../{busybox_1.29.3.bb => busybox_1.30.1.bb} | 5 +-
>> 4 files changed, 5 insertions(+), 89 deletions(-)
>> rename meta/recipes-core/busybox/{busybox-inittab_1.29.3.bb =>
>> busybox-inittab_1.30.1.bb} (100%)
>> delete mode 100644 meta/recipes-core/busybox/busybox/0001-testsuite-
>> check-CONFIG_DESKTOP-before-using-od-t.patch
>> rename meta/recipes-core/busybox/{busybox_1.29.3.bb =>
>> busybox_1.30.1.bb} (89%)
>
> There seems to be something not quite right with this:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/76/builds/284
> https://autobuilder.yoctoproject.org/typhoon/#/builders/50/builds/283
>
> Cheers,
>
> Richard
>
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH v3] Fix cp's target path for ext* filesystems
Does anybody have other suggestions on this one?
> Python subprocess' shell=True defaults to /bin/sh[1][2], which
> often refers to a POSIX-compliant shell. As the -e flag is
> not defined in the POSIX standard[3], some shells may
> interpret "-e" as the first argument to the echo command,
> causing the rest of the command line to fail.
>
> In this particular case, "echo -e 'cd {}'" is interpreted
> as "-e cd {}", which causes the first line of the command
> to fail, and causing cp to always place the source file
> in the filesystem's root.
>
> Replacing "echo -e" for a printf command makes this
> more portable.
>
> This issue only affects "wic cp" for ext* filesystems.
>
> [1] https://docs.python.org/2/library/subprocess.html
> [2] https://docs.python.org/3/library/subprocess.html
> [3] http://pubs.opengroup.org/onlinepubs/9699919799
>
> Signed-off-by: Leonardo Augusto
> ---
> scripts/lib/wic/engine.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/lib/wic/engine.py b/scripts/lib/wic/engine.py
> index 4662c665c0..97f5e848cc 100644
> --- a/scripts/lib/wic/engine.py
> +++ b/scripts/lib/wic/engine.py
> @@ -331,7 +331,7 @@ class Disk:
> def copy(self, src, pnum, path):
> """Copy partition image into wic image."""
> if self.partitions[pnum].fstype.startswith('ext'):
> -cmd = "echo -e 'cd {}\nwrite {} {}' | {} -w {}".\
> +cmd = "printf 'cd {}\nwrite {} {}' | {} -w {}".\
>format(path, src, os.path.basename(src),
> self.debugfs, self._get_part_image(pnum))
> else: # fat
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [OE-Core][PATCH] kernel-fitimage.bbclass: Fix the dependency issue while generating fitimage_initramfs
When building fitimage_initramfs, the correct depedency is to build
after do_bundle_initramfs. We can run into the following dependency
issue
DEBUG: Python function extend_recipe_sysroot finished
DEBUG: Executing shell function do_assemble_fitimage_initramfs
aarch64-xilinx-linux-objcopy: 'vmlinux': No such file
This happens because initramfs renames vmlinux to vmlinux.bak while
generating vmlinux.initramfs, there is a chance that fitimage_initramfs
can also start during this process and create the above issue.
This patch resolve the dependency issue by running fitimage_initramfs
task after do_bundle_initramfs
Signed-off-by: Varalaxmi Bingi
Signed-off-by: Manjukumar Matha
---
meta/classes/kernel-fitimage.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/kernel-fitimage.bbclass
b/meta/classes/kernel-fitimage.bbclass
index 718162a..8ebd3dd 100644
--- a/meta/classes/kernel-fitimage.bbclass
+++ b/meta/classes/kernel-fitimage.bbclass
@@ -488,7 +488,7 @@ do_assemble_fitimage_initramfs() {
fi
}
-addtask assemble_fitimage_initramfs before do_deploy after do_install
+addtask assemble_fitimage_initramfs before do_deploy after do_bundle_initramfs
kernel_do_deploy[vardepsexclude] = "DATETIME"
--
2.7.4
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [OE-Core][PATCH] bmap-tools: update from 3.4 to 3.5
On Thu, 2019-02-14 at 21:09 +, Alex Kiernan wrote:
> bmap-tools 3.5 was released August 2018 but has no release tarball,
> so
> switch to using the git fetcher. Also pull in the fix for
> StopIteration
> being transformed into RuntimeError for Python 3.7.
>
> Signed-off-by: Alex Kiernan
Unfortunately this triggers a selftest failure:
https://autobuilder.yoctoproject.org/typhoon/#/builders/56/builds/236
(ignore the virtgl piece, that is something else)
oe-selftest -r wic.Wic2.test_bmap_short
and
oe-selftest -r wic.Wic2.test_bmap_long
should reproduce. Might be as simple as a missing RDEPENDS.
Cheers,
Richard
>
> .../bmap-tools/{bmap-tools_3.4.bb => bmap-tools_3.5.bb} | 9
> +
> 1 file changed, 5 insertions(+), 4 deletions(-)
> rename meta/recipes-support/bmap-tools/{bmap-tools_3.4.bb => bmap-
> tools_3.5.bb} (74%)
>
> diff --git a/meta/recipes-support/bmap-tools/bmap-tools_3.4.bb
> b/meta/recipes-support/bmap-tools/bmap-tools_3.5.bb
> similarity index 74%
> rename from meta/recipes-support/bmap-tools/bmap-tools_3.4.bb
> rename to meta/recipes-support/bmap-tools/bmap-tools_3.5.bb
> index 2aae9a3fe0d8..25d66df623a0 100644
> --- a/meta/recipes-support/bmap-tools/bmap-tools_3.4.bb
> +++ b/meta/recipes-support/bmap-tools/bmap-tools_3.5.bb
> @@ -9,12 +9,13 @@ SECTION = "console/utils"
> LICENSE = "GPLv2"
> LIC_FILES_CHKSUM =
> "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
>
> -SRC_URI = "
> https://github.com/intel/${BPN}/releases/download/v${PV}/${BP}.tgz;
> +SRC_URI = "git://github.com/intel/${BPN}"
>
> -SRC_URI[md5sum] = "883420183611aa137cbaf68a91ef0d7e"
> -SRC_URI[sha256sum] =
> "0064891270c180c190f41925b0f6fb9cecac3056f1168d2592dbe90e5f226c0a"
> +SRCREV = "db7087b883bf52cbff063ad17a41cc1cbb85104d"
> +S = "${WORKDIR}/git"
> +PV .= "+git${SRCPV}"
>
> -UPSTREAM_CHECK_URI = "https://github.com/intel/${BPN}/releases;
> +UPSTREAM_CHECK_GITTAGREGEX = "v(?P.*)"
>
> RDEPENDS_${PN} = "python3-core python3-compression python3-mmap
> python3-setuptools python3-fcntl"
>
> --
> 2.7.4
>
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH v3 3/3] image_types.bbclass: Set memory usage limit and CPU threads for xz
On Fri, Feb 15, 2019 at 5:44 AM Otavio Salvador wrote: > > On Tue, Feb 12, 2019 at 3:48 AM Khem Raj wrote: > > > > when building with opkg backend and huge packages e.g. chromium/llvm all > > going in parallel, memory pressure causes xz to catapult with > > > > do_package_write_ipk: Failed to create package, opkg-build failed with: xz: > > (stdin): Cannot allocate memory > > > > since there are many tasks going on in parallel, xz adds to memory pressure > > and it wants it all, put an upper limit for memory xz can use > > > > We add a variable XZ_MAXRAM with 30% of RAM limit and can be customized > > if builders have more memory one can set it like > > The commit log refers to the wrong variable name, it seems. > I think thats a good point. but we should submit right names for documentation > > -- > Otavio Salvador O.S. Systems > http://www.ossystems.com.brhttp://code.ossystems.com.br > Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 1/3] busybox: Remove PN from rdeps of PN-dev
On Fri, Feb 15, 2019 at 8:04 AM Richard Purdie wrote: > > On Fri, 2019-02-15 at 07:01 -0800, Khem Raj wrote: > > Richard/Ross > > > > Are you able to reproduce the problem and have > > alternative solution? > > Your reproduction steps needed "use ipk", then yes, I could. I've sent > out a patch which addresses the problem. Thanks yes ipk was implied with oe-core+bitbake :) I will test https://patchwork.openembedded.org/patch/158751/ and see if my SDK is good with out busybox hack > > Cheers, > > Richard > > > -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 1/3] busybox: Remove PN from rdeps of PN-dev
On Fri, 2019-02-15 at 07:01 -0800, Khem Raj wrote: > Richard/Ross > > Are you able to reproduce the problem and have > alternative solution? Your reproduction steps needed "use ipk", then yes, I could. I've sent out a patch which addresses the problem. Cheers, Richard -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 5/5] lib/oe, oeqa/selftest: Fix DeprecationWarning: invalid escape sequence
Fix another load of regex escape sequence warnings for newer
python versions.
Signed-off-by: Richard Purdie
---
meta/lib/oe/recipeutils.py | 8
meta/lib/oeqa/selftest/cases/bbtests.py | 6 +++---
meta/lib/oeqa/selftest/cases/devtool.py | 2 +-
meta/lib/oeqa/selftest/cases/prservice.py | 4 ++--
meta/lib/oeqa/selftest/cases/sstatetests.py | 18 +-
5 files changed, 19 insertions(+), 19 deletions(-)
diff --git a/meta/lib/oe/recipeutils.py b/meta/lib/oe/recipeutils.py
index 92c0f65257f..8f70d2eb212 100644
--- a/meta/lib/oe/recipeutils.py
+++ b/meta/lib/oe/recipeutils.py
@@ -24,7 +24,7 @@ from bb.utils import vercmp_string
# Help us to find places to insert values
recipe_progression = ['SUMMARY', 'DESCRIPTION', 'HOMEPAGE', 'BUGTRACKER',
'SECTION', 'LICENSE', 'LICENSE_FLAGS', 'LIC_FILES_CHKSUM', 'PROVIDES',
'DEPENDS', 'PR', 'PV', 'SRCREV', 'SRCPV', 'SRC_URI', 'S', 'do_fetch()',
'do_unpack()', 'do_patch()', 'EXTRA_OECONF', 'EXTRA_OECMAKE', 'EXTRA_OESCONS',
'do_configure()', 'EXTRA_OEMAKE', 'do_compile()', 'do_install()',
'do_populate_sysroot()', 'INITSCRIPT', 'USERADD', 'GROUPADD', 'PACKAGES',
'FILES', 'RDEPENDS', 'RRECOMMENDS', 'RSUGGESTS', 'RPROVIDES', 'RREPLACES',
'RCONFLICTS', 'ALLOW_EMPTY', 'populate_packages()', 'do_package()',
'do_deploy()']
# Variables that sometimes are a bit long but shouldn't be wrapped
-nowrap_vars = ['SUMMARY', 'HOMEPAGE', 'BUGTRACKER',
'SRC_URI\[(.+\.)?md5sum\]', 'SRC_URI\[(.+\.)?sha256sum\]']
+nowrap_vars = ['SUMMARY', 'HOMEPAGE', 'BUGTRACKER',
r'SRC_URI\[(.+\.)?md5sum\]', r'SRC_URI\[(.+\.)?sha256sum\]']
list_vars = ['SRC_URI', 'LIC_FILES_CHKSUM']
meta_vars = ['SUMMARY', 'DESCRIPTION', 'HOMEPAGE', 'BUGTRACKER', 'SECTION']
@@ -161,7 +161,7 @@ def patch_recipe_lines(fromlines, values,
trailing_newline=True):
key = item[:-2]
else:
key = item
-restr = '%s(_[a-zA-Z0-9-_$(){}]+|\[[^\]]*\])?' % key
+restr = r'%s(_[a-zA-Z0-9-_$(){}]+|\[[^\]]*\])?' % key
if item.endswith('()'):
recipe_progression_restrs.append(restr + '()')
else:
@@ -925,7 +925,7 @@ def get_recipe_pv_without_srcpv(pv, uri_type):
sfx = ''
if uri_type == 'git':
-git_regex =
re.compile("(?Pv?)(?P[^\+]*)((?P\+(git)?r?(AUTOINC\+))(?P.*))?")
+git_regex =
re.compile(r"(?Pv?)(?P[^\+]*)((?P\+(git)?r?(AUTOINC\+))(?P.*))?")
m = git_regex.match(pv)
if m:
@@ -933,7 +933,7 @@ def get_recipe_pv_without_srcpv(pv, uri_type):
pfx = m.group('pfx')
sfx = m.group('sfx')
else:
-regex = re.compile("(?P(v|r)?)(?P.*)")
+regex = re.compile(r"(?P(v|r)?)(?P.*)")
m = regex.match(pv)
if m:
pv = m.group('ver')
diff --git a/meta/lib/oeqa/selftest/cases/bbtests.py
b/meta/lib/oeqa/selftest/cases/bbtests.py
index 005fdd09640..c503e4eedda 100644
--- a/meta/lib/oeqa/selftest/cases/bbtests.py
+++ b/meta/lib/oeqa/selftest/cases/bbtests.py
@@ -40,8 +40,8 @@ class BitbakeTests(OESelftestTestCase):
def test_event_handler(self):
self.write_config("INHERIT += \"test_events\"")
result = bitbake('m4-native')
-find_build_started = re.search("NOTE: Test for
bb\.event\.BuildStarted(\n.*)*NOTE: Executing RunQueue Tasks", result.output)
-find_build_completed = re.search("Tasks Summary:.*(\n.*)*NOTE: Test
for bb\.event\.BuildCompleted", result.output)
+find_build_started = re.search(r"NOTE: Test for
bb\.event\.BuildStarted(\n.*)*NOTE: Executing RunQueue Tasks", result.output)
+find_build_completed = re.search(r"Tasks Summary:.*(\n.*)*NOTE: Test
for bb\.event\.BuildCompleted", result.output)
self.assertTrue(find_build_started, msg = "Match failed in:\n%s" %
result.output)
self.assertTrue(find_build_completed, msg = "Match failed in:\n%s" %
result.output)
self.assertFalse('Test for bb.event.InvalidEvent' in result.output,
msg = "\"Test for bb.event.InvalidEvent\" message found during bitbake process.
bitbake output: %s" % result.output)
@@ -196,7 +196,7 @@ SSTATE_DIR = \"${TOPDIR}/download-selftest\"
@OETestID(1031)
def test_version(self):
result = runCmd('bitbake -s | grep wget')
-find = re.search("wget *:([0-9a-zA-Z\.\-]+)", result.output)
+find = re.search(r"wget *:([0-9a-zA-Z\.\-]+)", result.output)
self.assertTrue(find, "No version returned for searched recipe.
bitbake output: %s" % result.output)
@OETestID(1032)
diff --git a/meta/lib/oeqa/selftest/cases/devtool.py
b/meta/lib/oeqa/selftest/cases/devtool.py
index 9eb9badf84f..58f3e58461a 100644
--- a/meta/lib/oeqa/selftest/cases/devtool.py
+++ b/meta/lib/oeqa/selftest/cases/devtool.py
@@ -1291,7 +1291,7 @@ class DevtoolExtractTests(DevtoolBase):
installdir = bb_vars['D']
fakerootenv = bb_vars['FAKEROOTENV']
fakerootcmd = bb_vars['FAKEROOTCMD']
-
[OE-core] [PATCH 3/5] lttng-ust: Upgrade 2.10.2 -> 2.10.3
Signed-off-by: Richard Purdie
---
.../lttng/{lttng-ust_2.10.2.bb => lttng-ust_2.10.3.bb}| 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-kernel/lttng/{lttng-ust_2.10.2.bb => lttng-ust_2.10.3.bb}
(90%)
diff --git a/meta/recipes-kernel/lttng/lttng-ust_2.10.2.bb
b/meta/recipes-kernel/lttng/lttng-ust_2.10.3.bb
similarity index 90%
rename from meta/recipes-kernel/lttng/lttng-ust_2.10.2.bb
rename to meta/recipes-kernel/lttng/lttng-ust_2.10.3.bb
index 3e5f37d8865..b5c43200d62 100644
--- a/meta/recipes-kernel/lttng/lttng-ust_2.10.2.bb
+++ b/meta/recipes-kernel/lttng/lttng-ust_2.10.3.bb
@@ -23,8 +23,8 @@ PE = "2"
SRC_URI = "https://lttng.org/files/lttng-ust/lttng-ust-${PV}.tar.bz2 \
file://lttng-ust-doc-examples-disable.patch \
"
-SRC_URI[md5sum] = "a95333f76e2986113154b8193f5cfca3"
-SRC_URI[sha256sum] =
"c4ca22b904eb08817b313a73d499e1b217ffee1f862156d0d52865317486c045"
+SRC_URI[md5sum] = "ffcfa8c1ba9a52f002d240e936e9afa2"
+SRC_URI[sha256sum] =
"9e8420f90d5f963f7aa32bc6d44adc1e491136f687c69ffb7a3075d33b40852b"
CVE_PRODUCT = "ust"
--
2.20.1
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 4/5] lib/buildstats: Improve error message
Just stating the recipe counts are different isn't helpful, showing
the differences makes it much easier to understand what changed.
Signed-off-by: Richard Purdie
---
scripts/lib/buildstats.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/lib/buildstats.py b/scripts/lib/buildstats.py
index d9aadf3cb80..f7db3eaf92e 100644
--- a/scripts/lib/buildstats.py
+++ b/scripts/lib/buildstats.py
@@ -263,7 +263,7 @@ class BuildStats(dict):
"""Aggregate other buildstats into this"""
if set(self.keys()) != set(buildstats.keys()):
raise ValueError("Refusing to aggregate buildstats, set of "
- "recipes is different")
+ "recipes is different: %s" % (set(self.keys()) ^
set(buildstats.keys(
for pkg, data in buildstats.items():
self[pkg].aggregate(data)
--
2.20.1
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/5] target-sdk-provides-dummy: Extend to -dev and -src packages
This avoids errors when running populate_sdk under opkg: * Problem 1/1: * - package busybox-dev-1.30.1-r0.core2-64 requires busybox = 1.30.1-r0, but none of the providers can be installed * * Solution 1: * - allow deinstallation of target-sdk-provides-dummy-1.0-r0.sdk-provides-dummy-target * Solution 2: * - do not ask to install a package providing busybox-dev Signed-off-by: Richard Purdie --- meta/recipes-core/meta/target-sdk-provides-dummy.bb | 10 ++ 1 file changed, 10 insertions(+) diff --git a/meta/recipes-core/meta/target-sdk-provides-dummy.bb b/meta/recipes-core/meta/target-sdk-provides-dummy.bb index 26716ace87b..60499f7b66a 100644 --- a/meta/recipes-core/meta/target-sdk-provides-dummy.bb +++ b/meta/recipes-core/meta/target-sdk-provides-dummy.bb @@ -2,9 +2,17 @@ DUMMYARCH = "sdk-provides-dummy-target" DUMMYPROVIDES = "\ busybox \ +busybox-dev \ +busybox-src \ coreutils \ +coreutils-dev \ +coreutils-src \ bash \ +bash-dev \ +bash-src \ perl \ +perl-dev \ +perl-src \ perl-module-re \ perl-module-strict \ perl-module-vars \ @@ -36,6 +44,8 @@ DUMMYPROVIDES = "\ /usr/bin/env \ /usr/bin/perl \ pkgconfig \ +pkgconfig-dev \ +pkgconfig-src \ " require dummy-sdk-package.inc -- 2.20.1 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 2/5] lttng-tools: Upgrade 2.10.5 -> 2.10.6
Signed-off-by: Richard Purdie
---
.../lttng/{lttng-tools_2.10.5.bb => lttng-tools_2.10.6.bb}| 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-kernel/lttng/{lttng-tools_2.10.5.bb =>
lttng-tools_2.10.6.bb} (97%)
diff --git a/meta/recipes-kernel/lttng/lttng-tools_2.10.5.bb
b/meta/recipes-kernel/lttng/lttng-tools_2.10.6.bb
similarity index 97%
rename from meta/recipes-kernel/lttng/lttng-tools_2.10.5.bb
rename to meta/recipes-kernel/lttng/lttng-tools_2.10.6.bb
index 85ed3c691ba..13bab9068eb 100644
--- a/meta/recipes-kernel/lttng/lttng-tools_2.10.5.bb
+++ b/meta/recipes-kernel/lttng/lttng-tools_2.10.6.bb
@@ -34,8 +34,8 @@ SRC_URI =
"https://lttng.org/files/lttng-tools/lttng-tools-${PV}.tar.bz2 \
file://lttng-sessiond.service \
"
-SRC_URI[md5sum] = "50e07676d5eb5d6cf4ece804863a6f74"
-SRC_URI[sha256sum] =
"a4868078ef961e83dc236c4f24fd848161bfa755344b064dece62c4c81a07411"
+SRC_URI[md5sum] = "e88c521b5da6bb48a8187af66ecc"
+SRC_URI[sha256sum] =
"f05df52bbebf8ce88d1b29e9e98cfc957d2ed738a345118018237ebdb581537c"
inherit autotools ptest pkgconfig useradd python3-dir manpages systemd
--
2.20.1
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [OE-Core][PATCH] perf: Package libperf-jvmti.so as part of ${PN}
On Tue, Jan 15, 2019 at 6:55 AM Alex Kiernan wrote:
>
> perf's jvmti support builds libperf-jvmti.so that needs to be packaged
> as part of the main package, not a developer package. Given there's no
> files in the developer package, override FILES_SOLIBSDEV so it's not
> gobbled by FILES_${PN}-dev, and then add just that file to FILES_${PN}
> so that if in the future there other files which would be added to the
> dev package we'll fail then.
>
> Signed-off-by: Alex Kiernan
> ---
ping?
--
Alex Kiernan
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] mesa: upgrade 18.1.9 -> 18.3.3
On Fri, 15 Feb 2019 at 16:16, Otavio Salvador wrote: > I don't see urgency in to do the convertion so if there is more people > which wishes to keep autotools for this release, we can skip it for > 19.0.1 upgrade. The idea was to switch as many recipes as possible that are on the dependency path to qemu-native to meson, to improve build times. With the upcoming virgl patchset, mesa-native is in that set. I'll still provide the patch, as soon as mesa is updated. At least it could get a run on the AB to see where the known issues are. Alex -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] mesa: upgrade 18.1.9 -> 18.3.3
On Fri, Feb 15, 2019 at 12:36 PM Böszörményi Zoltán via Openembedded-core wrote: > > 2019. 02. 15. 14:26 keltezéssel, Alexander Kanavin írta: > > On Fri, 15 Feb 2019 at 14:21, Fabio Berton > > wrote: > >> In my opinion, there is no relation with an update and change build > >> system, once we can use mesa 18.3.3 without meson. > > > > Please see: > > https://www.phoronix.com/scan.php?page=news_item=Mesa-19.0-Deprecates-Autotools > > > > We might as well switch to meson now. The patches are ready and > > (mostly) working. > > I have read the mesa-dev list constantly regarding this change. > > The deprecation process was painful and issues in the meson > build system still turn up occasionally. > > 19.0 will still have a configure option to opt-in for autotools. > In this upcoming release they have worked out all known issues > for meson but I would in no way want to use meson for older main > releases because these changes are not backported offically. > > So, either keep autotools for 8.3.3 or wait for 9.0 and switch to meson. If the switch is made in another commit, we can easily revert it in case it causes issues. I don't see urgency in to do the convertion so if there is more people which wishes to keep autotools for this release, we can skip it for 19.0.1 upgrade. -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 1/3] busybox: Remove PN from rdeps of PN-dev
Richard/Ross
Are you able to reproduce the problem and have
alternative solution?
On Tue, Feb 12, 2019 at 11:04 AM Khem Raj wrote:
>
> On Tue, Feb 12, 2019 at 7:59 AM Burton, Ross wrote:
> >
> > Would a neater solution be to PACKAGES_remove = ${PN}-dev?
> >
>
> That was first thing I tried too. It does not fix the problem
>
> > Ross
> >
> > On Tue, 12 Feb 2019 at 05:48, Khem Raj wrote:
> > >
> > > PN-dev is empty and causes dependency loops during SDK build
> > >
> > > Signed-off-by: Khem Raj
> > > ---
> > > meta/recipes-core/busybox/busybox.inc | 1 +
> > > 1 file changed, 1 insertion(+)
> > >
> > > diff --git a/meta/recipes-core/busybox/busybox.inc
> > > b/meta/recipes-core/busybox/busybox.inc
> > > index 24c15e4aee..2444afabd5 100644
> > > --- a/meta/recipes-core/busybox/busybox.inc
> > > +++ b/meta/recipes-core/busybox/busybox.inc
> > > @@ -21,6 +21,7 @@ export EXTRA_LDFLAGS = "${LDFLAGS}"
> > > EXTRA_OEMAKE = "CC='${CC}' LD='${CCLD}' V=1 ARCH=${TARGET_ARCH}
> > > CROSS_COMPILE=${TARGET_PREFIX} SKIP_STRIP=y HOSTCC='${BUILD_CC}'
> > > HOSTCPP='${BUILD_CPP}'"
> > >
> > > PACKAGES =+ "${PN}-httpd ${PN}-udhcpd ${PN}-udhcpc ${PN}-syslog
> > > ${PN}-mdev ${PN}-hwclock"
> > > +RDEPENDS_${PN}-dev = ""
> > >
> > > FILES_${PN}-httpd = "${sysconfdir}/init.d/busybox-httpd /srv/www"
> > > FILES_${PN}-syslog = "${sysconfdir}/init.d/syslog*
> > > ${sysconfdir}/syslog-startup.conf* ${sysconfdir}/syslog.conf*
> > > ${systemd_unitdir}/system/syslog.service
> > > ${sysconfdir}/default/busybox-syslog"
> > > --
> > > 2.20.1
> > >
> > > --
> > > ___
> > > Openembedded-core mailing list
> > > Openembedded-core@lists.openembedded.org
> > > http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [OE-Core][PATCH] bmap-tools: update from 3.4 to 3.5
On Fri, Feb 15, 2019 at 11:27 AM Richard Purdie
wrote:
>
> On Thu, 2019-02-14 at 22:17 +0100, Alexander Kanavin wrote:
> > On Thu, 14 Feb 2019 at 22:10, Alex Kiernan
> > wrote:
> >
> > > +PV .= "+git${SRCPV}"
> >
> > This is unnecessary and adds clutter. Just the plain version number
> > is enough.
>
> If I read the original commit message correctly, it is necessary as the
> version is 3.5 plus a bugfix?
>
Yes it was 3.5 + a bug fix.
Ignore v2 that I sent!
--
Alex Kiernan
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 1/2] meson.bbclass: point to llvm-config
On Thu, Feb 14, 2019 at 11:32 PM Anuj Mittal wrote:
>
> Allow packages using llvm-config to find it using meson's dependency
> interface.
>
> Signed-off-by: Anuj Mittal
> ---
> meta/classes/meson.bbclass | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/classes/meson.bbclass b/meta/classes/meson.bbclass
> index dff0485b47..aaf873cad2 100644
> --- a/meta/classes/meson.bbclass
> +++ b/meta/classes/meson.bbclass
> @@ -89,6 +89,7 @@ ld = ${@meson_array('LD', d)}
> strip = ${@meson_array('STRIP', d)}
> readelf = ${@meson_array('READELF', d)}
> pkgconfig = 'pkg-config'
> +llvm-config = 'llvm-config8.0'
>
i think llvm should install a symlink from llvm-config
otherwise we will need to change this everytime
we upgrade llvm tonew major version
> [properties]
> needs_exe_wrapper = true
> --
> 2.17.1
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] mesa: upgrade 18.1.9 -> 18.3.3
2019. 02. 15. 14:26 keltezéssel, Alexander Kanavin írta: On Fri, 15 Feb 2019 at 14:21, Fabio Berton wrote: In my opinion, there is no relation with an update and change build system, once we can use mesa 18.3.3 without meson. Please see: https://www.phoronix.com/scan.php?page=news_item=Mesa-19.0-Deprecates-Autotools We might as well switch to meson now. The patches are ready and (mostly) working. I have read the mesa-dev list constantly regarding this change. The deprecation process was painful and issues in the meson build system still turn up occasionally. 19.0 will still have a configure option to opt-in for autotools. In this upcoming release they have worked out all known issues for meson but I would in no way want to use meson for older main releases because these changes are not backported offically. So, either keep autotools for 8.3.3 or wait for 9.0 and switch to meson. Just my 2 eurocents. Best regards, Zoltán Böszörményi Alex -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] mesa: upgrade 18.1.9 -> 18.3.3
On Fri, 15 Feb 2019 at 14:59, Otavio Salvador wrote: > > I am not going to do it: this split, when done properly, would require > > separate rounds of testing of the commits, and I've already spent more > > time on it than I really want to. > > When I replied first, I said I was going to do the upgrade at our side > and later you guys could convert to meson. > > As Fabio pointed out, there are more changes and issues to be fixed > so, we will do the upgrade here. We then can you guys so your changes > can be rebased on top of this and we avoid duplicated work. Fair enough, just please do so in a timely manner. Alex -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] mesa: upgrade 18.1.9 -> 18.3.3
On Fri, Feb 15, 2019 at 11:43 AM Alexander Kanavin wrote: > > On Fri, 15 Feb 2019 at 14:29, Otavio Salvador > wrote: > > > > > I am NOT against the switch. I am against in a single commit doing > > multiple changes at the same time. > > > > So AS MAINTAINER of the recipe, I nack this commit. > > I have to point out that as the maintainer you are supposed to be > doing the maintenance work. So if you feel that strongly about the > issue, please take the patch, split it as you see fit, and send it, > within reasonable time. > > I am not going to do it: this split, when done properly, would require > separate rounds of testing of the commits, and I've already spent more > time on it than I really want to. When I replied first, I said I was going to do the upgrade at our side and later you guys could convert to meson. As Fabio pointed out, there are more changes and issues to be fixed so, we will do the upgrade here. We then can you guys so your changes can be rebased on top of this and we avoid duplicated work. -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] linux-firmware: Bump to 710963f revision
Following changes are applied: 710963f Merge https://github.com/ajaykuee/linux-firmware c24aec4 nvidia: add TU10x typec controller firmware 28f5f7d Merge git://git.marvell.com/mwifiex-firmware f30a319 Merge branch 'ath10k-20190201' of git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/linux-firmware 8fcf0ec bnx2x: Add FW 7.13.11.0. 8bf607c amdgpu: add firmware for vega20 from 18.50 578aee3 amdgpu: bump year on license bd72387 linux-firmware: update Marvell PCIe-USB8997 firmware image 6cfdd52 linux-firmware: update Marvell SD8897-B0 firmware image 2206320 linux-firmware: add Marvell SD8977 firmware image 6b5e23a ath10k: QCA9984 hw1.0: update firmware-5.bin to 10.4-3.9.0.2-00021 0eef77d ath10k: QCA988X hw2.0: update firmware-5.bin to 10.2.4-1.0-00043 1bd5312 ath10k: QCA9888 hw2.0: update firmware-5.bin to 10.4-3.9.0.2-00024 97b1f93 ath10k: QCA6174 hw3.0: update board-2.bin a8b75ca Merge tag 'add-rpi-fw' of ssh://gitolite.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux-firmware 56483ad brcm: Add BCM43455 NVRAM for Raspberry Pi 3 B+ 638a91a brcm: Fix filename for BCM43430 NVRAM for the Raspberry Pi 3 Model B bc65650 amdgpu: add raven2 fw for 18.50 release 32201bb amdgpu: add picasso fw for 18.50 release b1eae29 Revert "brcm: Add BCM43455 NVRAM for Raspberry Pi 3 B+" 89d37c6 linux-firmware: Update firmware file for Intel Bluetooth,8265 f089658 linux-firmware: Update firmware patch for Intel Bluetooth 8260 ae90c3b linux-firmware: Update firmware file for Intel Bluetooth,9260 9723ba4 linux-firmware: Update firmware file for Intel Bluetooth,9560 c7148ed Merge tag 'add-rpi-fw' of ssh://gitolite.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux-firmware 128441e Merge tag 'iwlwifi-fw-2018-12-30' of git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware 56cbf41 Merge git://git.marvell.com/mwifiex-firmware 930f276 brcm: Add BCM43430 NVRAM for the Raspberry Pi 3 Model B fca5958 brcm: Add BCM43455 NVRAM for Raspberry Pi 3 B+ 63ca64a linux-firmware: update Marvell USB8801 B0 firmware image b727739 iwlwifi: update firmwares for 9000 series 80dee31 cxgb4: update firmware to revision 1.22.9.0 0f22c85 Revert "amdgpu: update vega10 fw for 18.50 release" 117d211 brcm: Add 4330 NVRAM for the Prowise PT301 tablet 912d6a5 brcm: Add 43430 NVRAM for the Chuwi Vi8 Plus tablet f16cf5e brcm: Add 43340 based AP6234 NVRAM for the Meegopad T08 HDMI stick 5a2766c brcm: Add 43430a0 based AP6212 NVRAM for the Jumper EZpad mini 3 tablet 867ac13 brcm: Add 43430a0 based AP6212 NVRAM for the Onda V80 Plus tablet a5662fb brcm: Add 4356 based AP6356 NVRAM for the GPD win handheld f055ceb brcm: Add brcmfmac43362-sdio.lemaker,bananapro.txt symlink d9430ac brcm: Add 43362 based AP6210 NVRAM for the Cubietech Cubietruck eb34562 WHENCE: Put quotes around brcmfmac NVRAM filenames be15035 check_whence.py: Add support for filenames with spaces in them e6b9001 rtl_bt: Add firmware and configuration files for the Bluetooth part of RTL8723BS 3de2546 Merge git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware 494709e Merge branch 'BXT_HUC' of git://anongit.freedesktop.org/drm/drm-firmware 8707ef3 iwlwifi: update firmwares for 8000 series 156b549 iwlwifi: add -43.ucode for 9000 series 8a396b6 iwlwifi: update -41.ucode for 9000 series 211de16 brcm: provide new firmwares for BCM4366 chipset 813fa1f Mellanox: Add new mlxsw_spectrum firmware 13.1910.622 a330ddb Merge branch 'for-upstream' of https://github.com/crojewsk/linux-firmware 8de1d88 cavium: Update firmware for CNN55XX crypto driver a7ea5a8 amdgpu: update vega12 fw for 18.50 release ec4b0cd amdgpu: update vega10 fw for 18.50 release 1abe3c3 amdgpu: update raven fw for 18.50 release 6e38fef amdgpu: update polaris11 fw for 18.50 release df89864 amdgpu: update polaris10 fw for 18.50 release a91e850 amdgpu: add firmware for vega12 6cca138 amdgpu: Add new polaris MC firmwares e8404a6 amdgpu: Add new polaris SMC firmwares 8aa9e3e linux-firmware: Update AMD cpu microcode f3f6ada Merge branch 'MSCC-PHYs' of https://github.com/QSchulz/linux-firmware 4bbd950 Merge branch 'for-upstream' of git://git.chelsio.net/pub/git/linux-firmware d9fb2ee nfp: update Agilio SmartNIC flower firmware to rev AOTC-2.10.A.13 57d49d5 microchip: add firmware for VSC8574 and VSC8584 Ethernet PHYs 82f6dbf linux-firmware: intel: Update Cannonlake audio firmware. 69f153b firmware/huc/bxt: Add huC Update for BXT 5904eab nfp: update Agilio SmartNIC firmware to rev 2.1.16 e7cdec4 cxgb4: update firmware to revision 1.21.5.0 License-Update: - LICENSE.amdgpu: Copyright year update; - WHENCE: New firmware files additions and version updates; Signed-off-by: Otavio Salvador --- meta/recipes-kernel/linux-firmware/linux-firmware_git.bb | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb b/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb index d337d07a53..fdf8f19490 100644 ---
Re: [OE-core] [PATCH v3 3/3] image_types.bbclass: Set memory usage limit and CPU threads for xz
On Tue, Feb 12, 2019 at 3:48 AM Khem Raj wrote: > > when building with opkg backend and huge packages e.g. chromium/llvm all > going in parallel, memory pressure causes xz to catapult with > > do_package_write_ipk: Failed to create package, opkg-build failed with: xz: > (stdin): Cannot allocate memory > > since there are many tasks going on in parallel, xz adds to memory pressure > and it wants it all, put an upper limit for memory xz can use > > We add a variable XZ_MAXRAM with 30% of RAM limit and can be customized > if builders have more memory one can set it like The commit log refers to the wrong variable name, it seems. -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] mesa: upgrade 18.1.9 -> 18.3.3
On Fri, 15 Feb 2019 at 14:29, Otavio Salvador wrote: > > I am NOT against the switch. I am against in a single commit doing > multiple changes at the same time. > > So AS MAINTAINER of the recipe, I nack this commit. I have to point out that as the maintainer you are supposed to be doing the maintenance work. So if you feel that strongly about the issue, please take the patch, split it as you see fit, and send it, within reasonable time. I am not going to do it: this split, when done properly, would require separate rounds of testing of the commits, and I've already spent more time on it than I really want to. Alex -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [OE-Core][PATCH v2] bmap-tools: update from 3.4 to 3.5
On Fri, Feb 15, 2019 at 8:02 AM Alex Kiernan wrote:
>
> bmap-tools 3.5 was released August 2018 but has no release tarball, so
> switch to using the git fetcher. Also pull in the fix for StopIteration
> being transformed into RuntimeError for Python 3.7.
>
> Signed-off-by: Alex Kiernan
> ---
>
> Changes in v2:
> - Drop append of "+git${SRCPV}" to PV
Please keep the SRCPV as it is not pointing directly to the tag, but
for a commit next. So keeping the SRCPV is indeed required for
correctness.
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.brhttp://code.ossystems.com.br
Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] mesa: upgrade 18.1.9 -> 18.3.3
Alex, On Fri, Feb 15, 2019 at 11:26 AM Alexander Kanavin wrote: > > On Fri, 15 Feb 2019 at 14:21, Fabio Berton > wrote: > > In my opinion, there is no relation with an update and change build > > system, once we can use mesa 18.3.3 without meson. > > Please see: > https://www.phoronix.com/scan.php?page=news_item=Mesa-19.0-Deprecates-Autotools > > We might as well switch to meson now. The patches are ready and > (mostly) working. I am NOT against the switch. I am against in a single commit doing multiple changes at the same time. So AS MAINTAINER of the recipe, I nack this commit. -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] mesa: upgrade 18.1.9 -> 18.3.3
On Fri, 15 Feb 2019 at 14:21, Fabio Berton wrote: > In my opinion, there is no relation with an update and change build > system, once we can use mesa 18.3.3 without meson. Please see: https://www.phoronix.com/scan.php?page=news_item=Mesa-19.0-Deprecates-Autotools We might as well switch to meson now. The patches are ready and (mostly) working. Alex -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] mesa: upgrade 18.1.9 -> 18.3.3
Hello,
On Fri, Feb 15, 2019 at 11:22 AM Fabio Berton
wrote:
> In my opinion, there is no relation with an update and change build
> system, once we can use mesa 18.3.3 without meson.
Agreed.
> On Fri, Feb 15, 2019 at 1:11 PM Alexander Kanavin
> wrote:
...
> See commit 30b10dbb7c6f6bdf3e489620f8333c727bd3a6dd
> move ${sysconfdir}/drirc to ${datadir}/drirc.d/00-mesa-defaults.conf
>
> We can remove ${sysconfdir}/drirc from FILES_${PN}
Agreed. Alex, as said, we need to upgrade first and move build system next.
Also, the build native change is another fix and should be sent
independently, with a proper commit log.
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.brhttp://code.ossystems.com.br
Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] mesa: upgrade 18.1.9 -> 18.3.3
Hi All!
In my opinion, there is no relation with an update and change build
system, once we can use mesa 18.3.3 without meson.
On Fri, Feb 15, 2019 at 1:11 PM Alexander Kanavin
wrote:
>
> From: Anuj Mittal
>
> * For changes, see:
> https://www.mesa3d.org/relnotes/18.3.3.html
>
> * Convert from using autotools to meson and get rid of unnecessary
> patches.
>
> * Include a patch to fix detection of host os combinations that we build
> for.
>
> Alex:
> * fixed mesa-native failures by correctly setting disabled variants of
> PACKAGECONFIGs
>
> * Added a backported patch to avoid a build failure
>
> Signed-off-by: Anuj Mittal
> Signed-off-by: Alexander Kanavin
> ---
> ...0001-Simplify-wayland-scanner-lookup.patch | 39 ---
> ...k-for-all-linux-host_os-combinations.patch | 49 +
> ...M-version-when-using-LLVM-Git-releas.patch | 44
> ...-Use-Python-3-to-execute-the-scripts.patch | 32 -
> ...-dri-i965-Add-missing-time.h-include.patch | 36 --
> ...R-for-defining-WAYLAND_PROTOCOLS_DAT.patch | 37 --
> .../mesa/files/fix-NULL-error.patch | 50 +
> .../{mesa-gl_18.1.9.bb => mesa-gl_18.3.3.bb} | 0
> meta/recipes-graphics/mesa/mesa.inc | 70 +--
> .../mesa/{mesa_18.1.9.bb => mesa_18.3.3.bb} | 11 ++-
> 10 files changed, 136 insertions(+), 232 deletions(-)
> delete mode 100644
> meta/recipes-graphics/mesa/files/0001-Simplify-wayland-scanner-lookup.patch
> create mode 100644
> meta/recipes-graphics/mesa/files/0001-meson.build-check-for-all-linux-host_os-combinations.patch
> delete mode 100644
> meta/recipes-graphics/mesa/files/0003-Properly-get-LLVM-version-when-using-LLVM-Git-releas.patch
> delete mode 100644
> meta/recipes-graphics/mesa/files/0004-Use-Python-3-to-execute-the-scripts.patch
> delete mode 100644
> meta/recipes-graphics/mesa/files/0005-dri-i965-Add-missing-time.h-include.patch
> delete mode 100644
> meta/recipes-graphics/mesa/files/0006-use-PKG_CHECK_VAR-for-defining-WAYLAND_PROTOCOLS_DAT.patch
> create mode 100644 meta/recipes-graphics/mesa/files/fix-NULL-error.patch
> rename meta/recipes-graphics/mesa/{mesa-gl_18.1.9.bb => mesa-gl_18.3.3.bb}
> (100%)
> rename meta/recipes-graphics/mesa/{mesa_18.1.9.bb => mesa_18.3.3.bb} (54%)
>
> diff --git
> a/meta/recipes-graphics/mesa/files/0001-Simplify-wayland-scanner-lookup.patch
> b/meta/recipes-graphics/mesa/files/0001-Simplify-wayland-scanner-lookup.patch
> deleted file mode 100644
> index a50d2a2ba28..000
> ---
> a/meta/recipes-graphics/mesa/files/0001-Simplify-wayland-scanner-lookup.patch
> +++ /dev/null
> @@ -1,39 +0,0 @@
> -From 7e8e0f8a8ac2425e19a2f340c9e3da9345f25940 Mon Sep 17 00:00:00 2001
> -From: Jussi Kukkonen
> -Date: Tue, 15 Nov 2016 15:20:49 +0200
> -Subject: [PATCH 1/6] Simplify wayland-scanner lookup
> -Organization: O.S. Systems Software LTDA.
> -
> -Don't use pkg-config to lookup the path of a binary that's in the path.
> -
> -Alternatively we'd have to prefix the path returned by pkg-config with
> -PKG_CONFIG_SYSROOT_DIR.
> -
> -Upstream-Status: Pending
> -Signed-off-by: Jussi Kukkonen
> -Signed-off-by: Otavio Salvador
>
> - configure.ac | 7 +--
> - 1 file changed, 1 insertion(+), 6 deletions(-)
> -
> -diff --git a/configure.ac b/configure.ac
> -index 14f1af2b2f..916d0bd207 100644
> a/configure.ac
> -+++ b/configure.ac
> -@@ -1825,12 +1825,7 @@ for plat in $platforms; do
> - PKG_CHECK_MODULES([WAYLAND_PROTOCOLS], [wayland-protocols >=
> $WAYLAND_PROTOCOLS_REQUIRED])
> - WAYLAND_PROTOCOLS_DATADIR=`$PKG_CONFIG --variable=pkgdatadir
> wayland-protocols`
> -
> --PKG_CHECK_MODULES([WAYLAND_SCANNER], [wayland-scanner],
> -- WAYLAND_SCANNER=`$PKG_CONFIG
> --variable=wayland_scanner wayland-scanner`,
> -- WAYLAND_SCANNER='')
> --if test "x$WAYLAND_SCANNER" = x; then
> --AC_PATH_PROG([WAYLAND_SCANNER], [wayland-scanner], [:])
> --fi
> -+AC_PATH_PROG([WAYLAND_SCANNER], [wayland-scanner], [:])
> -
> - if test "x$WAYLAND_SCANNER" = "x:"; then
> - AC_MSG_ERROR([wayland-scanner is needed to compile the
> wayland platform])
> ---
> -2.18.0
> -
> diff --git
> a/meta/recipes-graphics/mesa/files/0001-meson.build-check-for-all-linux-host_os-combinations.patch
>
> b/meta/recipes-graphics/mesa/files/0001-meson.build-check-for-all-linux-host_os-combinations.patch
> new file mode 100644
> index 000..1147eacdd93
> --- /dev/null
> +++
> b/meta/recipes-graphics/mesa/files/0001-meson.build-check-for-all-linux-host_os-combinations.patch
> @@ -0,0 +1,49 @@
> +From 8140dc078bcdbc5fbaf1c46c3fd3efbe587a0f29 Mon Sep 17 00:00:00 2001
> +From: Anuj Mittal
> +Date: Mon, 11 Feb 2019 20:55:27 +0800
> +Subject: [PATCH] meson.build: check for all linux host_os combinations
> +
> +Make sure that we are also looking for our host_os combinations like
> +linux-musl etc. when
[OE-core] [PATCH] mesa: upgrade 18.1.9 -> 18.3.3
From: Anuj Mittal
* For changes, see:
https://www.mesa3d.org/relnotes/18.3.3.html
* Convert from using autotools to meson and get rid of unnecessary
patches.
* Include a patch to fix detection of host os combinations that we build
for.
Alex:
* fixed mesa-native failures by correctly setting disabled variants of
PACKAGECONFIGs
* Added a backported patch to avoid a build failure
Signed-off-by: Anuj Mittal
Signed-off-by: Alexander Kanavin
---
...0001-Simplify-wayland-scanner-lookup.patch | 39 ---
...k-for-all-linux-host_os-combinations.patch | 49 +
...M-version-when-using-LLVM-Git-releas.patch | 44
...-Use-Python-3-to-execute-the-scripts.patch | 32 -
...-dri-i965-Add-missing-time.h-include.patch | 36 --
...R-for-defining-WAYLAND_PROTOCOLS_DAT.patch | 37 --
.../mesa/files/fix-NULL-error.patch | 50 +
.../{mesa-gl_18.1.9.bb => mesa-gl_18.3.3.bb} | 0
meta/recipes-graphics/mesa/mesa.inc | 70 +--
.../mesa/{mesa_18.1.9.bb => mesa_18.3.3.bb} | 11 ++-
10 files changed, 136 insertions(+), 232 deletions(-)
delete mode 100644
meta/recipes-graphics/mesa/files/0001-Simplify-wayland-scanner-lookup.patch
create mode 100644
meta/recipes-graphics/mesa/files/0001-meson.build-check-for-all-linux-host_os-combinations.patch
delete mode 100644
meta/recipes-graphics/mesa/files/0003-Properly-get-LLVM-version-when-using-LLVM-Git-releas.patch
delete mode 100644
meta/recipes-graphics/mesa/files/0004-Use-Python-3-to-execute-the-scripts.patch
delete mode 100644
meta/recipes-graphics/mesa/files/0005-dri-i965-Add-missing-time.h-include.patch
delete mode 100644
meta/recipes-graphics/mesa/files/0006-use-PKG_CHECK_VAR-for-defining-WAYLAND_PROTOCOLS_DAT.patch
create mode 100644 meta/recipes-graphics/mesa/files/fix-NULL-error.patch
rename meta/recipes-graphics/mesa/{mesa-gl_18.1.9.bb => mesa-gl_18.3.3.bb}
(100%)
rename meta/recipes-graphics/mesa/{mesa_18.1.9.bb => mesa_18.3.3.bb} (54%)
diff --git
a/meta/recipes-graphics/mesa/files/0001-Simplify-wayland-scanner-lookup.patch
b/meta/recipes-graphics/mesa/files/0001-Simplify-wayland-scanner-lookup.patch
deleted file mode 100644
index a50d2a2ba28..000
---
a/meta/recipes-graphics/mesa/files/0001-Simplify-wayland-scanner-lookup.patch
+++ /dev/null
@@ -1,39 +0,0 @@
-From 7e8e0f8a8ac2425e19a2f340c9e3da9345f25940 Mon Sep 17 00:00:00 2001
-From: Jussi Kukkonen
-Date: Tue, 15 Nov 2016 15:20:49 +0200
-Subject: [PATCH 1/6] Simplify wayland-scanner lookup
-Organization: O.S. Systems Software LTDA.
-
-Don't use pkg-config to lookup the path of a binary that's in the path.
-
-Alternatively we'd have to prefix the path returned by pkg-config with
-PKG_CONFIG_SYSROOT_DIR.
-
-Upstream-Status: Pending
-Signed-off-by: Jussi Kukkonen
-Signed-off-by: Otavio Salvador
- configure.ac | 7 +--
- 1 file changed, 1 insertion(+), 6 deletions(-)
-
-diff --git a/configure.ac b/configure.ac
-index 14f1af2b2f..916d0bd207 100644
a/configure.ac
-+++ b/configure.ac
-@@ -1825,12 +1825,7 @@ for plat in $platforms; do
- PKG_CHECK_MODULES([WAYLAND_PROTOCOLS], [wayland-protocols >=
$WAYLAND_PROTOCOLS_REQUIRED])
- WAYLAND_PROTOCOLS_DATADIR=`$PKG_CONFIG --variable=pkgdatadir
wayland-protocols`
-
--PKG_CHECK_MODULES([WAYLAND_SCANNER], [wayland-scanner],
-- WAYLAND_SCANNER=`$PKG_CONFIG
--variable=wayland_scanner wayland-scanner`,
-- WAYLAND_SCANNER='')
--if test "x$WAYLAND_SCANNER" = x; then
--AC_PATH_PROG([WAYLAND_SCANNER], [wayland-scanner], [:])
--fi
-+AC_PATH_PROG([WAYLAND_SCANNER], [wayland-scanner], [:])
-
- if test "x$WAYLAND_SCANNER" = "x:"; then
- AC_MSG_ERROR([wayland-scanner is needed to compile the
wayland platform])
---
-2.18.0
-
diff --git
a/meta/recipes-graphics/mesa/files/0001-meson.build-check-for-all-linux-host_os-combinations.patch
b/meta/recipes-graphics/mesa/files/0001-meson.build-check-for-all-linux-host_os-combinations.patch
new file mode 100644
index 000..1147eacdd93
--- /dev/null
+++
b/meta/recipes-graphics/mesa/files/0001-meson.build-check-for-all-linux-host_os-combinations.patch
@@ -0,0 +1,49 @@
+From 8140dc078bcdbc5fbaf1c46c3fd3efbe587a0f29 Mon Sep 17 00:00:00 2001
+From: Anuj Mittal
+Date: Mon, 11 Feb 2019 20:55:27 +0800
+Subject: [PATCH] meson.build: check for all linux host_os combinations
+
+Make sure that we are also looking for our host_os combinations like
+linux-musl etc. when assuming support for DRM/KMS.
+
+Also delete a duplicate line.
+
+Signed-off-by: Anuj Mittal
+---
+ meson.build | 6 ++
+ 1 file changed, 2 insertions(+), 4 deletions(-)
+
+diff --git a/meson.build b/meson.build
+index b934d0bfc76..7cbda909735 100644
+--- a/meson.build
b/meson.build
+@@ -34,7 +34,7 @@ cpp = meson.get_compiler('cpp')
+
+ null_dep = dependency('', required : false)
+
Re: [OE-core] dracut is impossible to run in do_rootfs
Hi again, I am now replying to myself. If anyone is interested, I have solved it in dracut so it can use a sysroot. See: https://github.com/dracutdevs/dracut/pull/535 Then, the dracut recipe also needs changes so it can be built as native. A recipe is needed for a cross-compiler ldd from this: https://gist.github.com/jerome-pouiller/c403786c1394f53f44a3b61214489e6f Then a dracut.bbclass to be used by a kernel recipe or anything else that wants to be included in the initramfs, like extra dracut modules or custom boot splash themes. I have all of this working now in Yocto 2.5 via a bbappend for dracut and the two extras. Eventually, I would like to upstream these changes when my dracut PR is merged, hopefully before 050 is released. 2018. 11. 14. 10:53 keltezéssel, Böszörményi Zoltán via Openembedded-core írta: Hi, I need to create the initramfs for the target build during do_rootfs using dracut to include systemd and plymouth into it and using the modules from the kernel version the image was built with. Currently I am on Yocto 2.5. There are several problem I am facing. First, the dracut recipe needs some fixes in the RDEPENDS/RRECOMMENDS clauses to only use subpackages of the recipes it depends on in class-target only. I could fix this with a bbappend file. Then, all the packages in the system that use the update-alternatives.bbclass have unusable symlinks during the do_rootfs stage. E.g. coreutils's binaries use this: zboszormenyi@buildbox-0001 rootfs]$ ls -l usr/bin/[ lrwxrwxrwx 1 zboszormenyi zboszormenyi 27 nov 14 03.51 usr/bin/[ -> /usr/bin/lbracket.coreutils Of course, the target of the symlink does not exist on the build host. As a consequence, dracut will not find anything that it needs to copy to the initramfs. Is there a way to tell update-alternatives.bbclass (e.g. globally from my layer.conf) to just use the relative symlink it is given? Thanks in advance, Zoltán Böszörményi -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 2/2] mesa: upgrade 18.1.9 -> 18.3.3
> -Original Message- > From: Alexander Kanavin [mailto:alex.kana...@gmail.com] > Sent: Friday, February 15, 2019 08:52 PM > To: Otavio Salvador > Cc: Mittal, Anuj ; Fabio Berton > ; Patches and discussions about the oe-core > layer > > Subject: Re: [OE-core] [PATCH 2/2] mesa: upgrade 18.1.9 -> 18.3.3 > > On Fri, 15 Feb 2019 at 13:46, Otavio Salvador > > wrote: > > > I think this patch should be split off. First we should upgrade to the > > newer release and later convert it to use meson. > > > > This allows for better review and testing. > > > > If desired, we can do the upgrade on our side and Anuj can handle the > > meson convertion, next. Does it make sense? > > Not really, in my opinion, it's just more friction and coordination, and > delays. It's > better to just fix the issues with the existing patch. > I'll send a fixed version in a few minutes. > Thanks Alex. I didn’t want to spend time in refreshing patches in one commit and testing and making sure they were correct when some of them were going to be removed in next. So I took this approach. Thanks, Anuj -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 2/2] mesa: upgrade 18.1.9 -> 18.3.3
On Fri, 15 Feb 2019 at 13:46, Otavio Salvador wrote: > I think this patch should be split off. First we should upgrade to the > newer release and later convert it to use meson. > > This allows for better review and testing. > > If desired, we can do the upgrade on our side and Anuj can handle the > meson convertion, next. Does it make sense? Not really, in my opinion, it's just more friction and coordination, and delays. It's better to just fix the issues with the existing patch. I'll send a fixed version in a few minutes. Alex -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 2/2] mesa: upgrade 18.1.9 -> 18.3.3
On Fri, Feb 15, 2019 at 5:32 AM Anuj Mittal wrote: > > * For changes, see: > https://www.mesa3d.org/relnotes/18.3.3.html > > * Convert from using autotools to meson and get rid of unnecessary > patches. > > * Include a patch to fix detection of host os combinations that we build > for. > > Signed-off-by: Anuj Mittal I think this patch should be split off. First we should upgrade to the newer release and later convert it to use meson. This allows for better review and testing. If desired, we can do the upgrade on our side and Anuj can handle the meson convertion, next. Does it make sense? -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [OE-Core][PATCH] bmap-tools: update from 3.4 to 3.5
On Fri, 15 Feb 2019 at 12:27, Richard Purdie
wrote:
>
> On Thu, 2019-02-14 at 22:17 +0100, Alexander Kanavin wrote:
> > On Thu, 14 Feb 2019 at 22:10, Alex Kiernan
> > wrote:
> >
> > > +PV .= "+git${SRCPV}"
> >
> > This is unnecessary and adds clutter. Just the plain version number
> > is enough.
>
> If I read the original commit message correctly, it is necessary as the
> version is 3.5 plus a bugfix?
Seems so. Sorry for the noise.
Alex
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [OE-Core][PATCH] bmap-tools: update from 3.4 to 3.5
On Thu, 2019-02-14 at 22:17 +0100, Alexander Kanavin wrote:
> On Thu, 14 Feb 2019 at 22:10, Alex Kiernan
> wrote:
>
> > +PV .= "+git${SRCPV}"
>
> This is unnecessary and adds clutter. Just the plain version number
> is enough.
If I read the original commit message correctly, it is necessary as the
version is 3.5 plus a bugfix?
Cheers,
Richard
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] busybox: 1.29.3 -> 1.30.1
On Fri, 2019-02-15 at 09:22 +0100, Andrej Valek wrote:
> - update to last stable version 1.30.1
> - remove and refresh already merged patches
>
> Signed-off-by: Andrej Valek
> ---
> ...inittab_1.29.3.bb => busybox-inittab_1.30.1.bb} | 0
> ...te-check-CONFIG_DESKTOP-before-using-od-t.patch | 83
> --
> ...-testsuite-check-uudecode-before-using-it.patch | 6 +-
> .../{busybox_1.29.3.bb => busybox_1.30.1.bb} | 5 +-
> 4 files changed, 5 insertions(+), 89 deletions(-)
> rename meta/recipes-core/busybox/{busybox-inittab_1.29.3.bb =>
> busybox-inittab_1.30.1.bb} (100%)
> delete mode 100644 meta/recipes-core/busybox/busybox/0001-testsuite-
> check-CONFIG_DESKTOP-before-using-od-t.patch
> rename meta/recipes-core/busybox/{busybox_1.29.3.bb =>
> busybox_1.30.1.bb} (89%)
There seems to be something not quite right with this:
https://autobuilder.yoctoproject.org/typhoon/#/builders/76/builds/284
https://autobuilder.yoctoproject.org/typhoon/#/builders/50/builds/283
Cheers,
Richard
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 2/2] mesa: upgrade 18.1.9 -> 18.3.3
On Fri, 15 Feb 2019 at 10:54, Richard Purdie wrote: > > * For changes, see: > > https://www.mesa3d.org/relnotes/18.3.3.html > > > > * Convert from using autotools to meson and get rid of unnecessary > > patches. > > > > * Include a patch to fix detection of host os combinations that we > > build > > for. > > > > Signed-off-by: Anuj Mittal > > This is good but I think you and Alex may need to work together to sort > out mesa-native which fails after this patchset and is needed by the > virtgl work (queued in -next). > > https://autobuilder.yoctoproject.org/typhoon/#/builders/85/builds/221 Thanks, I'll take Anuj's patch and see what needs to be changed in it. Alex -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [OE-Core][PATCH v2] bmap-tools: update from 3.4 to 3.5
bmap-tools 3.5 was released August 2018 but has no release tarball, so
switch to using the git fetcher. Also pull in the fix for StopIteration
being transformed into RuntimeError for Python 3.7.
Signed-off-by: Alex Kiernan
---
Changes in v2:
- Drop append of "+git${SRCPV}" to PV
.../bmap-tools/{bmap-tools_3.4.bb => bmap-tools_3.5.bb} | 8
1 file changed, 4 insertions(+), 4 deletions(-)
rename meta/recipes-support/bmap-tools/{bmap-tools_3.4.bb =>
bmap-tools_3.5.bb} (74%)
diff --git a/meta/recipes-support/bmap-tools/bmap-tools_3.4.bb
b/meta/recipes-support/bmap-tools/bmap-tools_3.5.bb
similarity index 74%
rename from meta/recipes-support/bmap-tools/bmap-tools_3.4.bb
rename to meta/recipes-support/bmap-tools/bmap-tools_3.5.bb
index 2aae9a3fe0d8..4609a7071c5a 100644
--- a/meta/recipes-support/bmap-tools/bmap-tools_3.4.bb
+++ b/meta/recipes-support/bmap-tools/bmap-tools_3.5.bb
@@ -9,12 +9,12 @@ SECTION = "console/utils"
LICENSE = "GPLv2"
LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
-SRC_URI = "https://github.com/intel/${BPN}/releases/download/v${PV}/${BP}.tgz;
+SRC_URI = "git://github.com/intel/${BPN}"
-SRC_URI[md5sum] = "883420183611aa137cbaf68a91ef0d7e"
-SRC_URI[sha256sum] =
"0064891270c180c190f41925b0f6fb9cecac3056f1168d2592dbe90e5f226c0a"
+SRCREV = "db7087b883bf52cbff063ad17a41cc1cbb85104d"
+S = "${WORKDIR}/git"
-UPSTREAM_CHECK_URI = "https://github.com/intel/${BPN}/releases;
+UPSTREAM_CHECK_GITTAGREGEX = "v(?P.*)"
RDEPENDS_${PN} = "python3-core python3-compression python3-mmap
python3-setuptools python3-fcntl"
--
2.7.4
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 3/4] libidn2: fix buildpaths qa warning
On Thu, 2019-02-14 at 21:06 -0500, kai.k...@windriver.com wrote:
> From: Kai Kang
>
> Fix buildpaths qa warning of libidn2:
>
> > WARNING: libidn2-2.0.5-r0 do_package_qa: QA Issue: File
> > /work/core2-64-poky-linux/libidn2/2.0.5-r0/packages-split/libidn2-
> > dev/usr/lib/pkgconfig/libidn2.pc
> > in package contained reference to tmpdir [buildpaths]
>
> Signed-off-by: Kai Kang
> ---
> meta/recipes-extended/libidn/libidn2_2.0.5.bb | 4
> 1 file changed, 4 insertions(+)
>
> diff --git a/meta/recipes-extended/libidn/libidn2_2.0.5.bb
> b/meta/recipes-extended/libidn/libidn2_2.0.5.bb
> index 0daf7a6877..da77c4402d 100644
> --- a/meta/recipes-extended/libidn/libidn2_2.0.5.bb
> +++ b/meta/recipes-extended/libidn/libidn2_2.0.5.bb
> @@ -26,4 +26,8 @@ EXTRA_OECONF += "--disable-rpath \
> LICENSE_${PN} = "(GPLv2+ | LGPLv3)"
> LICENSE_${PN}-bin = "GPLv3+"
>
> +do_install_append () {
> +sed -i 's#${RECIPE_SYSROOT}##'
> ${D}${libdir}/pkgconfig/libidn2.pc
> +}
> +
> BBCLASSEXTEND = "native nativesdk"
I have a strong dislike for editing .pc files after the fact. Part of
the concern is sed expressions like this bitrot badly, its hard to tell
if they still work as intended.
Is there not a way we can generate a correct .pc file in the first
place even if that means a patch?
Cheers,
Richard
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 2/2] mesa: upgrade 18.1.9 -> 18.3.3
On Fri, 2019-02-15 at 15:32 +0800, Anuj Mittal wrote: > * For changes, see: > https://www.mesa3d.org/relnotes/18.3.3.html > > * Convert from using autotools to meson and get rid of unnecessary > patches. > > * Include a patch to fix detection of host os combinations that we > build > for. > > Signed-off-by: Anuj Mittal This is good but I think you and Alex may need to work together to sort out mesa-native which fails after this patchset and is needed by the virtgl work (queued in -next). https://autobuilder.yoctoproject.org/typhoon/#/builders/85/builds/221 Cheers, Richard -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] oeqa/manual/bsp-hw.json: add non-IA tests
From: Mazliana
QA team found that 10 manual bsp test cases from Testopia for
Beaglebone, EdgeRouter, and MPC need to be up streamed
[YOCTO #12650]
Signed-off-by: Mazliana
---
meta/lib/oeqa/manual/bsp-hw.json | 260 +++
1 file changed, 260 insertions(+)
diff --git a/meta/lib/oeqa/manual/bsp-hw.json b/meta/lib/oeqa/manual/bsp-hw.json
index a2b1d3e..2bbf4b2 100644
--- a/meta/lib/oeqa/manual/bsp-hw.json
+++ b/meta/lib/oeqa/manual/bsp-hw.json
@@ -1196,5 +1196,265 @@
},
"summary": "Test_Seek_bar_and_volume_control"
}
+},
+{
+"test": {
+"@alias":
"bsps-runtime.bsps-runtime.Check_if_watchdog_can_reset_the_target_system",
+"author": [
+{
+"email": "yi.z...@windriver.com",
+"name": "yi.z...@windriver.com"
+}
+],
+"execution": {
+"1": {
+"action": "1.Check if watchdog device exist in /dev/
directory. Run command echo 1 > /dev/watchdog and wait for 60s. Then, the
target will reboot.",
+"expected_results": "The watchdog device exist in /dev/
directory and can reboot the target.\n"
+}
+},
+"summary": "Check_if_watchdog_can_reset_the_target_system"
+}
+},
+{
+"test": {
+"@alias":
"bsps-runtime.bsps-runtime.Check_if_RTC_(Real_Time_Clock)_can_work_correctly",
+"author": [
+{
+"email": "yi.z...@windriver.com",
+"name": "yi.z...@windriver.com"
+}
+],
+"execution": {
+"1": {
+"action": "Read time from RTC registers.
root@localhost:/root> hwclock -r Sun Mar 22 04:05:47 1970 -0.001948 seconds ",
+"expected_results": "Can read and set the time from RTC.\n"
+},
+"2": {
+"action": "Set system current time root@localhost:/root>
date 062309452008 ",
+"expected_results": ""
+},
+"3": {
+"action": "Synchronize the system current time to RTC
registers root@localhost:/root> hwclock -w ",
+"expected_results": ""
+},
+"4": {
+"action": "Read time from RTC registers
root@localhost:/root> hwclock -r ",
+"expected_results": ""
+},
+"5": {
+"action": "Reboot target and read time from RTC again\n",
+"expected_results": ""
+}
+},
+"summary": "Check_if_RTC_(Real_Time_Clock)_can_work_correctly"
+}
+},
+{
+"test": {
+"@alias":
"bsps-runtime.bsps-runtime.Check_if_target_can_support_EEPROM",
+"author": [
+{
+"email": "yi.z...@windriver.com",
+"name": "yi.z...@windriver.com"
+}
+],
+"execution": {
+"1": {
+"action": "Check eeprom device exist in
/sys/bus/i2c/devices/ ",
+"expected_results": "Hexdump can read data from eeprom.\n"
+},
+"2": {
+"action": "Run \"hexdump eeprom\"
commandroot@mpc8315e-rdb:/sys/bus/i2c/devices/1-0051> hexdump eeprom000
9210 0b02 0211 0009 0b52 0108 0c00 3c00010 6978 6930 6911 208c 7003 3c3c
00f0 8381\u2026\n",
+"expected_results": ""
+}
+},
+"summary": "Check_if_target_can_support_EEPROM"
+}
+},
+{
+"test": {
+"@alias": "bsps-tools.bsps-tools.smart_add_rpm-dir_channel_(auto)",
+"author": [
+{
+"email": "corneliux.stoice...@intel.com",
+"name": "corneliux.stoice...@intel.com"
+}
+],
+"execution": {
+"1": {
+"action": "Build out packages with poky tree and copy the
deploy/rpm directory to target directory. ",
+"expected_results": "The command should add a rpm-dir
channel with smart. "
+},
+"2": {
+"action": "On target, run \"smart channel --add myrpmdir
type=rpm-dir path=/path/to/tmp/deploy/rpm/i586\". ",
+"expected_results": "Run \"smart channel --show myrpmdir\"
can show the information about the channel:\n[myrpmdir] \ntype = rpm-dir \npath
= /path/to/tmp/deploy/rpm/i586"
+},
+"3": {
+"action": "Run \"smart channel --show myrpmdir\" and check
the output. ",
+"expected_results": "After disable the channel, run
\"smart channel
[OE-core] [PATCH 2/2] kernel-fitimage.bbclass: Introduce a way to provide external dtb
Currently kernel-fitimage gets the dtb from KERNEL_DEVICETREE, however
there are instances when the DTB file can be generated using other
recipes, provide a way to include the DTB instead of inkernel device
tree.
Add support for external device tree during the creation of fitimage.
If virtual/dtb is set then use the path provided in
EXTERNAL_KERNEL_DEVICETREE else use KERNEL_DEVICETREE during fitimage
process
Signed-off-by: Manjukumar Matha
---
meta/classes/kernel-fitimage.bbclass | 20 +++-
1 file changed, 19 insertions(+), 1 deletion(-)
diff --git a/meta/classes/kernel-fitimage.bbclass
b/meta/classes/kernel-fitimage.bbclass
index 8ebd3dd..3adb1c9 100644
--- a/meta/classes/kernel-fitimage.bbclass
+++ b/meta/classes/kernel-fitimage.bbclass
@@ -30,6 +30,13 @@ python __anonymous () {
if image:
d.appendVarFlag('do_assemble_fitimage_initramfs', 'depends', '
${INITRAMFS_IMAGE}:do_image_complete')
+ #check if there are any dtb providers
+providerdtb = d.getVar("PREFERRED_PROVIDER_virtual/dtb")
+if providerdtb:
+d.appendVarFlag('do_assemble_fitimage', 'depends', '
virtual/dtb:do_populate_sysroot')
+d.appendVarFlag('do_assemble_fitimage_initramfs', 'depends', '
virtual/dtb:do_populate_sysroot')
+d.setVar('EXTERNAL_KERNEL_DEVICETREE',
"${RECIPE_SYSROOT}/boot/devicetree")
+
# Verified boot will sign the fitImage and append the public key to
# U-Boot dtb. We ensure the U-Boot dtb is deployed before assembling
# the fitImage:
@@ -373,7 +380,8 @@ fitimage_assemble() {
#
# Step 2: Prepare a DTB image section
#
- if [ -n "${KERNEL_DEVICETREE}" ]; then
+
+ if [ -z "${EXTERNAL_KERNEL_DEVICETREE}" ] && [ -n
"${KERNEL_DEVICETREE}" ]; then
dtbcount=1
for DTB in ${KERNEL_DEVICETREE}; do
if echo ${DTB} | grep -q '/dts/'; then
@@ -391,6 +399,16 @@ fitimage_assemble() {
done
fi
+ if [ -n "${EXTERNAL_KERNEL_DEVICETREE}" ]; then
+ dtbcount=1
+ for DTBFILE in ${EXTERNAL_KERNEL_DEVICETREE}/*.dtb; do
+ DTB=`basename ${DTBFILE}`
+ DTB=$(echo "${DTB}" | tr '/' '_')
+ DTBS="${DTBS} ${DTB}"
+ fitimage_emit_section_dtb ${1} ${DTB} ${DTBFILE}
+ done
+ fi
+
#
# Step 3: Prepare a setup section. (For x86)
#
--
2.7.4
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] busybox: 1.29.3 -> 1.30.1
- update to last stable version 1.30.1
- remove and refresh already merged patches
Signed-off-by: Andrej Valek
---
...inittab_1.29.3.bb => busybox-inittab_1.30.1.bb} | 0
...te-check-CONFIG_DESKTOP-before-using-od-t.patch | 83 --
...-testsuite-check-uudecode-before-using-it.patch | 6 +-
.../{busybox_1.29.3.bb => busybox_1.30.1.bb} | 5 +-
4 files changed, 5 insertions(+), 89 deletions(-)
rename meta/recipes-core/busybox/{busybox-inittab_1.29.3.bb =>
busybox-inittab_1.30.1.bb} (100%)
delete mode 100644
meta/recipes-core/busybox/busybox/0001-testsuite-check-CONFIG_DESKTOP-before-using-od-t.patch
rename meta/recipes-core/busybox/{busybox_1.29.3.bb => busybox_1.30.1.bb} (89%)
diff --git a/meta/recipes-core/busybox/busybox-inittab_1.29.3.bb
b/meta/recipes-core/busybox/busybox-inittab_1.30.1.bb
similarity index 100%
rename from meta/recipes-core/busybox/busybox-inittab_1.29.3.bb
rename to meta/recipes-core/busybox/busybox-inittab_1.30.1.bb
diff --git
a/meta/recipes-core/busybox/busybox/0001-testsuite-check-CONFIG_DESKTOP-before-using-od-t.patch
b/meta/recipes-core/busybox/busybox/0001-testsuite-check-CONFIG_DESKTOP-before-using-od-t.patch
deleted file mode 100644
index 9b96eeeae5..00
---
a/meta/recipes-core/busybox/busybox/0001-testsuite-check-CONFIG_DESKTOP-before-using-od-t.patch
+++ /dev/null
@@ -1,83 +0,0 @@
-From b09db631e77c63ebe733c69b00108f043f1f1d85 Mon Sep 17 00:00:00 2001
-From: Chen Qi
-Date: Wed, 21 Nov 2018 10:00:29 +0800
-Subject: [PATCH] testsuite: check CONFIG_DESKTOP before using 'od -t'
-
-The '-t' option for od is enabled by CONFIG_DESKTOP. So
-check this config before using 'od -t' in test cases.
-
-Upstream-Status: Submitted
[http://lists.busybox.net/pipermail/busybox/2018-November/086895.html]
-
-Signed-off-by: Chen Qi
- testsuite/echo/echo-prints-dash| 1 +
- testsuite/echo/echo-prints-non-opts| 1 +
- testsuite/echo/echo-prints-slash-zero | 2 +-
- testsuite/echo/echo-prints-slash_00041 | 2 +-
- testsuite/echo/echo-prints-slash_0041 | 2 +-
- testsuite/echo/echo-prints-slash_041 | 2 +-
- testsuite/echo/echo-prints-slash_41| 2 +-
- 7 files changed, 7 insertions(+), 5 deletions(-)
-
-diff --git a/testsuite/echo/echo-prints-dash b/testsuite/echo/echo-prints-dash
-index ddcdbad..f1f31a0 100644
a/testsuite/echo/echo-prints-dash
-+++ b/testsuite/echo/echo-prints-dash
-@@ -1 +1,2 @@
-+# FEATURE: CONFIG_DESKTOP
- test "`busybox echo - | od -t x1 | head -n 1`" = "000 2d 0a"
-diff --git a/testsuite/echo/echo-prints-non-opts
b/testsuite/echo/echo-prints-non-opts
-index c7d1e20..4e642a1 100644
a/testsuite/echo/echo-prints-non-opts
-+++ b/testsuite/echo/echo-prints-non-opts
-@@ -1 +1,2 @@
-+# FEATURE: CONFIG_DESKTOP
- test "`busybox echo -neEZ | od -t x1 | head -n 1`" = "000 2d 6e 65 45 5a
0a"
-diff --git a/testsuite/echo/echo-prints-slash-zero
b/testsuite/echo/echo-prints-slash-zero
-index d97ed8e..948f899 100644
a/testsuite/echo/echo-prints-slash-zero
-+++ b/testsuite/echo/echo-prints-slash-zero
-@@ -1,3 +1,3 @@
--# FEATURE: CONFIG_FEATURE_FANCY_ECHO
-+# FEATURE: CONFIG_FEATURE_FANCY_ECHO CONFIG_DESKTOP
-
- test "`busybox echo -e -n 'msg\n\0' | od -t x1 | head -n 1`" = "000 6d 73
67 0a 00"
-diff --git a/testsuite/echo/echo-prints-slash_00041
b/testsuite/echo/echo-prints-slash_00041
-index 9cffabd..7ea217b 100644
a/testsuite/echo/echo-prints-slash_00041
-+++ b/testsuite/echo/echo-prints-slash_00041
-@@ -1,3 +1,3 @@
--# FEATURE: CONFIG_FEATURE_FANCY_ECHO
-+# FEATURE: CONFIG_FEATURE_FANCY_ECHO CONFIG_DESKTOP
-
- test "`busybox echo -ne '\00041z' | od -t x1 | head -n 1`" = "000 04 31
7a"
-diff --git a/testsuite/echo/echo-prints-slash_0041
b/testsuite/echo/echo-prints-slash_0041
-index b07429d..941faca 100644
a/testsuite/echo/echo-prints-slash_0041
-+++ b/testsuite/echo/echo-prints-slash_0041
-@@ -1,3 +1,3 @@
--# FEATURE: CONFIG_FEATURE_FANCY_ECHO
-+# FEATURE: CONFIG_FEATURE_FANCY_ECHO CONFIG_DESKTOP
-
- test "`busybox echo -ne '\0041z' | od -t x1 | head -n 1`" = "000 21 7a"
-diff --git a/testsuite/echo/echo-prints-slash_041
b/testsuite/echo/echo-prints-slash_041
-index 1d70cec..60cbfca 100644
a/testsuite/echo/echo-prints-slash_041
-+++ b/testsuite/echo/echo-prints-slash_041
-@@ -1,3 +1,3 @@
--# FEATURE: CONFIG_FEATURE_FANCY_ECHO
-+# FEATURE: CONFIG_FEATURE_FANCY_ECHO CONFIG_DESKTOP
-
- test "`busybox echo -ne '\041z' | od -t x1 | head -n 1`" = "000 21 7a"
-diff --git a/testsuite/echo/echo-prints-slash_41
b/testsuite/echo/echo-prints-slash_41
-index 6d8999b..afd7c36 100644
a/testsuite/echo/echo-prints-slash_41
-+++ b/testsuite/echo/echo-prints-slash_41
-@@ -1,3 +1,3 @@
--# FEATURE: CONFIG_FEATURE_FANCY_ECHO
-+# FEATURE: CONFIG_FEATURE_FANCY_ECHO CONFIG_DESKTOP
-
- test "`busybox echo -ne '\41z' | od -t x1 | head -n 1`" = "000 21 7a"
---
-2.7.4
-
diff --git
a/meta/recipes-core/busybox/busybox/0001-testsuite-check-uudecode-before-using-it.patch
