[OE-core] [PATCH 8/8] staging.bbclass: extend_recipe_sysroot: fix multilib manifest

Fixed: MACHINE = "qemux86-64" MULTILIBS = "multilib:lib32" DEFAULTTUNE_virtclass-multilib-lib32 = "x86" $ bitbake -cpopulate_sdk_ext [snip] Exception: subprocess.CalledProcessError: Command 'sed -e [snip]' [snip] Subprocess output: [snip] sed: can't read

[OE-core] [PATCH 7/8] populate_sdk_ext.bbclass: remove the try...finally

The "sdkbasepath + '/conf/local.conf.bak" doesn't exist when "oe.copy_buildsystem.check_sstate_task_list()" fails, then os.replace() would raise FileNotFoundError, which overcomes the real error. Keep the error status makes debug easier, so remove the try..finally. Signed-off-by: Robert Yang

[OE-core] [PATCH 6/8] toolchain-scripts.bbclass: only install all MULTILIB_VARIANTS for image

Install all MULTILIB_VARIANTS to sysroot and pack them only makes sense to image recipe, so limit it to image recipe only, and it can fix: MACHINE = "qemux86-64" require conf/multilib.conf MULTILIBS = "multilib:lib32" DEFAULTTUNE_virtclass-multilib-lib32 = "core2-32" $ bitbake

[OE-core] [PATCH 5/8] multilib.bbclass: extend allarch recipes

This can fix do_rootfs and depends chaos when multilib, for example ca-certificates is an allarch recipe: MACHINE = "qemux86-64" require conf/multilib.conf MULTILIBS = "multilib:lib32" DEFAULTTUNE_virtclass-multilib-lib32 = "core2-32" IMAGE_INSTALL_append = " ca-certificates" $ bitbake

[OE-core] [PATCH 4/8] package_manager.py: reverse archs correctly

It had reversed all the archs, which mixed multilib and common archs, e.g.: "all any noarch x86_64 core2-64 qemux86_64 x86 i586 core2-32" After reversed: "core2-32 i586 x86 qemux86_64 core2-64 x86_64 noarch any all" The core2-32 has a higher priority than core2-64 after reversed which is

[OE-core] [PATCH 3/8] staging.bbclass: print searched manifest when not found

The old warning was: WARNING: lib32-wrlinux-image-glibc-small-1.0-r1 do_prepare_recipe_sysroot: Manifest /path/to/tmp/sstate-control/manifest-allarch-lib32-qemuwrapper-cross.populate_sysroot not found? The message wasn't clear enough, it searched a few manifests, but only reported the last

[OE-core] [PATCH 1/8] populate_sdk_ext.bbclass: fix for multilib

Fixed: MACHINE = "qemux86-64" require conf/multilib.conf MULTILIBS = "multilib:lib32" DEFAULTTUNE_virtclass-multilib-lib32 = "x86" $ bitbake -cpopulate_sdk_ext $ bitbake -ctestsdkext [snip] Standard Output: /bin/sh: 1: i686-wrsmllib32-linux-gcc: not found [snip] It was failed because no lib32

[OE-core] [PATCH 2/8] staging.bbclass: staging_populate_sysroot_dir(): fix for multilib

Fixed: MACHINE = "qemux86-64" require conf/multilib.conf MULTILIBS = "multilib:lib32" DEFAULTTUNE_virtclass-multilib-lib32 = "x86" $ bitbake core-image-sato lib32-core-image-sato $ bitbake build-sysroots All lib32 manifests which had been built should be installed, but only a few such as

[OE-core] [PATCH 0/8] [rebase and resend] fixes for multilib

Hi RP, The multilib is still broken without these patches, I'd like to add oeqa test cases for them after it works. // Robert The following changes since commit 073d8d001033471d7fe44f52212c72a6c3541313: dbus-test-ptest: improve reproducibility (2018-03-12 15:05:58 -0700) are available in

[OE-core] [PATCH 3/3] python3: Fix purelib install and runtime paths

oe-core commit: 45afadf0b6 fixed the pip problem with purelib for python2, even though the the patch stated it was for python3. This patch addresses the purelib problem for python3. If you install the package python3-pip you will have a pip3 binary where you can see the problem on the device

