2032 2012-02-27 17:00:18 +0000 FRI2: do_kernel_checkout failes for linux-libc-headers-yocto 2012-03-15 12:40:56 +0000 1 1 7 Build System, Metadata & Runtime BSPs bsps-configuration 1.2 Other x86_64 RESOLVED FIXED High major 1.2 M3 1 sgw bruce.ashfield dvhart yp.bsp.watcher yp.watcher --- --- --- oldest_to_newest 18767 0 sgw 2012-02-27 17:00:18 +0000 I am getting a very reproducible failure from a cleanall state with linux-libc-headers-yocto when building for FRI2 NOTE: Running task 454 of 468 (ID: 1, /intel/poky2/distro/meta/recipes-kernel/linux-libc-headers/linux-libc-headers-yocto_git.bb, do_kernel_checkout) NOTE: package linux-libc-headers-yocto-2.6.37+git-1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3_1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3-r4: task do_kernel_checkout: Started ERROR: Function failed: do_kernel_checkout (see /intel/poky2/builds/fri/tmp/work/core2-poky-linux/linux-libc-headers-yocto-2.6.37+git-1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3_1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3-r4/temp/log.do_kernel_checkout.7612 for further information) ERROR: Logfile of failure stored in: /intel/poky2/builds/fri/tmp/work/core2-poky-linux/linux-libc-headers-yocto-2.6.37+git-1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3_1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3-r4/temp/log.do_kernel_checkout.7612 Log data follows: | ERROR: Function failed: do_kernel_checkout (see /intel/poky2/builds/fri/tmp/work/core2-poky-linux/linux-libc-headers-yocto-2.6.37+git-1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3_1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3-r4/temp/log.do_kernel_checkout.7612 for further information) | + cd /intel/poky2/builds/fri/tmp/work/core2-poky-linux/linux-libc-headers-yocto-2.6.37+git-1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3_1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3-r4/linux | + do_kernel_checkout | + rm -rf /intel/poky2/builds/fri/tmp/work/core2-poky-linux/linux-libc-headers-yocto-2.6.37+git-1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3_1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3-r4/linux | + mkdir -p /intel/poky2/builds/fri/tmp/work/core2-poky-linux/linux-libc-headers-yocto-2.6.37+git-1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3_1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3-r4/linux/.git | + set +e | + '[' -d /intel/poky2/builds/fri/tmp/work/core2-poky-linux/linux-libc-headers-yocto-2.6.37+git-1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3_1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3-r4/git/.git ']' | + echo 'WARNING. /intel/poky2/builds/fri/tmp/work/core2-poky-linux/linux-libc-headers-yocto-2.6.37+git-1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3_1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3-r4/git is not a bare clone.' | WARNING. /intel/poky2/builds/fri/tmp/work/core2-poky-linux/linux-libc-headers-yocto-2.6.37+git-1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3_1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3-r4/git is not a bare clone. | + echo 'Ensure that the SRC_URI includes the '\''bareclone=1'\'' option.' | Ensure that the SRC_URI includes the 'bareclone=1' option. | + mv /intel/poky2/builds/fri/tmp/work/core2-poky-linux/linux-libc-headers-yocto-2.6.37+git-1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3_1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3-r4/git/.git /intel/poky2/builds/fri/tmp/work/core2-poky-linux/linux-libc-headers-yocto-2.6.37+git-1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3_1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3-r4/linux | + rm -rf /intel/poky2/builds/fri/tmp/work/core2-poky-linux/linux-libc-headers-yocto-2.6.37+git-1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3_1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3-r4/git/ | + cd /intel/poky2/builds/fri/tmp/work/core2-poky-linux/linux-libc-headers-yocto-2.6.37+git-1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3_1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3-r4/linux | + git branch -a | + grep -q meta | + '[' 0 -ne 0 ']' | + '[' -z '' ']' | + git branch -a | + grep -q | Usage: grep [OPTION]... PATTERN [FILE]... | Try `grep --help' for more information. | + '[' 2 -ne 0 ']' | + echo 'ERROR. The branch '\'''\'' is required and was not' | ERROR. The branch '' is required and was not | + echo 'found. Ensure that the SRC_URI points to a valid linux-yocto' | found. Ensure that the SRC_URI points to a valid linux-yocto | + echo 'kernel repository' | kernel repository | + exit 1 NOTE: package linux-libc-headers-yocto-2.6.37+git-1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3_1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3-r4: task do_kernel_checkout: Failed ERROR: Task 1 (/intel/poky2/distro/meta/recipes-kernel/linux-libc-headers/linux-libc-headers-yocto_git.bb, do_kernel_checkout) failed with exit code '1' NOTE: Tasks Summary: Attempted 454 tasks of which 421 didn't need to be rerun and 1 failed. Summary: 1 task failed: /intel/poky2/distro/meta/recipes-kernel/linux-libc-headers/linux-libc-headers-yocto_git.bb, do_kernel_checkout Summary: There was 1 ERROR message shown, returning a non-zero exit code. 18771 1 bruce.ashfield 2012-02-27 19:35:49 +0000 patch sent to the mailing list. 18811 2 dvhart 2012-02-29 23:59:05 +0000 There is more to it that what the patch addresses. Once we get past do_kernel_checkout, if the KBRANCH doesn't exist in the repository, then do_validate_branches craps out. This means new BSPs on newer kernels will cause the older linux-libc-headers-yocto to fail. We can use the tarball PREFERRED_VERSION workaround in these cases - but it seems to be we would be better off just PROVIDING linux-libc-headers in the linux-yocto* recipes. Then we have a guaranteed 1:1 mapping and don't have to jump through the checkout/validate hoops multiple times. 18812 3 bruce.ashfield 2012-03-01 00:45:42 +0000 No there shouldn't be more to this than my patch addresses. There is supposed to always be a default KBRANCH. I built and deployed this 10 or 11 times today alone, with the BSP in question. So there must be something different in the configurations. 18813 4 dvhart 2012-03-01 00:50:18 +0000 Maybe that I am now building for 3.2 which has a different branching hierarchy than 3.0 ? 18814 5 bruce.ashfield 2012-03-01 00:51:57 +0000 I could be. The recipe needs a bump regardless. So your comment stands (it shouldn't be PV of 2.6.37). I'll address that and see if I can reproduce the problem. We may be able to unify the libc-headers and the kernel recipe, but it does break the separation between the two that has traditionally been enforced 18815 6 bruce.ashfield 2012-03-01 01:03:40 +0000 Just logging the last run; NOTE: package linux-libc-headers-yocto-2.6.37+git-1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3_1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3-r4: task do_validate_branches: StartedNOTE: package linux-libc-headers-yocto-2.6.37+git-1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3_1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3-r4: task do_validate_branches: SucceededNOTE: Running task 497 of 510 (ID: 3, /home/bruce/poky/meta/recipes-kernel/linux-libc-headers/linux-libc-headers-yocto_git.bb, do_patch) 18816 7 bruce.ashfield 2012-03-01 01:52:50 +0000 Can someone else confirm that my contrib branch (zedd/kernel) fixes the libc-header build ? Since clearly, my testing alone isn't sufficient. You want this change in particular: commit da4b543dc2f74f5172f1d7b3500d76f0ba81c8dd Author: Bruce Ashfield <bruce.ashfield@windriver.com> Date: Wed Feb 29 20:46:13 2012 -0500 linux-libc-headers-yocto: bump to v3.2.8 Making two changes for BSPs that prefer linux-libc-headers-yocto: - bumping to v3.2.8 headers - stubbing out unecessary linux-yocto functions when headers are being built Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> :100644 100644 734170f... 10b6b83... M meta/recipes-kernel/linux-libc-headers/linux-libc-headers-yocto_git.bb 18817 8 dvhart 2012-03-01 02:03:57 +0000 This is mostly what I did to fix it locally. The other change I made was to set the "bareclone=1" in the SRC_URI. This change makes it use "master" if the BSP doesn't exist. It seems like "standard/default/base" would be a better default. However, I tried that and couldn't find a way to change KBRANCH in the libc-headers recipe if the specified KBRANCH didn't exist in the git tree. 18819 9 bruce.ashfield 2012-03-01 02:10:03 +0000 I'll be doing a mass bareclone=1 change to all the linux-yocto* recipes, so for now, I kept it out of this fix. It'll be a complete switchover shortly. We actually do want standard/base, since standard/default/base gets us configuration fragments, which aren't used as part of the headers. So to keep it safe, sticking with standard/base to get any changes is what we want. My change should be setting it to standard/base, did you see something different ? 18820 10 dvhart 2012-03-01 02:12:55 +0000 Ah yes, it is standard/base, and this patch builds fri2 using a 3.2 kernel just fine. Acked-by: Darren Hart <dvhart@linux.intel.com> 18821 11 bruce.ashfield 2012-03-01 02:16:29 +0000 Sending patch to the list. bareclone to follow later. 19135 12 bruce.ashfield 2012-03-15 12:40:56 +0000 Marking as resolved.