2487 2012-05-23 23:15:49 +0000 linux-korg recipes do not work with tar.gz sources 2012-07-03 20:46:38 +0000 1 1 6 Yocto Project Subprojects Kernel kernel-tooling unspecified x86 Multiple VERIFIED WONTFIX Medium major 1.3 M1 2446 1 nitin.a.kamble bruce.ashfield dvhart laurentiu.serban richard.purdie yp.kernel.watcher yp.watcher --- --- --- oldest_to_newest 21562 0 nitin.a.kamble 2012-05-23 23:15:49 +0000 Gets this error: NOTE: package linux-korg-3.4-r0: task do_kernel_checkout: Started ERROR: Function failed: do_kernel_checkout (see /srv/home/nitin/builds/build-x32/tmp/work/qemux86_64-poky-linux-gnux32/linux-korg-3.4-r0/temp/log.do_kernel_checkout.5960 for further information) ERROR: Logfile of failure stored in: /srv/home/nitin/builds/build-x32/tmp/work/qemux86_64-poky-linux-gnux32/linux-korg-3.4-r0/temp/log.do_kernel_checkout.5960 Log data follows: | ERROR: Function failed: do_kernel_checkout (see /srv/home/nitin/builds/build-x32/tmp/work/qemux86_64-poky-linux-gnux32/linux-korg-3.4-r0/temp/log.do_kernel_checkout.5960 for further information) | fatal: Not a git repository (or any parent up to mount parent ) | Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). | fatal: Not a git repository (or any parent up to mount parent ) | Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). | Not checking out x32, it will be created later | fatal: Not a git repository (or any parent up to mount parent ) | Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). NOTE: package linux-korg-3.4-r0: task do_kernel_checkout: Failed $ cat linux-korg_3.4.bb inherit kernel require recipes-kernel/linux/linux-yocto.inc KMACHINE = "x32" YOCTO_KERNEL_META_DATA = "" KBRANCH = "${KMACHINE}" KMETA = "meta" SRC_URI[md5sum] = "146af0160fc7a60cf9acf44aec13482b" SRC_URI[sha256sum] = "a797a15d0b6228381507c14ecf4eec4a6cc5c77cfd521ba3b3e1325e85b5b16d" SRC_URI = "http://www.kernel.org/pub/linux/kernel/v3.0/linux-3.4.tar.bz2 \ file://defconfig \ " S = "${WORKDIR}/linux-3.4" LINUX_VERSION = "3.4" LOCALCOUNT = "0" LINUX_VERSION_EXTENSION ?= "-yoctized-${LINUX_KERNEL_TYPE}" PR = "r0" PV = "${LINUX_VERSION}" # Functionality flags KERNEL_REVISION_CHECKING = "" # extra tasks addtask kernel_link_vmlinux after do_compile before do_install addtask validate_branches before do_patch after do_kernel_checkout addtask kernel_configcheck after do_configure before do_compile 21600 1 dvhart 2012-05-25 03:07:27 +0000 Bruce, can you look at this for 1.3 M1? 21651 2 bruce.ashfield 2012-05-28 02:57:33 +0000 There's no sense looking at this for 1.3. Anything supported by the linux-yocto recipes works on git trees .. end of story. I have supported tgz's in the past by creating a git repository our of the tree, etc, but it adds a LOT of code complexity and it doesn't follow the workflow we are promoting. Why not just use the upstream git repository ? If we are talking about saving the time of a clone, etc, then there are other approaches to take first, before resorting to a tgz. 22334 3 richard.purdie 2012-06-19 12:20:09 +0000 Bruce, I thought we'd talked about being able to extend a kernel with limited functionality from the kernel tooling such as the fragement management? 22336 4 bruce.ashfield 2012-06-19 12:54:45 +0000 We did discuss the limited kernel extension, but that doesn't include a tgz kernel at the moment. It's any git repository, which is what the liunux-yocto-custom recipe handles. To extend it to tgz means restoring a lot of complexity which has been removed over the years, and breaking the use case of git/git manipulations in feature descriptions. The shallow clones, or other space saving ideas are higher in the list of TODO items before tgz's. It's like asking for Makefile based recipes instead of bitbake recipes ... 22340 5 bruce.ashfield 2012-06-19 14:56:18 +0000 I've added a new 1.3 feature to my 'bubble' list to address this. It should be simple enough to create a git repo, and normalize most of the tools on that. I'll likely introduce it via the -dev layer, and then out after that. 22344 6 laurentiu.serban 2012-06-19 16:02:46 +0000 So guys can we change the status of the bug? I suggest reopening it and set with a later milestone. Thank you, Laurentiu 22345 7 bruce.ashfield 2012-06-19 16:17:04 +0000 No. This bug is not a bug .. I'll open a feature request against 1.3, but it may not make 1.4, since tgz's based building is not something to promote. 22765 8 laurentiu.serban 2012-07-03 20:46:38 +0000 Verified. Bruce opened a feature request.