[OE-core] [PATCH 2/3] boost: Fix link problems with caffe and Movidius SDK

When using an image built with the Yocto Project which has a compiler and all the required libraries, projects such as caffe for the Movidius SDK which use python3 and boost fail to build because they look for libboost_python.so. The error that cmake returns doesn't even point to the fact that

[OE-core] [PATCH 1/3] alsa-lib: Add an RPROVIDES for alsa-lib

There are a number of other recipes outside oe-core that depend on alsa-lib and the rpm4 dependencies resolve sometimes to include alsa-lib and the packages in the other layers fail to install because the dependency cannot be resolved, despite the fact that libasound is installed. The simple is

Re: [OE-core] [PATCH V2] insane.bbclass: skip opening symlinks in package_qa_check_libdir

Ping //Yi 在 2018年03月07日 08:15, Yi Zhao 写道: If the library is installed in a non-standard location and don't set INSANE_SKIP, e.g. libfoo.so is installed in /usr/local/lib. The package_qa_check_libdir will cause a traceback because it will try to open the .so link in package-dev to check if

Re: [OE-core] [rocko][PATCH 0/8] Backports for rocko

Hi Juro, Khem, A rocko-next build including this patchset had a couple gcc-sanitizers do_compile failures: https://autobuilder.yocto.io/builders/nightly-x86-64-lsb/builds/865/steps/BuildImages/logs/stdio

Re: [OE-core] [PATCH] x86-base.inc: use xf86-video-modesettings as default xserver

It looks like Fedora doesn't patch the -intel driver anymore, instead they patch xserver to fiddle with the defaults. https://src.fedoraproject.org/rpms/xorg-x11-server/c/ee515e44b07e37689abf48cf2fffb41578f3bc1d?branch=master Given the comment and commit description, I'm guessing that list is

[OE-core] [PATCH] kernel.bbclass: avoid duplicates in KERNEL_IMAGETYPE_FOR_MAKE

Currently if KERNEL_IMAGETYPES contains both vmlinux and vmlinux.gz, KERNEL_IMAGETYPE_FOR_MAKE will end up containing two copies of vmlinux, which will result in two calls to "make vmlinux" from kernel_do_compile(). Avoid duplicating vmlinux in KERNEL_IMAGETYPE_FOR_MAKE plus some minor

Re: [OE-core] [oe-core][PATCH 1/7] eudev: fix file conflict when multilib enabled

On 3/12/18 11:55 AM, Alexander Kanavin wrote: > On 03/12/2018 08:38 PM, Mark Hatle wrote: >> In this case, because the user specifically asked for BOTH 32-bit and 64-bit >> development components to be installed onto the target for their application >> development. (This isn't a theoretical

Re: [OE-core] [oe-core][PATCH 1/7] eudev: fix file conflict when multilib enabled

On 03/12/2018 08:38 PM, Mark Hatle wrote: In this case, because the user specifically asked for BOTH 32-bit and 64-bit development components to be installed onto the target for their application development. (This isn't a theoretical problem, but a specific problem from one of our customers.)

Re: [OE-core] [oe-core][PATCH 1/7] eudev: fix file conflict when multilib enabled

On 3/12/18 3:13 AM, Alexander Kanavin wrote: > On 03/12/2018 11:12 AM, Zhang Xiao wrote: >> Config file udev.pc conflicts between 32 and 64 bit packages. >> Use update-alternatives to add base_libdir as suffix to avoid it. >> -inherit autotools update-rc.d qemu pkgconfig distro_features_check >>

Re: [OE-core] [rocko][PATCH 1/1] go: Upgrade 1.9 to 1.9.4 stable release

On Mon, Mar 12, 2018 at 8:44 AM, Burton, Ross wrote: > Note that stable branch policy is to cherry-pick security fixes unless > they're too complicated/risky to pick (openssl is the notable example here). I strong believe Go should be dealt in same way; it is known to be

Re: [OE-core] [rocko][PATCH 0/1] backport go 1.9.4 update to rocko

On Mon, Mar 12, 2018 at 8:29 AM, Matt Madison wrote: > One of the changes included in this point release update > fixes an issue with the construction of Go's shared runtim > library, so it would be great to backport this to rocko > to fix [YOCTO 12592]. Acked-by: Otavio

Re: [OE-core] [PATCH] core-image-minimal-initramfs: prepare initramfs for NFS boot

Hi. It'd be nice if this was part of initramfs-framework instead. In particular some devices need a bit more than ifconfig & route, e.g. configuration of SoC internal Ethernet switches. As it is, this patch is not very generic, whereas if it was integrated with the initramfs-framework, another

[OE-core] [PATCH 4/4] lib/oe/patch.py: add a warning if patch context was ignored

Ignoring patch context increases the chances of patches being applied incorrectly. Depending on what code is being patched, this can go completely unnoticed and create subtle bugs, sometimes with security implications. Please see here for a specific example:

[OE-core] [PATCH 3/4] oe-selftest: add a test for failing package post-installation scriptlets

The test runs a scriptlet that has an intentionally failing command in the middle and checks for two things: 1) that bitbake does warn the user about the failure 2) that scriptlet execution stops at that point. The test is run for all three package types: rpm, deb, ipk. Signed-off-by: Alexander

