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
/path/to/work/qemux86_64-wrs-linux/wrlin
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
---
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 lib32-meta-ide-suppo
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 ca-certifica
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
incorrect.
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 one,
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 t
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 qemux86_
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 the
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 easi
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 thi
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 to
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 i
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
https://autobuilder.yocto.io/builders/nightly-no-x11/builds/853/steps/BuildImages/logs/stdi
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
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 non-functio
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 proble
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.)
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
>> +i
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
good at supporting forwar
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 Salvador
--
Otavio Sal
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 m
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:
https://bugzilla.yoctoproject.org/show
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
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: Al
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
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
---
scripts/distro/build-recipe-list.p
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 | 2 --
meta/recipes
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'. Stop.
*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 ig
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
https://wiki.yoctoproject
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 ex
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 i
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 number of issues in the Go compiler and is impor
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
---
meta/classes/image_types.bbcl
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 compiler,
linker, runtime, do
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
meta/recipes-devtools/go
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 distro_featur
== 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 pro
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 =>
pkcs11-helper_1.22.bb} (95%
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
http://git.pokylinux.or
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
---
meta/recipes-devtools/btrfs-tools/btrfs-tools_4.13.3.bb | 2 ++
1 file chang
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
SRC_U
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 deletion(-)
diff --git a/meta/
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 --git a/meta/recipes-support/
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 deletion(-)
diff --git a/meta
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 deletion(-)
diff --git a/meta/
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 insertions(+), 1 deletion(-)
diff --
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 to
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(-)
diff --git a/meta/recipes-
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 = "git://github.com/systemd/systemd.gi
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:
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
---
...ck-protector-flags-to-workaround-musl-bui.patch | 33
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 | 28 ++
...efi_
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:
git://git.pokylinux.o
55 matches
Mail list logo
