Re: [yocto] [zeus] icu-native-64.2-r0 do_configure: configure failed
On 30/10/2019 06:25, s...@gmx.li wrote: Build of image failed, I got strange and long error messages like: | from distutils.sysconfig import parse_makefile | ModuleNotFoundError: No module named 'distutils.sysconfig' | configure: error: Python failed to run; see above error. a) What goes wrong here and how can this be avoid? distutils.sysconfig is part of the standard Python library. What distribution are you using? It's possible that you've only got a 'minimal' Python installed instead of the full thing. b) How do I found which module is responsible. There is nothing about strace/valgrind mentioned in the log. I just had to build all my additional packets of my image manually to find the triggers for this icu-native. The recipe responsible is icu-native. Something in your build depends on this, such as boost-native maybe. Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [zeus] icu-native-64.2-r0 do_configure: configure failed
I use a poky core-image-minimal with some packages added - as for instance strace and valgrind (for armv7a). Strange - yocto in older versions generates images with valgrind/strace .. without any complaints. So both PC and image-recipe are same, but in Yocto 2.5 and 2.7 it works, in 3.0 not ?!? Sorry I am confused, do you mean python is missing in requested image or at host PC with Ubuntu 1804? If it is missing in image, shouldn't it be included by dependencies automatically? At UbuntuPC python 2.7 is installed: python Python 2.7.15+ (default, Oct 7 2019, 17:39:04) [GCC 7.4.0] on linux2 Regrads Arno -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] NooB: applying new patches to older files, where do I find the older files?
Hello List, First I'm working on a unsupported distro (Manjaro) and try to get an older version (2.7.1) of poky working. I have ask a question before and Ross Burton pointed me in the direction of a patch. Now I'm trying to apply that patch, however the patch is for a newer version of the original files, so I need to make my own patch for the older version of these files. (reason: WARNING: Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.) The patch says: the file to be patch is e.g. /linux-user/syscall.c My question is where can I find the original syscall.c before any patches are applied to it? Just to be complete: I have tried the latest warrior branch and that worked fine. My objective is not just to get it working be also to get a grip on how the system works :-) Thanks, Robert. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-freescale][NXP] Failed to build gstreamer1.0 ith Yocto thud on NXP IMX8MQ
Hi, I'm currently trying to build gstreamer1.0 with Yocto Thud. My host machine is a Debian 9 (stretch) Linux. It always succeeded with previous version of Yocto rocko and sumo. But there with thud I immediately get an Unpack Error I've never experienced before: ERROR: gstreamer1.0-1.14.4.imx-r0 do_unpack: gitsm: submodule unpack failed: UnpackError Unpack failure for URL: 'gitsm://anongit.freedesktop.org/git/gstreamer/common.git;protocol=https;name=common;subpath=common;bareclone=1;nobranch=1'. No up to date source found: clone directory not available or not up to date: /opt/yocto/imx8/fsl-imx8-thud-4.19.35-1.0.0/../../downloads/git2/anongit.freedesktop.org.git.gstreamer.common.git; shallow clone not enabled ERROR: gstreamer1.0-1.14.4.imx-r0 do_unpack: Unpack failure for URL: 'gitsm://anongit.freedesktop.org/git/gstreamer/common.git;protocol=https;name=common;subpath=common;bareclone=1;nobranch=1'. No up to date source found: clone directory not available or not up to date: /opt/yocto/imx8/fsl-imx8-thud-4.19.35-1.0.0/../../downloads/git2/anongit.freedesktop.org.git.gstreamer.common.git; shallow clone not enabled ERROR: gstreamer1.0-1.14.4.imx-r0 do_unpack: Function failed: base_do_unpack ERROR: Logfile of failure stored in: /opt/yocto/imx8/fsl-imx8-thud-4.19.35-1.0.0/build/tmp/work/aarch64-poky-linux/gstreamer1.0/1.14.4.imx-r0/temp/log.do_unpack.27700 ERROR: Task (/opt/yocto/imx8/fsl-imx8-thud-4.19.35-1.0.0/sources/meta-freescale/recipes-multimedia/gstreamer/gstreamer1.0_1.14.imx.bb:do_unpack) failed with exit code '1' I've attached the log.do_unpack file. I tried to clean everything up, but I still get this annoying error and I'm stuck with it for a while now. Any suggestion is really welcome Thanks. Karim log.do_unpack.27700 Description: log.do_unpack.27700 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] QA notification for completed autobuilder build (yocto-2.7.2.rc1)
A build flagged for QA (yocto-2.7.2.rc1) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-2.7.2.rc1 Build hash information: bitbake: 75d6648f232a06b99c54a1e33324a7fc1cd15b38 meta-gplv2: d5d9fc9a4bbd365d6cd6fe4d6a8558f7115c17da meta-intel: ca26bed652722167b2dbe0042cfc2406029e9c6c meta-mingw: 10695afe8cd406844e0d0dd868c11677e07557d4 oecore: 726c3b92298981f5aa2f2449ceeec7b4bf84ed29 poky: d0f73121551dc98f6924cd77952bf9ebf5ef3dd7 This is an automated message from the Yocto Project Autobuilder Git: git://git.yoctoproject.org/yocto-autobuilder2 Email: richard.pur...@linuxfoundation.org -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [zeus] icu-native-64.2-r0 do_configure: configure failed
On 30/10/2019 12:11, Arno Steffens wrote: I use a poky core-image-minimal with some packages added - as for instance strace and valgrind (for armv7a). Strange - yocto in older versions generates images with valgrind/strace .. without any complaints. So both PC and image-recipe are same, but in Yocto 2.5 and 2.7 it works, in 3.0 not ?!? Sorry I am confused, do you mean python is missing in requested image or at host PC with Ubuntu 1804? If it is missing in image, shouldn't it be included by dependencies automatically? At UbuntuPC python 2.7 is installed: python Python 2.7.15+ (default, Oct 7 2019, 17:39:04) [GCC 7.4.0] on linux2 I mean the host, as that's running code using the host python during the build. Try this: $ python3 -m distutils.sysconfig If that does nothing then your Python is working. If it fails then you need to install the full Python 3 on your machine, not just minimal. Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Where is the documentation for things to fix when upgrading poky versions?
Hi all, This is probably a super easy question, but I've been searching half the day and decided it would be faster to ask for help. I know I've seen documentation in one of the manuals that points out major changes in syntax or behavior that will need to be fixed when upgrading the underlying version of poky, but now that I have need of it, I can't seem to find it anywhere. Can anyone point me in the right direction? Thanks! -Sean McKay -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Where is the documentation for things to fix when upgrading poky versions?
Hi Sean On Thursday, 31 October 2019 9:33:30 AM NZDT McKay, Sean wrote: > This is probably a super easy question, but I've been searching half the day > and decided it would be faster to ask for help. > I know I've seen documentation in one of the manuals that points out major > changes in syntax or behavior that will need to be fixed when upgrading the > underlying version of poky, but now that I have need of it, I can't seem to > find it anywhere. Can anyone point me in the right direction? It's in the reference manual: https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#migration BTW if you (or anyone else) finds anything we missed documenting here then please do let us know - things do slip by, especially upstream changes. Cheers, Paul -- Paul Eggleton Intel System Software Products -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Where is the documentation for things to fix when upgrading poky versions?
I finally found it... ยง25 of the mega manual. Not sure if it's anywhere else that's easier to find but I guess I just needed to ask. Thanks! -Sean From: yocto-boun...@yoctoproject.org On Behalf Of McKay, Sean Sent: Wednesday, October 30, 2019 1:34 PM To: yocto@yoctoproject.org Subject: [yocto] Where is the documentation for things to fix when upgrading poky versions? Hi all, This is probably a super easy question, but I've been searching half the day and decided it would be faster to ask for help. I know I've seen documentation in one of the manuals that points out major changes in syntax or behavior that will need to be fixed when upgrading the underlying version of poky, but now that I have need of it, I can't seem to find it anywhere. Can anyone point me in the right direction? Thanks! -Sean McKay -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] NooB: applying new patches to older files, where do I find the older files?
On 10/30/19 8:16 AM, R wrote: Hello List, First I'm working on a unsupported distro (Manjaro) and try to get an older version (2.7.1) of poky working. I have ask a question before and Ross Burton pointed me in the direction of a patch. Now I'm trying to apply that patch, however the patch is for a newer version of the original files, so I need to make my own patch for the older version of these files. (reason: WARNING: Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.) The patch says: the file to be patch is e.g. /linux-user/syscall.c My question is where can I find the original syscall.c before any patches are applied to it? Hi Robert, This file and the patch are for the qemu package. You can run: $ bitbake -c patch qemu-native <--- host build or $ bitbake -c patch qemu <--- target build to get all the patches that are listed in the qemu recipe in poky: meta/recipes-devtools/qemu/qemu_3.1.1.1.bb and meta/recipes-devtools/qemu/qemu.inc applied to unpacked source. The patched source will be in (this is on master branch): /tmp-glibc/work/x86_64-linux/qemu-native/4.1.0-r0/qemu-4.1.0/linux-user/syscall.c poky might just be /tmp/ instead of /tmp-glibc/ In my case the log of the patching is in: tmp-glibc/work/x86_64-linux/qemu-native/4.1.0-r0/temp/log.do_patch Just to be complete: I have tried the latest warrior branch and that worked fine. My objective is not just to get it working be also to get a grip on how the system works :-) Super. Have you looked at: https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html and perhaps: https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#finding-the-temporary-source-code will be useful now. Manipulating patches by hand can be tedious. There's a tool called wiggle: https://linux.die.net/man/1/wiggle which can help but may be too much for you to deal with initially. Actually, I suggest that you build on a supported distro initially to understand the basic workflow and then decide if you want to figure out how to make Arch/Manjaro work. ../Randy Thanks, Robert. -- # Randy MacLeod # Wind River Linux -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Which recipe for qmicli?
Hi, The qmicli is in libqmi-utils in Ubuntu package, but I could not find Yocto libqmi-utils, only libqmi recipe, is qmicli in libqmi? Thank you. Kind regards, - jh -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Which recipe for qmicli?
On Thu, Oct 31, 2019 at 7:26 AM JH wrote: > > Hi, > > The qmicli is in libqmi-utils in Ubuntu package, but I could not find > Yocto libqmi-utils, only libqmi recipe, is qmicli in libqmi? yes, it is there. There isn't a 1 to 1 mapping between debian and OE package names. But if you build libqmi recipe, you will see that the libqmi package includes qmicli. > > Thank you. > > Kind regards, > > - jh > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