[OE-core] [PATCH 2/4] meta/lib/oe/package_manager.py: warn about failing scriptlets for all package types

Previously this was done only for rpm packages; now also ipk/deb scriptlet failures are reported. In the future this will become a hard error, but it can't yet happen due to the legacy 'exit 1' way of deferring scriptlet execution to first boot which needs a deprecation period. Signed-off-by:

[OE-core] [PATCH 1/4] package.bbclass: run pre/post installation/removal scriptlets using sh -e

This allows catching errors in the scriptlets which would otherwise go unnoticed, e.g. this sequence: bogus_command proper_command would work just fine without any visible warnings or errors. This was previously done only for rpm packages; this patch replaces the rpm-specific tweak with

[OE-core] [PATCH 2/2] build-recipe-list: build universe instead of world

Building world means recipes that are excluded from world build for whatever reason get skipped from the manifests, which isn't useful. Instead building universe and pass -k so that the expected dependency failures are not fatal. Signed-off-by: Ross Burton ---

[OE-core] [PATCH 1/2] meta: remove some EXCLUDE_FROM_WORLD assignments

Now that we have recipe-specific-sysroots we don't need to exclude recipes from world builds because they conflict with other recipes, as they'll all be built with their own sysroots. Signed-off-by: Ross Burton --- meta/recipes-connectivity/bluez5/bluez5.inc

[OE-core] [PATCH] iproute2: fix rebuild failures

When rebuilding iproute2, many such instances of the following build failure occur: | make[1]: Entering directory '.../iproute2/4.14.1-r0/iproute2-4.14.1/lib' | Makefile:1: ../config.mk: No such file or directory | make[1]: *** No rule to make target '../config.mk'.

[OE-core] IMPORTANT: do_patch() fuzz warnings and how to deal with them

*Executive summary* do_patch() will shortly start issuing warnings when recipe patches are applied with some of the patch context ignored. This email explains why this is necessary, and how the warnings can be eliminated. *What is patch fuzz?* Patch fuzz is a situation when the patch tool

[OE-core] Yocto Project Status WW11’18

Current Dev Position: YP 2.5 M3 final close out. Next Deadline: YP 2.5 M3 cut off was 2/19/18 *** FEATURE FREEZE for 2.5 has passed *** SWAT lead is currently Cal. SWAT team rotation: Cal -> Armin on March 16, 2018 SWAT team rotation: Armin -> Ross on March 23, 2018

[OE-core] [PATCH] core-image-minimal-initramfs: prepare initramfs for NFS boot

It helps to boot device by mounting rootfs via NFS when network drivers are built as modules. We include modules in core-image-minimal-initramfs image and start kernel with specifying custom rdinit in cmdline: rdinit=/init-nfs.sh NFS and IP parameters should be passed to kernel as usual. For

[OE-core] uninative and recipe parsing

