Re: [OE-core] [PATCH] core-image-sato-sdk: test image with 512M memory
On 2019/8/12 下午4:57, Kang Kai wrote: On 2019/7/27 下午4:42, Kang Kai wrote: On 2019/7/27 上午5:40, richard.pur...@linuxfoundation.org wrote: On Fri, 2019-07-26 at 05:23 -0400, kai.k...@windriver.com wrote: From: Kai Kang When run do_testimage for core-image-sato-sdk, it fails to pass test case: RESULTS - systemd.SystemdBasicTests.test_systemd_failed: FAILED (0.43s) It is OOM issue and daemon rpc.statd is killed: [ 531.306146] Out of memory: Kill process 193 (rpc.statd) score 200 or sacrifice child Increase the memory of qemu to 512M to avoid such OOM issue. Signed-off-by: Kai Kang --- meta/recipes-sato/images/core-image-sato-sdk.bb | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/recipes-sato/images/core-image-sato-sdk.bb b/meta/recipes-sato/images/core-image-sato-sdk.bb index d7cc52b52b..f7963d018e 100644 --- a/meta/recipes-sato/images/core-image-sato-sdk.bb +++ b/meta/recipes-sato/images/core-image-sato-sdk.bb @@ -9,3 +9,4 @@ IMAGE_FEATURES += "dev-pkgs tools-sdk \ IMAGE_INSTALL += "kernel-devsrc" +TEST_QEMUPARAMS = "-m 512" Any idea what is using so much memory in the image when this happens? Its rather sad that we can't have NFS+systemd with 256MB memory... It caused by stap test case. I minimized the test cases to TEST_SUITES = "ping date ssh systemd stap kernelmodule gcc " which could reproduce the error. And it PASSes testimage that remove stap test from default TEST_SUITES: TEST_SUITES_remove = 'stap' But I can't reproduce the OOM failure to run stap tests manually. Hi Richard, The root cause of test case stap fails is available memory is too low. Compare systemd with sysvinit, memory status are listed: systemd: root@qemux86:~# free -h total used free shared buff/cache available Mem: 239Mi 120Mi 23Mi 8.0Mi 94Mi 100Mi Swap: 0B 0B 0B sysvinit: root@qemux86:~# free -h total used free shared buff/cache available Mem: 239Mi 45Mi 111Mi 0.0Ki 82Mi 184Mi Swap: 0B 0B 0B With systemd, processes of rpc.statd and rpc.mountd take about less than 80M memories. And I compared with Debian 10, they take similar size of memories. PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 464 rpcuser 20 0 56316 51336 2192 S 0.0 20.9 0:00.09 rpc.statd 186 root 20 0 30136 27024 2280 S 0.0 11.0 0:00.02 rpc.mountd Compare to sysvinit, they take only about 2M and 448K: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 567 rpcuser 20 0 3444 2372 1792 S 0.0 1.0 0:00.00 rpc.statd 677 root 20 0 3700 448 0 S 0.0 0.2 0:00.00 rpc.mountd I didn't figure out the differences between these 2 ways to start the commands: ExecStart=/usr/sbin/rpc.statd -F $STATD_OPTS Vs. test -x "$NFS_STATD" || NFS_STATD=/usr/sbin/rpc.statd start-stop-daemon --start --exec "$NFS_STATD" --pidfile "$STATD_PID" Hi Richard, Any more comment here please? Regards, Kai Regards, Kai Regards, Kai Cheers, Richard -- Kai Kang -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 3/3] qemuriscv64: Specify the firmware as a bios instead of kernel
Hi,
On 8/15/19 11:31 PM, Alistair Francis wrote:
> Signed-off-by: Alistair Francis
> ---
> meta/conf/machine/include/riscv/qemuriscv.inc | 2 +-
> meta/conf/machine/qemuriscv64.conf| 2 --
> 2 files changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/meta/conf/machine/include/riscv/qemuriscv.inc
> b/meta/conf/machine/include/riscv/qemuriscv.inc
> index 797a27660d..2ebd0a01f2 100644
> --- a/meta/conf/machine/include/riscv/qemuriscv.inc
> +++ b/meta/conf/machine/include/riscv/qemuriscv.inc
> @@ -28,7 +28,7 @@ UBOOT_ENTRYPOINT_riscv64 = "0x8020"
> QB_KERNEL_CMDLINE_APPEND = "earlycon=sbi"
> QB_MEM = "-m 512"
> QB_MACHINE = "-machine virt"
> -QB_DEFAULT_KERNEL = "fw_jump.elf"
> +QB_DEFAULT_BIOS = "fw_jump.elf"
> QB_TAP_OPT = "-netdev tap,id=net0,ifname=@TAP@,script=no,downscript=no"
> QB_NETWORK_DEVICE = "-device virtio-net-device,netdev=net0,mac=@MAC@"
> QB_ROOTFS_OPT = "-drive id=disk0,file=@ROOTFS@,if=none,format=raw -device
> virtio-blk-device,drive=disk0"
> diff --git a/meta/conf/machine/qemuriscv64.conf
> b/meta/conf/machine/qemuriscv64.conf
> index dba8f09e93..99b48b309b 100644
> --- a/meta/conf/machine/qemuriscv64.conf
> +++ b/meta/conf/machine/qemuriscv64.conf
> @@ -4,8 +4,6 @@
>
> require conf/machine/include/riscv/qemuriscv.inc
>
> -QB_OPT_APPEND += "-show-cursor -monitor null -device
> loader,file=${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE},addr=0x8020"
> -
Was it intentional to remove these lines aswell ? I can't tell from the
commit message.
/Jacob
> EXTRA_IMAGEDEPENDS += "u-boot"
> UBOOT_MACHINE = "qemu-riscv64_defconfig"
> UBOOT_ELF = "u-boot"
>
[mikrodidakt]
Jacob Kroon • +46 46325040
mikrodidakt.se • Skiffervägen 48, SE-224 78 LUND, Sweden
Consultans since 1980 • SW, HW, Embedded Systems, Linux
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [warrior][PATCH] bitbake.conf: add git-lfs to HOSTTOOLS_NONFATAL
On 8/15/19 2:31 PM, Andre McCurdy wrote: > On Thu, Aug 15, 2019 at 2:09 PM Richard Purdie > wrote: >> On Thu, 2019-08-15 at 09:23 +0200, Martin Jansa wrote: >>> NAK >>> >>> Yes, the first part was merged in warrior and is correct. >>> >>> But this second part isn't good (you don't want git-lfs to sometimes >>> work and sometimes fail) and that's why it was rejected for master >>> and _shouldn't_ be merged to warrior. If you have recipes which need >>> git-lfs, then add it to normal HOSTTOOLS in your builds to make sure >>> it's always present when needed. >> I don't like the patch but it did merge to master. >> >> Building a git-lfs-native is a nightmare due to all its dependencies (I >> think its go based?) and there wasn't really any other way to sort it. > Upstream provides generic binaries for at least x86, x86-64 and ARM64: > > https://github.com/git-lfs/git-lfs/releases > > https://github.com/git-lfs/git-lfs/releases/download/v2.8.0/git-lfs-linux-386-v2.8.0.tar.gz > > https://github.com/git-lfs/git-lfs/releases/download/v2.8.0/git-lfs-linux-amd64-v2.8.0.tar.gz > > https://github.com/git-lfs/git-lfs/releases/download/v2.8.0/git-lfs-linux-arm64-v2.8.0.tar.gz > > Would just downloading and installing the official upstream binaries be so > bad? making a big change like this seems to be a no-go for a stable branch. - armin > >> Having recipe specific hosttools would be ideal but we don't have that. >> >> Cheers, >> >> Richard >> >> -- >> ___ >> 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
[OE-core] [PATCH 1/1] target-sdk-provides-dummy: extend packages for multilib case
If we have installed some lib32 package which depends on perl/bash,
then populating sdk for that image would fail with the following error.
Error:
Problem: package lib32-libxml-namespacesupport-perl-1.12-r0.corei7_32
requires lib32-perl, but none of the providers can be installed
package target-sdk-provides-dummy-1.0-r0.sdk_provides_dummy_target
conflicts with /usr/bin/perl provided by lib32-perl-5.30.0-r0.corei7_32
package target-sdk-provides-dummy-1.0-r0.sdk_provides_dummy_target
conflicts with libperl.so.5 provided by lib32-perl-5.30.0-r0.corei7_32
This could be produced by the following steps:
1. IMAGE_INSTALL_append = " lib32-valgrind"
2. bitbake core-image-minimal -c populate_sdk
We need to extend all packages in DUMMYPROVIDES to avoid such problems.
Signed-off-by: Chen Qi
---
meta/recipes-core/meta/target-sdk-provides-dummy.bb | 12
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/meta/recipes-core/meta/target-sdk-provides-dummy.bb
b/meta/recipes-core/meta/target-sdk-provides-dummy.bb
index c33cb80..87b8bfa 100644
--- a/meta/recipes-core/meta/target-sdk-provides-dummy.bb
+++ b/meta/recipes-core/meta/target-sdk-provides-dummy.bb
@@ -1,6 +1,6 @@
DUMMYARCH = "sdk-provides-dummy-target"
-DUMMYPROVIDES = "\
+DUMMYPROVIDES_PACKAGES = "\
busybox \
busybox-dev \
busybox-src \
@@ -42,15 +42,19 @@ DUMMYPROVIDES = "\
perl-module-threads \
perl-module-warnings \
perl-module-warnings-register \
+pkgconfig \
+pkgconfig-dev \
+pkgconfig-src \
+"
+
+DUMMYPROVIDES = "\
+${@' '.join([multilib_pkg_extend(d, pkg) for pkg in
d.getVar('DUMMYPROVIDES_PACKAGES').split()])} \
/bin/sh \
/bin/bash \
/usr/bin/env \
/usr/bin/perl \
libperl.so.5 \
libperl.so.5()(64bit) \
-pkgconfig \
-pkgconfig-dev \
-pkgconfig-src \
"
require dummy-sdk-package.inc
--
1.9.1
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 0/1] target-sdk-provides-dummy: extend packages for multilib case
*** BLURB HERE *** The following changes since commit 5f0d31ce4653f7a76a5226fa379a285ceca19d63: bitbake: runqueue: Ensure data is handled correctly (2019-08-15 13:32:06 +0100) are available in the git repository at: git://git.pokylinux.org/poky-contrib ChenQi/dummy-multilib http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=ChenQi/dummy-multilib Chen Qi (1): target-sdk-provides-dummy: extend packages for multilib case meta/recipes-core/meta/target-sdk-provides-dummy.bb | 12 1 file changed, 8 insertions(+), 4 deletions(-) -- 1.9.1 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] dbus: disable test-bus
From: Changqing Li test-bus take long time to finish, sometimes longer than ptest-runner's timeout limit 300s, so skipped it for now [YOCTO #13409] Signed-off-by: Changqing Li --- meta/recipes-core/dbus/dbus/run-ptest | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/meta/recipes-core/dbus/dbus/run-ptest b/meta/recipes-core/dbus/dbus/run-ptest index cf2e68f..48535e1 100755 --- a/meta/recipes-core/dbus/dbus/run-ptest +++ b/meta/recipes-core/dbus/dbus/run-ptest @@ -21,7 +21,8 @@ do #these programs are used by testcase test-bus, don't run here if [ $i = "test/test-service" ] \ || [ $i = "test/test-shell-service" ] \ -|| [ $i = "test/test-segfault" ] +|| [ $i = "test/test-segfault" ] \ +|| [ $i = "test/test-bus" ] then continue fi -- 2.7.4 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] Long delays with latest bitbake (was: [PATCH 1/7] insane.bbclass: in file-rdeps do not look into RDEPENDS recursively)
On Thu, 2019-08-15 at 14:56 +0100, richard.pur...@linuxfoundation.org wrote: > On Thu, 2019-08-15 at 14:56 +0200, Alexander Kanavin wrote: > What is really odd is this on both traces: > >524436 405.1020.001 405.2660.001 > /home/alexander/development/poky/bitbake/lib/bb/cooker.py:264(notific > ations) > > What that means is that cooker recieved notification of 524436 file > changes whilst it was parsing/preparing runqueue. > > I would be very interested to understand which files its being > notified > of changes to as I suspect there is something that shouldn't be > there. This is a bit of a false lead. At least locally I found them to be profiles of the individual tasks being written out which is only triggered on profiled builds. We should write those files to a different directory to avoid this confusion of the profiles... Cheers, Richard -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/3] qemu: Upgrade to version 4.1
Signed-off-by: Alistair Francis
---
meta/conf/distro/include/tcmode-default.inc | 2 +-
meta/recipes-devtools/qemu/qemu-native.inc| 4 +-
...u-native_4.0.0.bb => qemu-native_4.1.0.bb} | 0
...e_4.0.0.bb => qemu-system-native_4.1.0.bb} | 2 +-
meta/recipes-devtools/qemu/qemu.inc | 20 +-
...emu-Add-missing-wacom-HID-descriptor.patch | 10 +-
...test-which-runs-all-unit-test-cases-.patch | 6 +-
...n-environment-space-to-boot-loader-q.patch | 4 +-
.../qemu/0004-qemu-disable-Valgrind.patch | 6 +-
...-searched-during-user-mode-emulation.patch | 146
...d.bfd-fix-cflags-and-set-some-envir.patch} | 6 +-
...connect-socket-to-a-spawned-command.patch} | 18 +-
... 0007-apic-fixup-fallthrough-to-PIC.patch} | 6 +-
...ebkitgtk-hangs-on-32-bit-x86-target.patch} | 6 +-
...-fix-mmap-munmap-mprotect-mremap-sh.patch} | 58 +--
...-libcap-header-issue-on-some-distro.patch} | 0
...messages-when-qemi_cpu_kick_thread-.patch} | 2 +-
...et-arm-Fix-vector-operation-segfault.patch | 66
...o-handle-variably-sized-SIOCGSTAMP-w.patch | 339 --
.../qemu/qemu/CVE-2019-12155.patch| 35 --
.../qemu/{qemu_4.0.0.bb => qemu_4.1.0.bb} | 0
21 files changed, 59 insertions(+), 677 deletions(-)
rename meta/recipes-devtools/qemu/{qemu-native_4.0.0.bb =>
qemu-native_4.1.0.bb} (100%)
rename meta/recipes-devtools/qemu/{qemu-system-native_4.0.0.bb =>
qemu-system-native_4.1.0.bb} (99%)
delete mode 100644
meta/recipes-devtools/qemu/qemu/0005-qemu-Limit-paths-searched-during-user-mode-emulation.patch
rename
meta/recipes-devtools/qemu/qemu/{0006-qemu-native-set-ld.bfd-fix-cflags-and-set-some-envir.patch
=> 0005-qemu-native-set-ld.bfd-fix-cflags-and-set-some-envir.patch} (82%)
rename
meta/recipes-devtools/qemu/qemu/{0007-chardev-connect-socket-to-a-spawned-command.patch
=> 0006-chardev-connect-socket-to-a-spawned-command.patch} (93%)
rename
meta/recipes-devtools/qemu/qemu/{0008-apic-fixup-fallthrough-to-PIC.patch =>
0007-apic-fixup-fallthrough-to-PIC.patch} (90%)
rename
meta/recipes-devtools/qemu/qemu/{0009-linux-user-Fix-webkitgtk-hangs-on-32-bit-x86-target.patch
=> 0008-linux-user-Fix-webkitgtk-hangs-on-32-bit-x86-target.patch} (90%)
rename
meta/recipes-devtools/qemu/qemu/{0010-Revert-linux-user-fix-mmap-munmap-mprotect-mremap-sh.patch
=> 0009-Revert-linux-user-fix-mmap-munmap-mprotect-mremap-sh.patch} (63%)
rename
meta/recipes-devtools/qemu/qemu/{0011-fix-libcap-header-issue-on-some-distro.patch
=> 0010-fix-libcap-header-issue-on-some-distro.patch} (100%)
rename
meta/recipes-devtools/qemu/qemu/{0012-cpus.c-Add-error-messages-when-qemi_cpu_kick_thread-.patch
=> 0011-cpus.c-Add-error-messages-when-qemi_cpu_kick_thread-.patch} (97%)
delete mode 100644
meta/recipes-devtools/qemu/qemu/0013-target-arm-Fix-vector-operation-segfault.patch
delete mode 100644
meta/recipes-devtools/qemu/qemu/0014-linux-user-fix-to-handle-variably-sized-SIOCGSTAMP-w.patch
delete mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2019-12155.patch
rename meta/recipes-devtools/qemu/{qemu_4.0.0.bb => qemu_4.1.0.bb} (100%)
diff --git a/meta/conf/distro/include/tcmode-default.inc
b/meta/conf/distro/include/tcmode-default.inc
index 1966dbd521..c89b8e012d 100644
--- a/meta/conf/distro/include/tcmode-default.inc
+++ b/meta/conf/distro/include/tcmode-default.inc
@@ -24,7 +24,7 @@ BINUVERSION ?= "2.32%"
GDBVERSION ?= "8.3%"
GLIBCVERSION ?= "2.30%"
LINUXLIBCVERSION ?= "5.0%"
-QEMUVERSION ?= "4.0%"
+QEMUVERSION ?= "4.1%"
GOVERSION ?= "1.12%"
# This can not use wildcards like 8.0.% since it is also used in mesa to denote
# llvm version being used, so always bump it with llvm recipe version bump
diff --git a/meta/recipes-devtools/qemu/qemu-native.inc
b/meta/recipes-devtools/qemu/qemu-native.inc
index c04297cad0..69c2c43e6b 100644
--- a/meta/recipes-devtools/qemu/qemu-native.inc
+++ b/meta/recipes-devtools/qemu/qemu-native.inc
@@ -3,8 +3,8 @@ inherit native
require qemu.inc
SRC_URI_append = " \
-file://0011-fix-libcap-header-issue-on-some-distro.patch \
-
file://0012-cpus.c-Add-error-messages-when-qemi_cpu_kick_thread-.patch \
+file://0010-fix-libcap-header-issue-on-some-distro.patch \
+
file://0011-cpus.c-Add-error-messages-when-qemi_cpu_kick_thread-.patch \
"
EXTRA_OEMAKE_append = " LD='${LD}' AR='${AR}' OBJCOPY='${OBJCOPY}'
LDFLAGS='${LDFLAGS}'"
diff --git a/meta/recipes-devtools/qemu/qemu-native_4.0.0.bb
b/meta/recipes-devtools/qemu/qemu-native_4.1.0.bb
similarity index 100%
rename from meta/recipes-devtools/qemu/qemu-native_4.0.0.bb
rename to meta/recipes-devtools/qemu/qemu-native_4.1.0.bb
diff --git a/meta/recipes-devtools/qemu/qemu-system-native_4.0.0.bb
b/meta/recipes-devtools/qemu/qemu-system-native_4.1.0.bb
similarity index 99%
rename from meta/recipes-devtools/qemu/qemu-system-native_4.0.0.bb
rename to meta/recipes-devtools/qemu/qemu-system-native_4.1.0.bb
index 964dcee5
[OE-core] [PATCH 2/3] scripts/runqemu: Add support for the BIOS variable
Add support for specifying a BIOS the same way that the KERNEL variable
is specified. This includes specifying a QB_DEFAULT_BIOS variable.
Signed-off-by: Alistair Francis
---
scripts/runqemu | 53 +++--
1 file changed, 29 insertions(+), 24 deletions(-)
diff --git a/scripts/runqemu b/scripts/runqemu
index df3c8aad08..e9b83737cb 100755
--- a/scripts/runqemu
+++ b/scripts/runqemu
@@ -59,6 +59,7 @@ def print_usage():
Usage: you can run this script with any valid combination
of the following environment variables (in any order):
KERNEL - the kernel image file to use
+ BIOS - the bios image file to use
ROOTFS - the rootfs image file or nfsroot directory to use
DEVICE_TREE - the device tree blob to use
MACHINE - the machine name (optional, autodetected from KERNEL filename if
unspecified)
@@ -77,8 +78,6 @@ of the following environment variables (in any order):
audio - enable audio
[*/]ovmf* - OVMF firmware file or base name for booting with UEFI
tcpserial= - specify tcp serial port number
- biosdir= - specify custom bios dir
- biosfilename= - specify bios filename
qemuparams= - specify custom parameters to QEMU
bootparams= - specify custom kernel parameters during boot
help, -h, --help: print this text
@@ -129,6 +128,7 @@ class BaseConfig(object):
self.env_vars = ('MACHINE',
'ROOTFS',
'KERNEL',
+'BIOS',
'DEVICE_TREE',
'DEPLOY_DIR_IMAGE',
'OE_TMPDIR',
@@ -155,6 +155,7 @@ class BaseConfig(object):
self.qemuboot = ''
self.qbconfload = False
self.kernel = ''
+self.bios = ''
self.kernel_cmdline = ''
self.kernel_cmdline_script = ''
self.bootparams = ''
@@ -171,7 +172,6 @@ class BaseConfig(object):
self.saved_stty = ''
self.audio_enabled = False
self.tcpserial_portnum = ''
-self.custombiosdir = ''
self.taplock = ''
self.taplock_descriptor = None
self.portlocks = {}
@@ -480,10 +480,6 @@ class BaseConfig(object):
self.qemu_opt_script += ' -vnc :0'
elif arg.startswith('tcpserial='):
self.tcpserial_portnum = '%s' % arg[len('tcpserial='):]
-elif arg.startswith('biosdir='):
-self.custombiosdir = arg[len('biosdir='):]
-elif arg.startswith('biosfilename='):
-self.qemu_opt_script += ' -bios %s' %
arg[len('biosfilename='):]
elif arg.startswith('qemuparams='):
self.qemuparams = ' %s' % arg[len('qemuparams='):]
elif arg.startswith('bootparams='):
@@ -725,25 +721,30 @@ class BaseConfig(object):
if not os.path.exists(self.dtb):
raise RunQemuError('DTB not found: %s, %s or %s' % cmds)
-def check_biosdir(self):
-"""Check custombiosdir"""
-if not self.custombiosdir:
+def check_bios(self):
+"""Check and set bios"""
+
+# See if the user supplied a BIOS option
+if self.get('BIOS'):
+self.bios = self.get('BIOS')
+
+# QB_DEFAULT_BIOS is always a full file path
+bios_name = os.path.basename(self.get('QB_DEFAULT_BIOS'))
+
+# The user didn't want a bios to be loaded
+if (bios_name == "" or bios_name == "none") and not self.bios:
return
-biosdir = ""
-biosdir_native = "%s/%s" % (self.get('STAGING_DIR_NATIVE'),
self.custombiosdir)
-biosdir_host = "%s/%s" % (self.get('STAGING_DIR_HOST'),
self.custombiosdir)
-for i in (self.custombiosdir, biosdir_native, biosdir_host):
-if os.path.isdir(i):
-biosdir = i
-break
+if not self.bios:
+deploy_dir_image = self.get('DEPLOY_DIR_IMAGE')
+self.bios = "%s/%s" % (deploy_dir_image, bios_name)
+
+if not self.bios:
+raise RunQemuError('BIOS not found: %s' % bios_match_name)
+
+if not os.path.exists(self.bios):
+raise RunQemuError("KERNEL %s not found" % self.bios)
-if biosdir:
-logger.debug("Assuming biosdir is: %s" % biosdir)
-self.qemu_opt_script += ' -L %s' % biosdir
-else:
-logger.error("Custom BIOS directory not found. Tried: %s, %s, and
%s" % (self.custombiosdir, biosdir_native, biosdir_host))
-raise RunQemuError("Invalid custombiosdir: %s" %
self.custombiosdir)
def check_mem(self):
"""
@@ -811,7 +812,7 @@ class BaseConfig(object):
self.check_ovmf()
self.check_kernel()
self.check_dtb()
-self.check_biosdir()
+self.check_bios()
self.check_mem()
self.check_tcpserial()
@@ -923,6 +924,8 @@ class BaseConfig(object):
logger.info('Continuing with the following para
[OE-core] [PATCH 3/3] qemuriscv64: Specify the firmware as a bios instead of kernel
Signed-off-by: Alistair Francis
---
meta/conf/machine/include/riscv/qemuriscv.inc | 2 +-
meta/conf/machine/qemuriscv64.conf| 2 --
2 files changed, 1 insertion(+), 3 deletions(-)
diff --git a/meta/conf/machine/include/riscv/qemuriscv.inc
b/meta/conf/machine/include/riscv/qemuriscv.inc
index 797a27660d..2ebd0a01f2 100644
--- a/meta/conf/machine/include/riscv/qemuriscv.inc
+++ b/meta/conf/machine/include/riscv/qemuriscv.inc
@@ -28,7 +28,7 @@ UBOOT_ENTRYPOINT_riscv64 = "0x8020"
QB_KERNEL_CMDLINE_APPEND = "earlycon=sbi"
QB_MEM = "-m 512"
QB_MACHINE = "-machine virt"
-QB_DEFAULT_KERNEL = "fw_jump.elf"
+QB_DEFAULT_BIOS = "fw_jump.elf"
QB_TAP_OPT = "-netdev tap,id=net0,ifname=@TAP@,script=no,downscript=no"
QB_NETWORK_DEVICE = "-device virtio-net-device,netdev=net0,mac=@MAC@"
QB_ROOTFS_OPT = "-drive id=disk0,file=@ROOTFS@,if=none,format=raw -device
virtio-blk-device,drive=disk0"
diff --git a/meta/conf/machine/qemuriscv64.conf
b/meta/conf/machine/qemuriscv64.conf
index dba8f09e93..99b48b309b 100644
--- a/meta/conf/machine/qemuriscv64.conf
+++ b/meta/conf/machine/qemuriscv64.conf
@@ -4,8 +4,6 @@
require conf/machine/include/riscv/qemuriscv.inc
-QB_OPT_APPEND += "-show-cursor -monitor null -device
loader,file=${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE},addr=0x8020"
-
EXTRA_IMAGEDEPENDS += "u-boot"
UBOOT_MACHINE = "qemu-riscv64_defconfig"
UBOOT_ELF = "u-boot"
--
2.22.0
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [warrior][PATCH] bitbake.conf: add git-lfs to HOSTTOOLS_NONFATAL
On Thu, Aug 15, 2019 at 2:09 PM Richard Purdie wrote: > On Thu, 2019-08-15 at 09:23 +0200, Martin Jansa wrote: > > NAK > > > > Yes, the first part was merged in warrior and is correct. > > > > But this second part isn't good (you don't want git-lfs to sometimes > > work and sometimes fail) and that's why it was rejected for master > > and _shouldn't_ be merged to warrior. If you have recipes which need > > git-lfs, then add it to normal HOSTTOOLS in your builds to make sure > > it's always present when needed. > > I don't like the patch but it did merge to master. > > Building a git-lfs-native is a nightmare due to all its dependencies (I > think its go based?) and there wasn't really any other way to sort it. Upstream provides generic binaries for at least x86, x86-64 and ARM64: https://github.com/git-lfs/git-lfs/releases https://github.com/git-lfs/git-lfs/releases/download/v2.8.0/git-lfs-linux-386-v2.8.0.tar.gz https://github.com/git-lfs/git-lfs/releases/download/v2.8.0/git-lfs-linux-amd64-v2.8.0.tar.gz https://github.com/git-lfs/git-lfs/releases/download/v2.8.0/git-lfs-linux-arm64-v2.8.0.tar.gz Would just downloading and installing the official upstream binaries be so bad? > Having recipe specific hosttools would be ideal but we don't have that. > > Cheers, > > Richard > > -- > ___ > 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] [warrior][PATCH] bitbake.conf: add git-lfs to HOSTTOOLS_NONFATAL
On Thu, 2019-08-15 at 09:23 +0200, Martin Jansa wrote: > NAK > > Yes, the first part was merged in warrior and is correct. > > But this second part isn't good (you don't want git-lfs to sometimes > work and sometimes fail) and that's why it was rejected for master > and _shouldn't_ be merged to warrior. If you have recipes which need > git-lfs, then add it to normal HOSTTOOLS in your builds to make sure > it's always present when needed. I don't like the patch but it did merge to master. Building a git-lfs-native is a nightmare due to all its dependencies (I think its go based?) and there wasn't really any other way to sort it. Having recipe specific hosttools would be ideal but we don't have that. Cheers, Richard -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 2/3] qemuboot.bbclass: increase the default RAM to 512M
Maybe we should drop x11 from default DISTRO_FEATURES :) Will resolve the memory consumption and image size. Well the image size isn't much different, I was just surprised to see libx11 being included even in core-image-minimal (because systemd -> dbus -> libx11: "dbus.do_package" -> "libx11.do_packagedata"), but in the end the difference in ext4 was only 2MB (61MB/63MB), caused by following 4 packages: libx11-6 core2-64 1:1.6.8-r0.0 libxau6 core2-64 1:1.0.9-r0.15 libxcb1 core2-64 1.13.1-r0.15 libxdmcp6 core2-64 1:1.1.3-r0.15 so I guess embedded no longer have neither small ram nor small flash. On Thu, Aug 15, 2019 at 6:20 PM Alexander Kanavin wrote: > On Wed, 14 Aug 2019 at 18:42, Richard Purdie < > richard.pur...@linuxfoundation.org> wrote: > >> I'm not sure I agree with this. >> >> We are meant to work on embedded systems and 256MB should be enough to >> let us bring up X under qemu. >> >> I'm fine with some sdk/ptest images having more memory, that makes >> sense but 256MB not allowing X under qemu seems rather poor. >> > > I poked a bit more at this. The main difference between vmware emulated > hardware and std emulated hardware is that X uses the standard 2D > framebuffer interface for the former, and the full 3D stack for the latter > (via use of glamor: https://www.freedesktop.org/wiki/Software/Glamor/). > The 3D stack (mesa and friends) is what causes the memory usage to swell. > > It is possible to disable this behaviour and enforce framebuffer usage > (see 'man modesetting'), and I have verified that the RAM usage drops to > similar levels as vmware, but that is not the upstream default; they have > more or less obsoleted 2D drivers and are defaulting to 3D rendering > nowadays. I'd rather follow that. > > Alex > > > -- > ___ > 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
[OE-core] [PATCH V2] gcc-9: Upgrade to 9.2
BugFix only release see [1] for details
[1]
https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=9.2
Signed-off-by: Khem Raj
---
v2: Drop 0006-gcc-disable-MASK_RELAX_PIC_CALLS-bit.patch which was not
needed
meta/conf/distro/include/maintainers.inc | 2 +-
.../gcc/{gcc-9.1.inc => gcc-9.2.inc} | 73 ++-
...0001-gcc-4.3.1-ARCH_FLAGS_FOR_TARGET.patch | 14 ++--
.../0002-gcc-poison-system-directories.patch | 26 +++
...-gcc-4.3.3-SYSROOT_CFLAGS_FOR_TARGET.patch | 10 +--
.../0004-64-bit-multilib-hack.patch | 6 +-
.../0005-optional-libstdc.patch | 20 ++---
.../0006-COLLECT_GCC_OPTIONS.patch} | 8 +-
...s.h-in-B-instead-of-S-and-t-oe-in-B.patch} | 12 +--
.../0008-fortran-cross-compile-hack.patch}| 12 +--
.../0009-cpp-honor-sysroot.patch} | 8 +-
.../0010-MIPS64-Default-to-N64-ABI.patch} | 10 +--
...MIC_LINKER-and-UCLIBC_DYNAMIC_LINKE.patch} | 26 ++-
...cc-Fix-argument-list-too-long-error.patch} | 10 +--
.../0013-Disable-sdt.patch} | 20 ++---
.../0014-libtool.patch} | 6 +-
...-fix-v4bx-to-linker-to-support-EABI.patch} | 6 +-
...config-files-from-B-instead-of-usin.patch} | 10 +--
...r-from-.la-which-usually-points-to-.patch} | 6 +-
.../0018-export-CPP.patch}| 8 +-
...-target-gcc-headers-can-be-included.patch} | 12 +--
...ld-with-disable-dependency-tracking.patch} | 6 +-
...-directory-during-relink-if-inst_pr.patch} | 6 +-
...R-replacement-instead-of-hardcoding.patch} | 8 +-
...3-aarch64-Add-support-for-musl-ldso.patch} | 8 +-
...fix-libcc1-s-install-path-and-rpath.patch} | 6 +-
...e-sysroot-support-for-nativesdk-gcc.patch} | 8 +-
...root-gcc-version-specific-dirs-with.patch} | 8 +-
...us-_FOR_BUILD-and-related-variables.patch} | 16 ++--
...28-nios2-Define-MUSL_DYNAMIC_LINKER.patch} | 6 +-
...-to-link-commandline-for-musl-targe.patch} | 14 ++--
...gcc-Add-knob-to-use-ldbl-128-on-ppc.patch} | 6 +-
...sing-LDFLAGS-not-just-SHLIB_LDFLAGS.patch} | 6 +-
...s-for-__cpu_indicator_init-instead-.patch} | 10 +--
.../0033-sync-gcc-stddef.h-with-musl.patch} | 6 +-
...fault-in-precompiled-header-generat.patch} | 6 +-
.../0035-Fix-for-testsuite-failure.patch} | 8 +-
...e-introduce-spe-commandline-options.patch} | 8 +-
...adian_9.1.bb => gcc-cross-canadian_9.2.bb} | 0
.../{gcc-cross_9.1.bb => gcc-cross_9.2.bb}| 0
...cc-crosssdk_9.1.bb => gcc-crosssdk_9.2.bb} | 0
...{gcc-runtime_9.1.bb => gcc-runtime_9.2.bb} | 0
...anitizers_9.1.bb => gcc-sanitizers_9.2.bb} | 0
.../{gcc-source_9.1.bb => gcc-source_9.2.bb} | 0
.../gcc/{gcc_9.1.bb => gcc_9.2.bb}| 0
...c-initial_9.1.bb => libgcc-initial_9.2.bb} | 0
.../gcc/{libgcc_9.1.bb => libgcc_9.2.bb} | 0
...{libgfortran_9.1.bb => libgfortran_9.2.bb} | 0
48 files changed, 214 insertions(+), 227 deletions(-)
rename meta/recipes-devtools/gcc/{gcc-9.1.inc => gcc-9.2.inc} (56%)
rename meta/recipes-devtools/gcc/{gcc-9.1 =>
gcc-9.2}/0001-gcc-4.3.1-ARCH_FLAGS_FOR_TARGET.patch (79%)
rename meta/recipes-devtools/gcc/{gcc-9.1 =>
gcc-9.2}/0002-gcc-poison-system-directories.patch (91%)
rename meta/recipes-devtools/gcc/{gcc-9.1 =>
gcc-9.2}/0003-gcc-4.3.3-SYSROOT_CFLAGS_FOR_TARGET.patch (93%)
rename meta/recipes-devtools/gcc/{gcc-9.1 =>
gcc-9.2}/0004-64-bit-multilib-hack.patch (98%)
rename meta/recipes-devtools/gcc/{gcc-9.1 =>
gcc-9.2}/0005-optional-libstdc.patch (91%)
rename meta/recipes-devtools/gcc/{gcc-9.1/0007-COLLECT_GCC_OPTIONS.patch =>
gcc-9.2/0006-COLLECT_GCC_OPTIONS.patch} (85%)
rename
meta/recipes-devtools/gcc/{gcc-9.1/0008-Use-the-defaults.h-in-B-instead-of-S-and-t-oe-in-B.patch
=> gcc-9.2/0007-Use-the-defaults.h-in-B-instead-of-S-and-t-oe-in-B.patch} (92%)
rename
meta/recipes-devtools/gcc/{gcc-9.1/0009-fortran-cross-compile-hack.patch =>
gcc-9.2/0008-fortran-cross-compile-hack.patch} (84%)
rename meta/recipes-devtools/gcc/{gcc-9.1/0010-cpp-honor-sysroot.patch =>
gcc-9.2/0009-cpp-honor-sysroot.patch} (92%)
rename meta/recipes-devtools/gcc/{gcc-9.1/0011-MIPS64-Default-to-N64-ABI.patch
=> gcc-9.2/0010-MIPS64-Default-to-N64-ABI.patch} (85%)
rename
meta/recipes-devtools/gcc/{gcc-9.1/0012-Define-GLIBC_DYNAMIC_LINKER-and-UCLIBC_DYNAMIC_LINKE.patch
=> gcc-9.2/0011-Define-GLIBC_DYNAMIC_LINKER-and-UCLIBC_DYNAMIC_LINKE.patch}
(92%)
rename
meta/recipes-devtools/gcc/{gcc-9.1/0013-gcc-Fix-argument-list-too-long-error.patch
=> gcc-9.2/0012-gcc-Fix-argument-list-too-long-error.patch} (85%)
rename meta/recipes-devtools/gcc/{gcc-9.1/0014-Disable-sdt.patch =>
gcc-9.2/0013-Disable-sdt.patch} (89%)
rename meta/recipes-devtools/gcc/{gcc-9.1/0015-libtool.patch =>
gcc-9.2/0014-libtool.patch} (91%)
rename
meta/recipes-devtools/gcc/{gcc-9.1/0016-gcc-armv4-pass-fix-v4bx-to-linker-to-support-EABI.patch
=> gcc-9.2/0015-gcc-armv4-pass-fix-v4bx-to-linker-to-support-EABI.patch} (91%)
rename
Re: [OE-core] [PATCH] gcc-9: Upgrade to 9.2
On 8/15/19 11:22 AM, Adrian Bunk wrote: On Thu, Aug 15, 2019 at 12:17:13AM -0700, Khem Raj wrote: ... create mode 100644 meta/recipes-devtools/gcc/gcc-9.2/0006-gcc-disable-MASK_RELAX_PIC_CALLS-bit.patch ... That would be a partial revert of a change in master. thanks, that missed to be removed from local rebased trees. I will send a v2. cu Adrian -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] gcc-9: Upgrade to 9.2
On Thu, Aug 15, 2019 at 12:17:13AM -0700, Khem Raj wrote: >... > create mode 100644 > meta/recipes-devtools/gcc/gcc-9.2/0006-gcc-disable-MASK_RELAX_PIC_CALLS-bit.patch >... That would be a partial revert of a change in master. 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
[OE-core] ✗ patchtest: failure for bitbake: runqueue: Ensure data is handled correctly
== Series Details == Series: bitbake: runqueue: Ensure data is handled correctly Revision: 1 URL : https://patchwork.openembedded.org/series/19294/ 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 sent to the wrong mailing list or some patches from the series correspond to different mailing lists [test_target_mailing_list] Suggested fixSend the series again to the correct mailing list (ML) Suggested ML bitbake-de...@lists.openembedded.org [http://git.openembedded.org/bitbake/] Patch's path:bitbake/lib/bb/runqueue.py * 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 6b36db8365) 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 2/3] qemuboot.bbclass: increase the default RAM to 512M
On Wed, 14 Aug 2019 at 18:42, Richard Purdie < richard.pur...@linuxfoundation.org> wrote: > I'm not sure I agree with this. > > We are meant to work on embedded systems and 256MB should be enough to > let us bring up X under qemu. > > I'm fine with some sdk/ptest images having more memory, that makes > sense but 256MB not allowing X under qemu seems rather poor. > I poked a bit more at this. The main difference between vmware emulated hardware and std emulated hardware is that X uses the standard 2D framebuffer interface for the former, and the full 3D stack for the latter (via use of glamor: https://www.freedesktop.org/wiki/Software/Glamor/). The 3D stack (mesa and friends) is what causes the memory usage to swell. It is possible to disable this behaviour and enforce framebuffer usage (see 'man modesetting'), and I have verified that the RAM usage drops to similar levels as vmware, but that is not the upstream default; they have more or less obsoleted 2D drivers and are defaulting to 3D rendering nowadays. I'd rather follow that. Alex -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] python3-scons: update to 3.1.1
Signed-off-by: Oleksandr Kravchuk
---
...n3-scons-native_3.1.0.bb => python3-scons-native_3.1.1.bb} | 0
.../python/{python3-scons_3.1.0.bb => python3-scons_3.1.1.bb} | 4 ++--
2 files changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-devtools/python/{python3-scons-native_3.1.0.bb =>
python3-scons-native_3.1.1.bb} (100%)
rename meta/recipes-devtools/python/{python3-scons_3.1.0.bb =>
python3-scons_3.1.1.bb} (82%)
diff --git a/meta/recipes-devtools/python/python3-scons-native_3.1.0.bb
b/meta/recipes-devtools/python/python3-scons-native_3.1.1.bb
similarity index 100%
rename from meta/recipes-devtools/python/python3-scons-native_3.1.0.bb
rename to meta/recipes-devtools/python/python3-scons-native_3.1.1.bb
diff --git a/meta/recipes-devtools/python/python3-scons_3.1.0.bb
b/meta/recipes-devtools/python/python3-scons_3.1.1.bb
similarity index 82%
rename from meta/recipes-devtools/python/python3-scons_3.1.0.bb
rename to meta/recipes-devtools/python/python3-scons_3.1.1.bb
index f1545dade6..0c7aaeaeee 100644
--- a/meta/recipes-devtools/python/python3-scons_3.1.0.bb
+++ b/meta/recipes-devtools/python/python3-scons_3.1.1.bb
@@ -4,8 +4,8 @@ LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=37bb53a08e6beaea0c90e7821d731284"
SRC_URI = "${SOURCEFORGE_MIRROR}/scons/scons-${PV}.tar.gz"
-SRC_URI[md5sum] = "e2fe9d16f81b0285b969238af4b552ff"
-SRC_URI[sha256sum] =
"f3f548d738d4a2179123ecd744271ec413b2d55735ea7625a59b1b59e6cd132f"
+SRC_URI[md5sum] = "35b2a3993313bbedd221d4d5758fd2fd"
+SRC_URI[sha256sum] =
"4cea417fdd7499a36f407923d03b4b7000b0f9e8fd7b31b316b9ce7eba9143a5"
S = "${WORKDIR}/scons-${PV}"
--
2.17.1
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] bitbake: runqueue: Ensure data is handled correctly
From: Richard Purdie This doesn't appear to have ill effects right now but there is a correctness issue which this so fix it. (Bitbake rev: a5e084a266f63c2fd370122327615e49beaeb94e) Signed-off-by: Richard Purdie --- bitbake/lib/bb/runqueue.py | 2 ++ 1 file changed, 2 insertions(+) diff --git a/bitbake/lib/bb/runqueue.py b/bitbake/lib/bb/runqueue.py index 53031740bd..4e64ddfdad 100644 --- a/bitbake/lib/bb/runqueue.py +++ b/bitbake/lib/bb/runqueue.py @@ -2306,6 +2306,8 @@ class RunQueueExecute: self.scenequeue_notcovered.remove(tid) if tid in self.scenequeue_covered: self.scenequeue_covered.remove(tid) +if tid in self.scenequeue_notneeded: +self.scenequeue_notneeded.remove(tid) (mc, fn, taskname, taskfn) = split_tid_mcfn(tid) self.sqdata.stamps[tid] = bb.build.stampfile(taskname + "_setscene", self.rqdata.dataCaches[mc], taskfn, noextra=True) -- 2.17.1 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] python-setuptools: update to 41.1.0
Signed-off-by: Oleksandr Kravchuk
---
meta/recipes-devtools/python/python-setuptools.inc| 4 ++--
...ython-setuptools_41.0.1.bb => python-setuptools_41.1.0.bb} | 0
...hon3-setuptools_41.0.1.bb => python3-setuptools_41.1.0.bb} | 0
3 files changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-devtools/python/{python-setuptools_41.0.1.bb =>
python-setuptools_41.1.0.bb} (100%)
rename meta/recipes-devtools/python/{python3-setuptools_41.0.1.bb =>
python3-setuptools_41.1.0.bb} (100%)
diff --git a/meta/recipes-devtools/python/python-setuptools.inc
b/meta/recipes-devtools/python/python-setuptools.inc
index f49e078697..c806589dba 100644
--- a/meta/recipes-devtools/python/python-setuptools.inc
+++ b/meta/recipes-devtools/python/python-setuptools.inc
@@ -10,8 +10,8 @@ inherit pypi
SRC_URI_append_class-native = "
file://0001-conditionally-do-not-fetch-code-by-easy_install.patch"
-SRC_URI[md5sum] = "6404ca798bb9a9073aff3b91b2df35c8"
-SRC_URI[sha256sum] =
"a222d126f5471598053c9a77f4b5d4f26eaa1f150ad6e01dcf1a42e185d05613"
+SRC_URI[md5sum] = "f26bbb3201c42ef37fb8d184cb85234d"
+SRC_URI[sha256sum] =
"c519b84c299911fd94ef47e3de4fe678c254aefc5cdf8a9b12e4cdc8cc3744a8"
DEPENDS += "${PYTHON_PN}"
diff --git a/meta/recipes-devtools/python/python-setuptools_41.0.1.bb
b/meta/recipes-devtools/python/python-setuptools_41.1.0.bb
similarity index 100%
rename from meta/recipes-devtools/python/python-setuptools_41.0.1.bb
rename to meta/recipes-devtools/python/python-setuptools_41.1.0.bb
diff --git a/meta/recipes-devtools/python/python3-setuptools_41.0.1.bb
b/meta/recipes-devtools/python/python3-setuptools_41.1.0.bb
similarity index 100%
rename from meta/recipes-devtools/python/python3-setuptools_41.0.1.bb
rename to meta/recipes-devtools/python/python3-setuptools_41.1.0.bb
--
2.17.1
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] ffmpeg: update to 4.2
Signed-off-by: Oleksandr Kravchuk
---
.../ffmpeg/{ffmpeg_4.1.4.bb => ffmpeg_4.2.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-multimedia/ffmpeg/{ffmpeg_4.1.4.bb => ffmpeg_4.2.bb} (97%)
diff --git a/meta/recipes-multimedia/ffmpeg/ffmpeg_4.1.4.bb
b/meta/recipes-multimedia/ffmpeg/ffmpeg_4.2.bb
similarity index 97%
rename from meta/recipes-multimedia/ffmpeg/ffmpeg_4.1.4.bb
rename to meta/recipes-multimedia/ffmpeg/ffmpeg_4.2.bb
index 884973d237..2d69d8bd72 100644
--- a/meta/recipes-multimedia/ffmpeg/ffmpeg_4.1.4.bb
+++ b/meta/recipes-multimedia/ffmpeg/ffmpeg_4.2.bb
@@ -26,8 +26,8 @@ LIC_FILES_CHKSUM =
"file://COPYING.GPLv2;md5=b234ee4d69f5fce4486a80fdaf4a4263 \
SRC_URI = "https://www.ffmpeg.org/releases/${BP}.tar.xz \
file://mips64_cpu_detection.patch \
"
-SRC_URI[md5sum] = "5307931aeb7aaee5e1509d9996040661"
-SRC_URI[sha256sum] =
"f1f049a82fcfbf156564e73a3935d7e750891fab2abf302e735104fd4050a7e1"
+SRC_URI[md5sum] = "fb33a9110251873002869664686b2a3f"
+SRC_URI[sha256sum] =
"023f10831a97ad93d798f53a3640e55cd564abfeba807ecbe8524dac4fedecd5"
# Build fails when thumb is enabled:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=7717
ARM_INSTRUCTION_SET_armv4 = "arm"
--
2.17.1
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] Long delays with latest bitbake (was: [PATCH 1/7] insane.bbclass: in file-rdeps do not look into RDEPENDS recursively)
On Tue, Aug 13, 2019 at 10:04:08AM +0100, Richard Purdie wrote:
> On Mon, 2019-08-12 at 20:26 +, Peter Kjellerstedt wrote:
> > Comparing that build to a corresponding do-nothing build with Thud,
> > the time difference matches those three minutes where I have no idea
> > what bitbake is doing now that it didn’t need to do before…
> >
> > Hopefully these time degradations can be solved, because the current
> > state of bitbake is barely usable. We also need to look into possible
> > ways to improve the cooker output when it is running the setscene
> > tasks so it makes some kind of sense again.
>
> We talked on irc and you pointed at the commit things started to go
> wrong. Just to summarise things for the benefit of the list, this is
> some quick testing I did:
>
> "bitbake -p; time bitbake core-image-minimal -n"
>
> 30.0s 6c7c0cefd34067311144a1d4c01986fe0a4aef26
> 30.6s a0d941c787cf3ef030d190903279d311bc05d752
> 40.3s 7df31ff36892c2f9c65326b06b4c70
> 42.2s a0542ed3ff700eca35f9195f743c9e28bcd50f3e
> 45.4s 9983b07fffd19082abded7c3f15cc77d306dd69c
> 76.9s master-next
I know I'm late to the party, but it took really long for the test to finish..
I'm not using poky, so reproduce this testing on our builds I've used
bitbake revisions matching with poky revision RP was testing:
+ oe-core 18cdc087fd5da30e2b31f3d4e81b153cd36ca844 for older bitbake, because
current master isn't compatible with old bitbake (bb.data_smart.ExpansionError:
Failure expanding variable OE_IMPORTED[:=], expression was ${@oe_import(d)}
which triggered exception AttributeError: module 'bb.siggen' has no attribute
'SignatureGeneratorUniHashMixIn')
and oe-core 23db236a054ee7a989cdbbcb42ad5c6eefd4a6ae for newer bitbake (to
possibly eliminate impact of metadata changes)
tested on 72core (Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz) with 380GB RAM
nothing in TMPDIR/SSTATE_DIR, no SSTATE_MIRRO, no Hash Equivalence Server
configured
on a build with few more layers:
Parsing of 3238 .bb files complete (0 cached, 3238 parsed). 7632 targets, 1927
skipped, 54 masked, 0 errors.
but first doing just core-image-minimal like RP did:
timepokybitbake
oe-core
2m8.191s6c7c0cefd34067311144a1d4c01986fe0a4aef26
18d4a31fdcec1f0e5d2199d6142f0ce833fca1a7
18cdc087fd5da30e2b31f3d4e81b153cd36ca844
N/A a0d941c787cf3ef030d190903279d311bc05d752doesn't exist
in poky/poky-contrib 18cdc087fd5da30e2b31f3d4e81b153cd36ca844
2m17.053s 7df31ff36892c2f9c65326b06b4c70
1f630fdf0260db08541d3ca9f25f852931c19905
18cdc087fd5da30e2b31f3d4e81b153cd36ca844
2m18.515s a0542ed3ff700eca35f9195f743c9e28bcd50f3e
f43778c2d19e70d4befd483b06aaf247fc65c799
23db236a054ee7a989cdbbcb42ad5c6eefd4a6ae
2m22.220s 9983b07fffd19082abded7c3f15cc77d306dd69c
8c26b451f22193ef1c544e2017cc84515566c1b8
2m38.185s master-next
fbcb89dc3dbabfc80310e9a4ebe72d919300a32e
cache.py:446: ResourceWarning: unclosed
value = pickled.load()
started showing with this revision
2m17.991s master-next + fixups
f7cd14f90463957b3e4be6d3876def98b78f1424
2m9.651smaster-next + "Holding off tasks %s" out
now world
253m36.637s 7df31ff36892c2f9c65326b06b4c70
1f630fdf0260db08541d3ca9f25f852931c19905
18cdc087fd5da30e2b31f3d4e81b153cd36ca844
174m13.324s a0542ed3ff700eca35f9195f743c9e28bcd50f3e
f43778c2d19e70d4befd483b06aaf247fc65c799
23db236a054ee7a989cdbbcb42ad5c6eefd4a6ae
this is time when killed at "NOTE: Executing Tasks" without showing any
progress on the tasks (unlike other tests) and only one bitbake process is
running
633m27.475s master-next
fbcb89dc3dbabfc80310e9a4ebe72d919300a32e
this is time when killed at (1417 from 71749) - running very slowly unlike
other bitbake revisions where the task number changes relatively quickly -
about 10 tasks per second
89m13.992s master-next + "Holding off tasks %s" out
89m59.201s master-next updated today
85fe627fdb6510f0942917964386fad9d8c479c8
Interestingly old 1f630fdf0260db08541d3ca9f25f852931c19905 is 3 times
slower than recent master-next.
I'll send -P output next.
>
> So basically the original changes showed a 25% hit but the performance
> of -next is dire.
>
> This is with no hash equiv server configured.
>
> It will vary depending on the target used (numbers with -sato for the
> above would be interesting for comparision) and how much was or is in
> sstate, they type of sstate mirror configured and so on.
>
> I really need to focus on getting the new code functioning correctly
> before we attempt to optimise but if nobody tests the new code due to
> performance problems we have a different issue. We also have a scaling
> pro
Re: [OE-core] Long delays with latest bitbake (was: [PATCH 1/7] insane.bbclass: in file-rdeps do not look into RDEPENDS recursively)
On Thu, 2019-08-15 at 14:56 +0200, Alexander Kanavin wrote: > On Wed, 14 Aug 2019 at 23:25, > wrote: > > Right, it still definitely needs work. Its a balancing act between > > sorting out the execution bugs in the code and figuring out the > > performance problem. > > > > If anyone wants to experiment, the way I'd debug this is to run the > > before and after cases with the -P option to bitbake. If you want > > to > > exit early just make the code return where it prints "Executing > > tasks" > > or whatever makes sense as Ctrl+C won't write the profile data. > > > > You want the profile.log.processed file. > > > > So save that file with the "before" commit, then save it afterwards > > and > > look at those files and see where its spending more time. > > > > If someone generates those two files I'll happily take a look, I'm > > kind > > of used to reading them. There are four sets of output in there, > > same > > data but different sorting/types, each has its uses. > > And here they are (with task spinning included this time): > http://sensi.org/~ak/tmp/profile.log.processed.before > http://sensi.org/~ak/tmp/profile.log.processed.after > > Hope you find it useful! How many tasks are in that build? What is really odd is this on both traces: 524436 405.1020.001 405.2660.001 /home/alexander/development/poky/bitbake/lib/bb/cooker.py:264(notifications) What that means is that cooker recieved notification of 524436 file changes whilst it was parsing/preparing runqueue. I would be very interested to understand which files its being notified of changes to as I suspect there is something that shouldn't be there. If we fixed that, it would take 406s off the 1800s for starters in both cases. I don't see that locally in my trace, my build layout may be different. Other things of note: Time in next_buildable_task went up 338 -> 440s (probably through the set manipulation e.g. method 'difference' of 'set' objects) New function update_holdofftasks() took 173s build_taskdepdata is also eating lots of time suddenly. So yes, useful, thanks. You may want to add some debug to that nofitications() function in cooker and see which files are changing though. Cheers, Richard -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] Long delays with latest bitbake (was: [PATCH 1/7] insane.bbclass: in file-rdeps do not look into RDEPENDS recursively)
On Wed, 14 Aug 2019 at 23:25, wrote: > Right, it still definitely needs work. Its a balancing act between > sorting out the execution bugs in the code and figuring out the > performance problem. > > If anyone wants to experiment, the way I'd debug this is to run the > before and after cases with the -P option to bitbake. If you want to > exit early just make the code return where it prints "Executing tasks" > or whatever makes sense as Ctrl+C won't write the profile data. > > You want the profile.log.processed file. > > So save that file with the "before" commit, then save it afterwards and > look at those files and see where its spending more time. > > If someone generates those two files I'll happily take a look, I'm kind > of used to reading them. There are four sets of output in there, same > data but different sorting/types, each has its uses. > And here they are (with task spinning included this time): http://sensi.org/~ak/tmp/profile.log.processed.before http://sensi.org/~ak/tmp/profile.log.processed.after Hope you find it useful! Alex -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [warrior][PATCH] boost: Fix build and enable context and coroutines on aarch64
Like for ARM bjam need some hints about the ABI to properly build on
aarch64. While at it also enable context and coroutine as these are
supported on aarch64.
Signed-off-by: Alban Bedel
---
meta/recipes-support/boost/boost.inc | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-support/boost/boost.inc
b/meta/recipes-support/boost/boost.inc
index 9be3717fd6..c2e2cbb352 100644
--- a/meta/recipes-support/boost/boost.inc
+++ b/meta/recipes-support/boost/boost.inc
@@ -33,6 +33,7 @@ BOOST_LIBS_append_x86 = " context coroutine"
BOOST_LIBS_append_x86-64 = " context coroutine"
BOOST_LIBS_append_powerpc = " context coroutine"
BOOST_LIBS_append_arm = " context coroutine"
+BOOST_LIBS_append_aarch64 = " context coroutine"
# need consistent settings for native builds (x86 override not applied for
native)
BOOST_LIBS_remove_class-native = " context coroutine"
# does not compile
@@ -151,6 +152,7 @@ BJAM_OPTS_append_x86-x32 = " abi=x32 address-model=64"
# cross compiling for arm fails to detect abi, so provide some help
BJAM_OPTS_append_arm = " abi=aapcs architecture=arm"
+BJAM_OPTS_append_aarch64 = " abi=aapcs address-model=64 architecture=arm"
do_configure() {
cp -f ${S}/boost/config/platform/linux.hpp
${S}/boost/config/platform/linux-gnueabi.hpp
--
2.20.1
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] webkitgtk: disable gold on mipsn32
From: Kai Kang Using gold on mipsn32 still fails. It fails to run $ bitbake webkitgtk -c configure with configuration: MACHINE ?= "qemumips" DEFAULTTUNE = "mips64-n32" Signed-off-by: Kai Kang --- meta/recipes-sato/webkit/webkitgtk_2.24.3.bb | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/recipes-sato/webkit/webkitgtk_2.24.3.bb b/meta/recipes-sato/webkit/webkitgtk_2.24.3.bb index c42c3de69f..0e5ee5ba00 100644 --- a/meta/recipes-sato/webkit/webkitgtk_2.24.3.bb +++ b/meta/recipes-sato/webkit/webkitgtk_2.24.3.bb @@ -88,6 +88,7 @@ EXTRA_OECMAKE_append_armv5 = " -DENABLE_JIT=OFF " EXTRA_OECMAKE_append_armv6 = " -DENABLE_JIT=OFF " EXTRA_OECMAKE_append_armv4 = " -DENABLE_JIT=OFF " +EXTRA_OECMAKE_append_mipsarchn32 = " -DUSE_LD_GOLD=OFF " EXTRA_OECMAKE_append_powerpc = " -DUSE_LD_GOLD=OFF " # JIT not supported on MIPS either -- 2.20.0 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [warrior][PATCH] bitbake.conf: add git-lfs to HOSTTOOLS_NONFATAL
On 8/15/19 3:23 PM, Martin Jansa wrote: NAK Yes, the first part was merged in warrior and is correct. But this second part isn't good (you don't want git-lfs to sometimes work and sometimes fail) and that's why it was rejected for master and _shouldn't_ be merged to warrior. If you have recipes which need git-lfs, then add it to normal HOSTTOOLS in your builds to make sure it's always present when needed. Noted. Thanks. -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [warrior][PATCH] bitbake.conf: add git-lfs to HOSTTOOLS_NONFATAL
NAK
Yes, the first part was merged in warrior and is correct.
But this second part isn't good (you don't want git-lfs to sometimes work
and sometimes fail) and that's why it was rejected for master and
_shouldn't_ be merged to warrior. If you have recipes which need git-lfs,
then add it to normal HOSTTOOLS in your builds to make sure it's always
present when needed.
On Thu, Aug 15, 2019 at 9:01 AM Saini, Naveen Kumar <
naveen.kumar.sa...@intel.com> wrote:
> The corresponding first patch of this patch series already merged in
> Warrior
>
>
> https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/bitbake/lib?h=warrior&id=6e3a4d7926296380da23536c29af35d5702e02fb
>
> So this patch should also go in warrior.
>
>
> On 8/15/19 2:53 PM, Naveen Saini wrote:
> > This provides git large file storage (lfs) extension.
> >
> > Include git-lfs conditionally. If git-lfs is present on host and repo
> > has lfs pointers, then git-lfs will be used. If git-lfs is not present
> > on host, it will be ignored.
> >
> > [YOCTO #13198]
> >
> > (From OE-Core rev: 2968ad8514721ec06e67aaf3fd5ec7b247b3431d)
> >
> > Signed-off-by: Naveen Saini
> > Signed-off-by: Richard Purdie
> > ---
> > meta/conf/bitbake.conf | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> > index c996301a8b..c5313ccd19 100644
> > --- a/meta/conf/bitbake.conf
> > +++ b/meta/conf/bitbake.conf
> > @@ -514,6 +514,9 @@ HOSTTOOLS_NONFATAL += "bzr"
> > # Used by ssh fetcher
> > HOSTTOOLS_NONFATAL += "scp"
> >
> > +# Link to git-lfs if present
> > +HOSTTOOLS_NONFATAL += "git-lfs"
> > +
> > CCACHE ??= ""
> >
> > TOOLCHAIN_OPTIONS = " --sysroot=${STAGING_DIR_TARGET}"
> >
> --
> ___
> 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
[OE-core] [PATCH] gcc-9: Upgrade to 9.2
BugFix only release see [1] for details
[1]
https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=9.2
Signed-off-by: Khem Raj
---
meta/conf/distro/include/maintainers.inc | 2 +-
.../gcc/{gcc-9.1.inc => gcc-9.2.inc} | 11 ++--
...0001-gcc-4.3.1-ARCH_FLAGS_FOR_TARGET.patch | 12 ++--
.../0002-gcc-poison-system-directories.patch | 24
...-gcc-4.3.3-SYSROOT_CFLAGS_FOR_TARGET.patch | 8 +--
.../0004-64-bit-multilib-hack.patch | 4 +-
.../0005-optional-libstdc.patch | 18 +++---
...gcc-disable-MASK_RELAX_PIC_CALLS-bit.patch | 59 +++
.../0007-COLLECT_GCC_OPTIONS.patch| 6 +-
...ts.h-in-B-instead-of-S-and-t-oe-in-B.patch | 10 ++--
.../0009-fortran-cross-compile-hack.patch | 10 ++--
.../0010-cpp-honor-sysroot.patch | 6 +-
.../0011-MIPS64-Default-to-N64-ABI.patch | 8 +--
...AMIC_LINKER-and-UCLIBC_DYNAMIC_LINKE.patch | 24 ++--
...gcc-Fix-argument-list-too-long-error.patch | 8 +--
.../0014-Disable-sdt.patch| 18 +++---
.../{gcc-9.1 => gcc-9.2}/0015-libtool.patch | 4 +-
...s-fix-v4bx-to-linker-to-support-EABI.patch | 4 +-
...-config-files-from-B-instead-of-usin.patch | 8 +--
...ir-from-.la-which-usually-points-to-.patch | 4 +-
.../0019-export-CPP.patch | 6 +-
...e-target-gcc-headers-can-be-included.patch | 10 ++--
...ild-with-disable-dependency-tracking.patch | 4 +-
...t-directory-during-relink-if-inst_pr.patch | 4 +-
...IR-replacement-instead-of-hardcoding.patch | 6 +-
...24-aarch64-Add-support-for-musl-ldso.patch | 6 +-
...-fix-libcc1-s-install-path-and-rpath.patch | 4 +-
...le-sysroot-support-for-nativesdk-gcc.patch | 6 +-
...sroot-gcc-version-specific-dirs-with.patch | 6 +-
...ous-_FOR_BUILD-and-related-variables.patch | 14 ++---
...029-nios2-Define-MUSL_DYNAMIC_LINKER.patch | 4 +-
...d-to-link-commandline-for-musl-targe.patch | 12 ++--
...bgcc-Add-knob-to-use-ldbl-128-on-ppc.patch | 4 +-
...using-LDFLAGS-not-just-SHLIB_LDFLAGS.patch | 4 +-
...as-for-__cpu_indicator_init-instead-.patch | 8 +--
.../0034-sync-gcc-stddef.h-with-musl.patch| 4 +-
...-fault-in-precompiled-header-generat.patch | 4 +-
.../0036-Fix-for-testsuite-failure.patch | 6 +-
...Re-introduce-spe-commandline-options.patch | 6 +-
...adian_9.1.bb => gcc-cross-canadian_9.2.bb} | 0
.../{gcc-cross_9.1.bb => gcc-cross_9.2.bb}| 0
...cc-crosssdk_9.1.bb => gcc-crosssdk_9.2.bb} | 0
...{gcc-runtime_9.1.bb => gcc-runtime_9.2.bb} | 0
...anitizers_9.1.bb => gcc-sanitizers_9.2.bb} | 0
.../{gcc-source_9.1.bb => gcc-source_9.2.bb} | 0
.../gcc/{gcc_9.1.bb => gcc_9.2.bb}| 0
...c-initial_9.1.bb => libgcc-initial_9.2.bb} | 0
.../gcc/{libgcc_9.1.bb => libgcc_9.2.bb} | 0
...{libgfortran_9.1.bb => libgfortran_9.2.bb} | 0
49 files changed, 206 insertions(+), 160 deletions(-)
rename meta/recipes-devtools/gcc/{gcc-9.1.inc => gcc-9.2.inc} (94%)
rename meta/recipes-devtools/gcc/{gcc-9.1 =>
gcc-9.2}/0001-gcc-4.3.1-ARCH_FLAGS_FOR_TARGET.patch (84%)
rename meta/recipes-devtools/gcc/{gcc-9.1 =>
gcc-9.2}/0002-gcc-poison-system-directories.patch (92%)
rename meta/recipes-devtools/gcc/{gcc-9.1 =>
gcc-9.2}/0003-gcc-4.3.3-SYSROOT_CFLAGS_FOR_TARGET.patch (95%)
rename meta/recipes-devtools/gcc/{gcc-9.1 =>
gcc-9.2}/0004-64-bit-multilib-hack.patch (98%)
rename meta/recipes-devtools/gcc/{gcc-9.1 =>
gcc-9.2}/0005-optional-libstdc.patch (92%)
create mode 100644
meta/recipes-devtools/gcc/gcc-9.2/0006-gcc-disable-MASK_RELAX_PIC_CALLS-bit.patch
rename meta/recipes-devtools/gcc/{gcc-9.1 =>
gcc-9.2}/0007-COLLECT_GCC_OPTIONS.patch (89%)
rename meta/recipes-devtools/gcc/{gcc-9.1 =>
gcc-9.2}/0008-Use-the-defaults.h-in-B-instead-of-S-and-t-oe-in-B.patch (94%)
rename meta/recipes-devtools/gcc/{gcc-9.1 =>
gcc-9.2}/0009-fortran-cross-compile-hack.patch (88%)
rename meta/recipes-devtools/gcc/{gcc-9.1 =>
gcc-9.2}/0010-cpp-honor-sysroot.patch (94%)
rename meta/recipes-devtools/gcc/{gcc-9.1 =>
gcc-9.2}/0011-MIPS64-Default-to-N64-ABI.patch (88%)
rename meta/recipes-devtools/gcc/{gcc-9.1 =>
gcc-9.2}/0012-Define-GLIBC_DYNAMIC_LINKER-and-UCLIBC_DYNAMIC_LINKE.patch (92%)
rename meta/recipes-devtools/gcc/{gcc-9.1 =>
gcc-9.2}/0013-gcc-Fix-argument-list-too-long-error.patch (89%)
rename meta/recipes-devtools/gcc/{gcc-9.1 => gcc-9.2}/0014-Disable-sdt.patch
(90%)
rename meta/recipes-devtools/gcc/{gcc-9.1 => gcc-9.2}/0015-libtool.patch (94%)
rename meta/recipes-devtools/gcc/{gcc-9.1 =>
gcc-9.2}/0016-gcc-armv4-pass-fix-v4bx-to-linker-to-support-EABI.patch (95%)
rename meta/recipes-devtools/gcc/{gcc-9.1 =>
gcc-9.2}/0017-Use-the-multilib-config-files-from-B-instead-of-usin.patch (94%)
rename meta/recipes-devtools/gcc/{gcc-9.1 =>
gcc-9.2}/0018-Avoid-using-libdir-from-.la-which-usually-points-to-.patch (91%)
rename meta/recipes-devtools/gcc/{gcc-9.1 => gcc-9.2}/0019-export-CPP.patch
(95%)
rename
Re: [OE-core] [warrior][PATCH] bitbake.conf: add git-lfs to HOSTTOOLS_NONFATAL
The corresponding first patch of this patch series already merged in
Warrior
https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/bitbake/lib?h=warrior&id=6e3a4d7926296380da23536c29af35d5702e02fb
So this patch should also go in warrior.
On 8/15/19 2:53 PM, Naveen Saini wrote:
This provides git large file storage (lfs) extension.
Include git-lfs conditionally. If git-lfs is present on host and repo
has lfs pointers, then git-lfs will be used. If git-lfs is not present
on host, it will be ignored.
[YOCTO #13198]
(From OE-Core rev: 2968ad8514721ec06e67aaf3fd5ec7b247b3431d)
Signed-off-by: Naveen Saini
Signed-off-by: Richard Purdie
---
meta/conf/bitbake.conf | 3 +++
1 file changed, 3 insertions(+)
diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index c996301a8b..c5313ccd19 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -514,6 +514,9 @@ HOSTTOOLS_NONFATAL += "bzr"
# Used by ssh fetcher
HOSTTOOLS_NONFATAL += "scp"
+# Link to git-lfs if present
+HOSTTOOLS_NONFATAL += "git-lfs"
+
CCACHE ??= ""
TOOLCHAIN_OPTIONS = " --sysroot=${STAGING_DIR_TARGET}"
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
