Re: [yocto] NooB: applying new patches to older files, where do I find the older files?

2019-10-30 Thread Randy MacLeod
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

Re: [yocto] Where is the documentation for things to fix when upgrading poky versions?

2019-10-30 Thread McKay, Sean
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:

Re: [yocto] Where is the documentation for things to fix when upgrading poky versions?

2019-10-30 Thread Paul Eggleton
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

[yocto] Where is the documentation for things to fix when upgrading poky versions?

2019-10-30 Thread McKay, Sean
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

Re: [yocto] [zeus] icu-native-64.2-r0 do_configure: configure failed

2019-10-30 Thread Ross Burton
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] QA notification for completed autobuilder build (yocto-2.7.2.rc1)

2019-10-30 Thread Pokybuild User
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

Re: [linux-yocto] kernel-dev rpm does not have much contents

2019-10-30 Thread Michael Lim
>>Thank you Bruce. After enable kernel-devsrc, the necessary rpm had been created. >> >>I have one question though, the kernel-devsrc does not seem to include all the kernel src, that has been fetched and applied patches. Why does it call kernel-devsrc instead of just kernel-dev? Is there a way

Re: [linux-yocto] kernel-dev rpm does not have much contents

2019-10-30 Thread Bruce Ashfield
On Wed, Oct 30, 2019 at 10:44 AM Michael Lim wrote: > >>>You want the kernel-devsrc package, not kernel-dev in this case. > >> > >>>Bruce > >> > >> Thank you for responding Bruce. > >> > >> I do not see kernel-devsrc defined in the kernel.bbclass > > > >It's a separate recipe. Not part of the

[yocto] [meta-freescale][NXP] Failed to build gstreamer1.0 ith Yocto thud on NXP IMX8MQ

2019-10-30 Thread Karim ATIKI
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:

Re: [linux-yocto] kernel-dev rpm does not have much contents

2019-10-30 Thread Michael Lim
>>>You want the kernel-devsrc package, not kernel-dev in this case. >> >>>Bruce >> >> Thank you for responding Bruce. >> >> I do not see kernel-devsrc defined in the kernel.bbclass > >It's a separate recipe. Not part of the bbclass. Build that recipe, >and install the package and you'll get what

[yocto] NooB: applying new patches to older files, where do I find the older files?

2019-10-30 Thread R
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

Re: [yocto] [zeus] icu-native-64.2-r0 do_configure: configure failed

2019-10-30 Thread Arno Steffens
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 ?!?

Re: [yocto] [zeus] icu-native-64.2-r0 do_configure: configure failed

2019-10-30 Thread Ross Burton
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

[linux-yocto] [PATCH] Revert "arm64: dts: r8a7795: Add CPUIdle support for all CPU core"

2019-10-30 Thread Meng.Li
From: Limeng This reverts commit c93bf81feabf89b5ee77838d3bb62825d04dab09. Support cpu ilde feature, there are still other related patches need to be applied, but as a basic BSP, it doesn't recommend to merge lots of patches to standard/base branch. In addtional, only get one patch of cpu ilde

[linux-yocto] [linux-yocto-v5.2]: [kernel v5.2/standard/base]: Revert "arm64: dts: r8a7795: Add CPUIdle support for all CPU core"

2019-10-30 Thread Meng.Li
From: Limeng Hi Bruce, Some days ago, I sent a patch to add CPUIdle feature for renesas-rcar platform. This patch only add cpu-idle-states property in dts file. But after testing, we find out it causes kernel unstable when run some stress testing cases. So, I think maybe I omit other cpuidle

[yocto] [zeus] icu-native-64.2-r0 do_configure: configure failed

2019-10-30 Thread star
Build of image failed, I got strange and long error messages like: ERROR: icu-native-64.2-r0 do_configure: configure failed ERROR: icu-native-64.2-r0 do_configure: Execution of '/home/.../tmp/work/x86_64-linux/icu-native/64.2-r0/temp/run.do_configure ... | configure: WARNING: unrecognized