Hi all, When you add several layers, recipe parsing can take a (very) long time. In our case it takes more than a couple minutes [1]. Fortunately it is supposed to happens once, except when you use uninative (poky's default) where it happens twice (the two first times you build). I think this

Re: [OE-core] [rocko][PATCH 1/1] go: Upgrade 1.9 to 1.9.4 stable release

Note that stable branch policy is to cherry-pick security fixes unless they're too complicated/risky to pick (openssl is the notable example here). Ross On 12 March 2018 at 11:29, Matt Madison wrote: > From: Otavio Salvador > > The 1.9.4 fixes a

[OE-core] [PATCH] image_types.bbclass: Rename lz4_legacy to lz4

LZ4 format currently used by the Linux kernel is the 'legacy' format. In order to avoid creating an image that can't be used as a compressed initial ramdisk with Linux kernel, rename lz4_legacy to lz4. [YOCTO #12461] [YOCTO #12149] Signed-off-by: Maxin B. John ---

[OE-core] [rocko][PATCH 1/1] go: Upgrade 1.9 to 1.9.4 stable release

From: Otavio Salvador The 1.9.4 fixes a number of issues in the Go compiler and is important to get in before we start working on 1.10 inclusion. - go1.9.1 (released 2017/10/04) includes two security fixes. - go1.9.2 (released 2017/10/25) includes fixes to the

[OE-core] [rocko][PATCH 0/1] backport go 1.9.4 update to rocko

One of the changes included in this point release update fixes an issue with the construction of Go's shared runtim library, so it would be great to backport this to rocko to fix [YOCTO 12592]. Thanks, -Matt Otavio Salvador (1): go: Upgrade 1.9 to 1.9.4 stable release

Re: [OE-core] [oe-core][PATCH 1/7] eudev: fix file conflict when multilib enabled

On 03/12/2018 11:12 AM, Zhang Xiao wrote: Config file udev.pc conflicts between 32 and 64 bit packages. Use update-alternatives to add base_libdir as suffix to avoid it. -inherit autotools update-rc.d qemu pkgconfig distro_features_check +inherit autotools update-rc.d qemu pkgconfig

[OE-core] ✗ patchtest: failure for pkcs11-helper: 1.11 -> 1.22

== Series Details == Series: pkcs11-helper: 1.11 -> 1.22 Revision: 1 URL : https://patchwork.openembedded.org/series/11358/ 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

[OE-core] [oe][meta-oe][PATCH] pkcs11-helper: 1.11 -> 1.22

Upgrade pkcs11-helper from 1.11 to 1.22. Signed-off-by: Huang Qiyu --- .../pkcs11-helper/{pkcs11-helper_1.11.bb => pkcs11-helper_1.22.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta-oe/recipes-crypto/pkcs11-helper/{pkcs11-helper_1.11.bb

[OE-core] [PATCH 0/1] btrfs-tools: set CLEANBROKEN to 1 to avoid rebuild failure

The following changes since commit 5350ee317740751f2417c1794dd39d3880347dbf: yocto-uninative: Upgrade to 1.8 version with glibc 2.27 (2018-03-11 06:27:02 -0700) are available in the git repository at: git://git.pokylinux.org/poky-contrib ChenQi/btrfs-tools-rebuild

[OE-core] [PATCH 1/1] btrfs-tools: set CLEANBROKEN to 1 to avoid rebuild failure

When rebuilding btrfs-tools, we would sometimes meet the following error. Makefile:43: *** Makefile.inc not generated, please configure first. Set CLEANBROKEN to "1" to solve this problem. Signed-off-by: Chen Qi ---

Re: [OE-core] [PATCH 1/3] systemd: upgrade to 237

On 03/12/2018 04:52 PM, Maxin B. John wrote: Hi, On Mon, Mar 12, 2018 at 04:38:51PM +0800, Chen Qi wrote: Upgrade systemd to 237. Note that this version has dropped autotools support. Very minor nit-picking : Even with this patch, "systemd_237.bb" and "systemd.inc" contains duplicated

[OE-core] [oe-core][PATCH 6/7] xtrans: fix file conflict when multilib enabled

Script file xtrans.pc conflicts between 32 and 64 bit packages. Use update-alternatives to add base_libdir as suffix to avoid it. Signed-off-by: Zhang Xiao --- meta/recipes-graphics/xorg-lib/xtrans_1.3.5.bb | 15 ++- 1 file changed, 14 insertions(+), 1

[OE-core] [oe-core][PATCH 7/7] icu: fix file conflict when multilib enabled

Script icu-config conflicts between 32 and 64 bit packages. Use update-alternatives to add base_libdir as suffix to avoid it. Signed-off-by: Zhang Xiao --- meta/recipes-support/icu/icu.inc | 16 ++-- 1 file changed, 14 insertions(+), 2 deletions(-) diff

[OE-core] [oe-core][PATCH 2/7] python3: fix file conflict when multilib enabled

Config file python3.5m-config conflicts between 32 and 64 bit packages. Use update-alternatives to add base_libdir as suffix to avoid it. Signed-off-by: Zhang Xiao --- meta/recipes-devtools/python/python3_3.5.4.bb | 10 +- 1 file changed, 9 insertions(+), 1

[OE-core] [oe-core][PATCH 5/7] cairo: fix file conflict when multilib enabled

Script file cairo-trace conflict between 32 and 64 bit packages. Use update-alternatives to add base_libdir as suffix to avoid it. Signed-off-by: Zhang Xiao --- meta/recipes-graphics/cairo/cairo_1.14.12.bb | 16 +++- 1 file changed, 15 insertions(+), 1

[OE-core] [oe-core][PATCH 3/7] vala: fix file conflict when multilib enabled

Config file vala-gen-introspect-${SHRT_VER} conflicts between 32 and 64 bit packages. Use update-alternatives to add base_libdir as suffix to avoid it. Signed-off-by: Zhang Xiao --- meta/recipes-devtools/vala/vala.inc | 15 ++- 1 file changed, 14

[OE-core] [oe-core][PATCH 4/7] gobject-introspection: fix file conflict when multilib enabled

Script files conflict between 32 and 64 bit packages: ${bindir}/g-ir-annotation-tool ${bindir}/g-ir-compiler-wrapper ${bindir}/g-ir-scanner ${bindir}/g-ir-scanner-lddwrapper ${bindir}/g-ir-scanner-qemuwrapper ${bindir}/g-ir-scanner-wrapper ${datadir}/gir-1.0/GLib-2.0.gir Use update-alternatives

[OE-core] [oe-core][PATCH 1/7] eudev: fix file conflict when multilib enabled

Config file udev.pc conflicts between 32 and 64 bit packages. Use update-alternatives to add base_libdir as suffix to avoid it. Signed-off-by: Zhang Xiao --- meta/recipes-core/udev/eudev_3.2.5.bb | 17 +++-- 1 file changed, 15 insertions(+), 2 deletions(-)

Re: [OE-core] [PATCH 1/3] systemd: upgrade to 237

Hi, On Mon, Mar 12, 2018 at 04:38:51PM +0800, Chen Qi wrote: > Upgrade systemd to 237. > > Note that this version has dropped autotools support. Very minor nit-picking : Even with this patch, "systemd_237.bb" and "systemd.inc" contains duplicated SRC_URI =

Re: [OE-core] [PATCH 0/3] systemd & systemd-boot: upgrade to 237

Hi Ross, This patchset has been rebased against latest master to resolve conflicts. Best Regards, Chen Qi On 03/12/2018 04:38 PM, Chen Qi wrote: Changes in V2: * Rebase against latest master to resolve conflicts The following changes since commit 5350ee317740751f2417c1794dd39d3880347dbf:

[OE-core] [PATCH 2/3] systemd: fix build failure for qemux86 and qemuppc with musl

Remove the 'fstack-protector' and 'fstack-protector-strong' flags as a workaround to fix the following error when building for qemux86 and qemuppc with musl. undefined reference to `__stack_chk_fail_local' Signed-off-by: Chen Qi ---

[OE-core] [PATCH 3/3] systemd-boot: upgrade to 237

Upgrade systemd-boot to 237. As systemd has dropped autotools support, fix configure and compile failures related to meson. Signed-off-by: Chen Qi --- .../{systemd-boot_234.bb => systemd-boot_237.bb} | 31 ++- ...01-Also-check-i386-i586-and-i686-for-ia32.patch

[OE-core] [PATCH 0/3] systemd & systemd-boot: upgrade to 237

Changes in V2: * Rebase against latest master to resolve conflicts The following changes since commit 5350ee317740751f2417c1794dd39d3880347dbf: yocto-uninative: Upgrade to 1.8 version with glibc 2.27 (2018-03-11 06:27:02 -0700) are available in the git repository at: