Re: [yocto] question on poky and git interaction
On 13/01/12 17:27, Jim Abernathy wrote: under the poky directory you git checkout of the branch you want to work with, then you clone meta-intel and within that directory you checkout a branch. if you needed to use git for you personal project, you can't put it at the same meta-intel level, right? Only one per directory??? I would guess that you'd need to create your personal git clone below meta-intel; something like meta-jima. Does this sound correct?? Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto Hi Jim, This is indeed how I manage my extra package files and anything else poky needs. Any other interesting input would be good to hear though! Slightly off-topic, with meta-intel and then checking out branches to get specific machines, do you do global work in master, machine specific work in the branches, and then merge out from master to the branches to keep them all in sync? Cheers, Jack. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] question on poky and git interaction
On Mon, Jan 16, 2012 at 4:27 AM, Jack Mitchell m...@communistcode.co.ukwrote: On 13/01/12 17:27, Jim Abernathy wrote: under the poky directory you git checkout of the branch you want to work with, then you clone meta-intel and within that directory you checkout a branch. if you needed to use git for you personal project, you can't put it at the same meta-intel level, right? Only one per directory??? I would guess that you'd need to create your personal git clone below meta-intel; something like meta-jima. Does this sound correct?? Jim A __**_ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.**org/listinfo/yoctohttps://lists.yoctoproject.org/listinfo/yocto Hi Jim, This is indeed how I manage my extra package files and anything else poky needs. Any other interesting input would be good to hear though! Slightly off-topic, with meta-intel and then checking out branches to get specific machines, do you do global work in master, machine specific work in the branches, and then merge out from master to the branches to keep them all in sync? At this point, I'm sticking to named releases like Edison. I have not tried Master yet. I need to learn a lot more before I try that. I get enough errors using official releases. Jim A Cheers, Jack. __**_ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.**org/listinfo/yoctohttps://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Linux RT build fail
Hi, I get build failure for the rt. ERROR: Function 'do_patch' failed (see /usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/temp/log.do_patch.32459 for further information) ERROR: Logfile of failure stored in: /usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/temp/log.do_patch.32459 Log data follows: | ERROR: Function 'do_patch' failed (see /usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/temp/log.do_patch.32459 for further information) | Deleted branch meta-temp (was 620917d). | | ERROR: patch /usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/linux/meta/cfg/kernel-cache/features/rt/rt-apply-patch-3.0.10-rt27.patch.patch is not available | | ERROR. Could not find an excutable target for yocto/standard/preempt-rt/base | ERROR. Could not locate meta series for preempt-rt-standard | ERROR. Could not modify yocto/standard/preempt-rt/base NOTE: package linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1: task do_patch: Failed NOTE: package bzip2-1.0.6-r4: task do_compile: Succeeded ERROR: Task 3 (/usr/local/src/jan13/poky/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb, do_patch) failed with exit code '1' Is this anything to do with meta-kernel-dev I am using or something else? Thanks Kishore. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Linux RT build fail
On 12-01-16 01:40 PM, Bodke, Kishore K wrote: Hi, I get build failure for the rt. ERROR: Function 'do_patch' failed (see /usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/temp/log.do_patch.32459 for further information) ERROR: Logfile of failure stored in: /usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/temp/log.do_patch.32459 Log data follows: | ERROR: Function 'do_patch' failed (see /usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/temp/log.do_patch.32459 for further information) | Deleted branch meta-temp (was 620917d). | | ERROR: patch /usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/linux/meta/cfg/kernel-cache/features/rt/rt-apply-patch-3.0.10-rt27.patch.patch is not available This is the problem. But I could have sworn that I fixed this, and send a merge request. When I just checked now, it still looks broken. That being said, we should have seen this before now. Are any -rt kernels being build regularly on master ? It is partially due to meta-kernel-dev picking up new kernel tools that do strict checking on patches by default (hence my question about anyone else building this on master). I'm pushing a fix out now to the meta branch and will send it along with my next consolidated pull request. Cheers, Bruce | | ERROR. Could not find an excutable target for yocto/standard/preempt-rt/base | ERROR. Could not locate meta series for preempt-rt-standard | ERROR. Could not modify yocto/standard/preempt-rt/base NOTE: package linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1: task do_patch: Failed NOTE: package bzip2-1.0.6-r4: task do_compile: Succeeded ERROR: Task 3 (/usr/local/src/jan13/poky/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb, do_patch) failed with exit code '1' Is this anything to do with meta-kernel-dev I am using or something else? Thanks Kishore. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Linux RT build fail
On 01/16/2012 10:44 AM, Bruce Ashfield wrote: On 12-01-16 01:40 PM, Bodke, Kishore K wrote: Hi, I get build failure for the rt. ERROR: Function 'do_patch' failed (see /usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/temp/log.do_patch.32459 for further information) ERROR: Logfile of failure stored in: /usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/temp/log.do_patch.32459 Log data follows: | ERROR: Function 'do_patch' failed (see /usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/temp/log.do_patch.32459 for further information) | Deleted branch meta-temp (was 620917d). | | ERROR: patch /usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/linux/meta/cfg/kernel-cache/features/rt/rt-apply-patch-3.0.10-rt27.patch.patch is not available This is the problem. But I could have sworn that I fixed this, and send a merge request. When I just checked now, it still looks broken. That being said, we should have seen this before now. Are any -rt kernels being build regularly on master ? I just checked with Beth and we are not. I will open a bug against the autobuilder, we need to do this regularly. -- Darren It is partially due to meta-kernel-dev picking up new kernel tools that do strict checking on patches by default (hence my question about anyone else building this on master). I'm pushing a fix out now to the meta branch and will send it along with my next consolidated pull request. Cheers, Bruce | | ERROR. Could not find an excutable target for yocto/standard/preempt-rt/base | ERROR. Could not locate meta series for preempt-rt-standard | ERROR. Could not modify yocto/standard/preempt-rt/base NOTE: package linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1: task do_patch: Failed NOTE: package bzip2-1.0.6-r4: task do_compile: Succeeded ERROR: Task 3 (/usr/local/src/jan13/poky/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb, do_patch) failed with exit code '1' Is this anything to do with meta-kernel-dev I am using or something else? Thanks Kishore. -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] qemu EFI build failure
Darren, I have reworked the commits to fix issues while building on other distros. Can you check this branch http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=nitin/grub-efi It is working for me on Fedora 14, for which the other grub-efi commit was failing for me. Thanks, Nitin -Original Message- From: Kamble, Nitin A Sent: Thursday, January 12, 2012 2:33 PM To: Kamble, Nitin A; Hart, Darren; Bodke, Kishore K Cc: Ahmad, Josef; yocto@yoctoproject.org Subject: RE: [yocto] qemu EFI build failure Here is the commit: http://git.yoctoproject.org/cgit.cgi/poky- contrib/log/?h=nitin/misc Nitin -Original Message- From: yocto-boun...@yoctoproject.org [mailto:yocto- boun...@yoctoproject.org] On Behalf Of Kamble, Nitin A Sent: Thursday, January 12, 2012 2:32 PM To: Hart, Darren; Bodke, Kishore K Cc: Ahmad, Josef; yocto@yoctoproject.org Subject: Re: [yocto] qemu EFI build failure I just sent a patch to oecore mailing list to fix the grub issue with automake 1.11.2. Thanks, Nitin -Original Message- From: Hart, Darren Sent: Thursday, January 12, 2012 1:39 PM To: Bodke, Kishore K Cc: Ahmad, Josef; yocto@yoctoproject.org; Kamble, Nitin A Subject: Re: [yocto] qemu EFI build failure On 01/12/2012 01:28 PM, Bodke, Kishore K wrote: I have only MACHINE_FEATURES += efi KERNEL_FEATURES_append_cedartrail += cfg/efi-ext.scc. I am not having IMAGE_FSTYPES += live. The live change is just to trigger the live image type which builds grub-efi-native for efi systems. qemux86 needs this added explicitly. -- Darren Thanks Kishore. -Original Message- From: Hart, Darren Sent: Thursday, January 12, 2012 1:20 PM To: Ahmad, Josef Cc: yocto@yoctoproject.org; Bodke, Kishore K; Kamble, Nitin A Subject: Re: [yocto] qemu EFI build failure On 01/12/2012 10:27 AM, Darren Hart wrote: On 01/12/2012 08:19 AM, Josef Ahmad wrote: I tried to build a qemux86 EFI image, by setting: - in my local.conf: IMAGE_FSTYPES += live - in poly/meta/conf/machine/qemux86.conf: MACHINE_FEATURES += efi I haven't tried live images with QEMU. For one thing, they aren't really necessary as you can specify all the boot parameters on the qemu command line. Is there are reason you want to use the live image specifically? Also, in order to properly test EFI in QEMU, you will need to use an EFI BIOS - I believe you're aware of this already - but this isn't currently supported by the runqemu scripts that ship with yocto. The build gave me the following error: I'll do some test builds - it isn't clear to me what is going on here. snip Has anyone encountered the same error? I'm not sure I set up the correct configuration. Also, is there another way to append efi to MACHINE_FEATURES rather than by modifying qemux86.conf? You should be able to do something like: MACHINE_FEATURES_append_qemux86 = efi Note that you will also need to enable the efi support in the kernel, which is done with the KERNEL_FEATURES variable, something like: KERNEL_FEATURES_append_qemux86 = conf/efi-ext.scc Either of these can be set in your local.conf. More accurately: MACHINE_FEATURES_append_qemux86= efi pcbios KERNEL_FEATURES_append_qemux86= cfg/efi-ext.scc IMAGE_FSTYPES += live With these added to local.conf and building for qemux86 I see the same configure failures reported by Kishore and Josef: | ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from... | acinclude.m4:363: grub_CHECK_STACK_ARG_PROBE is expanded from... I've discussed in IRC with Nitin and he thinks this may be related to the automake update and is looking into it. -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] qemu EFI build failure
On 01/16/2012 02:00 PM, Kamble, Nitin A wrote: Darren, I have reworked the commits to fix issues while building on other distros. Can you check this branch http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=nitin/grub-efi It is working for me on Fedora 14, for which the other grub-efi commit was failing for me. Thanks Nitin, Builds fine for me on Ubuntu 11.10 64 bit -- Darren Thanks, Nitin -Original Message- From: Kamble, Nitin A Sent: Thursday, January 12, 2012 2:33 PM To: Kamble, Nitin A; Hart, Darren; Bodke, Kishore K Cc: Ahmad, Josef; yocto@yoctoproject.org Subject: RE: [yocto] qemu EFI build failure Here is the commit: http://git.yoctoproject.org/cgit.cgi/poky- contrib/log/?h=nitin/misc Nitin -Original Message- From: yocto-boun...@yoctoproject.org [mailto:yocto- boun...@yoctoproject.org] On Behalf Of Kamble, Nitin A Sent: Thursday, January 12, 2012 2:32 PM To: Hart, Darren; Bodke, Kishore K Cc: Ahmad, Josef; yocto@yoctoproject.org Subject: Re: [yocto] qemu EFI build failure I just sent a patch to oecore mailing list to fix the grub issue with automake 1.11.2. Thanks, Nitin -Original Message- From: Hart, Darren Sent: Thursday, January 12, 2012 1:39 PM To: Bodke, Kishore K Cc: Ahmad, Josef; yocto@yoctoproject.org; Kamble, Nitin A Subject: Re: [yocto] qemu EFI build failure On 01/12/2012 01:28 PM, Bodke, Kishore K wrote: I have only MACHINE_FEATURES += efi KERNEL_FEATURES_append_cedartrail += cfg/efi-ext.scc. I am not having IMAGE_FSTYPES += live. The live change is just to trigger the live image type which builds grub-efi-native for efi systems. qemux86 needs this added explicitly. -- Darren Thanks Kishore. -Original Message- From: Hart, Darren Sent: Thursday, January 12, 2012 1:20 PM To: Ahmad, Josef Cc: yocto@yoctoproject.org; Bodke, Kishore K; Kamble, Nitin A Subject: Re: [yocto] qemu EFI build failure On 01/12/2012 10:27 AM, Darren Hart wrote: On 01/12/2012 08:19 AM, Josef Ahmad wrote: I tried to build a qemux86 EFI image, by setting: - in my local.conf: IMAGE_FSTYPES += live - in poly/meta/conf/machine/qemux86.conf: MACHINE_FEATURES += efi I haven't tried live images with QEMU. For one thing, they aren't really necessary as you can specify all the boot parameters on the qemu command line. Is there are reason you want to use the live image specifically? Also, in order to properly test EFI in QEMU, you will need to use an EFI BIOS - I believe you're aware of this already - but this isn't currently supported by the runqemu scripts that ship with yocto. The build gave me the following error: I'll do some test builds - it isn't clear to me what is going on here. snip Has anyone encountered the same error? I'm not sure I set up the correct configuration. Also, is there another way to append efi to MACHINE_FEATURES rather than by modifying qemux86.conf? You should be able to do something like: MACHINE_FEATURES_append_qemux86 = efi Note that you will also need to enable the efi support in the kernel, which is done with the KERNEL_FEATURES variable, something like: KERNEL_FEATURES_append_qemux86 = conf/efi-ext.scc Either of these can be set in your local.conf. More accurately: MACHINE_FEATURES_append_qemux86= efi pcbios KERNEL_FEATURES_append_qemux86= cfg/efi-ext.scc IMAGE_FSTYPES += live With these added to local.conf and building for qemux86 I see the same configure failures reported by Kishore and Josef: | ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from... | acinclude.m4:363: grub_CHECK_STACK_ARG_PROBE is expanded from... I've discussed in IRC with Nitin and he thinks this may be related to the automake update and is looking into it. -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Serial consoles
I'm using a Marshalltown Cedarview board and it's serial ports are standard PC com1 and com2 so I put the following in my conf/machine/mycdv.conf file, where mycdv is the name of my machine/bsp, i.e. meta-mycdv. SERIAL_CONSOLE = 115200 ttyS0 SYSLINUX_OPTS = serial 0 115200 APPEND = console=ttyS0,115200 console=tty0 When the system booted, I have the kernel console on com1 and I also got a login prompt on com1. However, the syslinux output was only displayed on the VGA monitor. Anyone know why? Maybe SYSLINUX_OPTS goes somewhere else? I noticed in the n450 release notes that they accomplish this with the following in the local.conf file: # Serial Port Setup for Intel Embedded Development Board 1-N40\ SYSLINUX_OPTS_atom-pc = serial 0 115200 SERIAL_CONSOLE_atom-pc = 115200 ttyS0 APPEND_atom-pc = console=ttyS0,115200 console=tty0 This does work for the N450, but the cedartrail bsp is not under standard/common-pc/atom-pc. It's under standard/cedartrail. If I have to put SYSLINUX_OPTS in local.conf, what is the suffix and why??? JIm A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Linux RT build fail
I get the same build ERRORS without meta-kernel-dev as well. Thanks Kishore. -Original Message- From: Hart, Darren Sent: Monday, January 16, 2012 11:14 AM To: Bruce Ashfield Cc: Bodke, Kishore K; yocto@yoctoproject.org Subject: Re: Linux RT build fail On 01/16/2012 10:44 AM, Bruce Ashfield wrote: On 12-01-16 01:40 PM, Bodke, Kishore K wrote: Hi, I get build failure for the rt. ERROR: Function 'do_patch' failed (see /usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/temp/log.do_patch.32459 for further information) ERROR: Logfile of failure stored in: /usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/temp/log.do_patch.32459 Log data follows: | ERROR: Function 'do_patch' failed (see /usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/temp/log.do_patch.32459 for further information) | Deleted branch meta-temp (was 620917d). | | ERROR: patch /usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/linux/meta/cfg/kernel-cache/features/rt/rt-apply-patch-3.0.10-rt27.patch.patch is not available This is the problem. But I could have sworn that I fixed this, and send a merge request. When I just checked now, it still looks broken. That being said, we should have seen this before now. Are any -rt kernels being build regularly on master ? I just checked with Beth and we are not. I will open a bug against the autobuilder, we need to do this regularly. -- Darren It is partially due to meta-kernel-dev picking up new kernel tools that do strict checking on patches by default (hence my question about anyone else building this on master). I'm pushing a fix out now to the meta branch and will send it along with my next consolidated pull request. Cheers, Bruce | | ERROR. Could not find an excutable target for yocto/standard/preempt-rt/base | ERROR. Could not locate meta series for preempt-rt-standard | ERROR. Could not modify yocto/standard/preempt-rt/base NOTE: package linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1: task do_patch: Failed NOTE: package bzip2-1.0.6-r4: task do_compile: Succeeded ERROR: Task 3 (/usr/local/src/jan13/poky/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb, do_patch) failed with exit code '1' Is this anything to do with meta-kernel-dev I am using or something else? Thanks Kishore. -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
