Bug 2518 - linux-korg recipe does not work with v3.4 kernel
Summary: linux-korg recipe does not work with v3.4 kernel
Status: VERIFIED FIXED
Alias: None
Product: Kernel
Classification: Yocto Project Subprojects
Component: kernel-tooling (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Undecided major
Target Milestone: 1.3 M1
Assignee: Bruce Ashfield
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks: 2446
  Show dependency tree
 
Reported: 2012-05-29 18:16 UTC by Nitin Kamble
Modified: 2012-06-12 15:55 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nitin Kamble 2012-05-29 18:16:20 UTC
Error reported:

DEBUG: Executing shell function do_patch
ERROR: Function failed: do_patch (see /srv/home/nitin/builds/build-x32/tmp/work/qemux86_64-poky-linux-gnux32/linux-korg-3.4+git1+76e10d158efb6d4516018846f60c2ab5501900bc-r0/temp/log.do_patch.12214 for further information)
ERROR. meta data not found, check upstream repo for tags and branches


The recipe file: cat linux-korg_3.4.bb

inherit kernel
require recipes-kernel/linux/linux-yocto.inc

KMACHINE = "x32"
YOCTO_KERNEL_EXTERNAL_BRANCH = "master"
YOCTO_KERNEL_META_DATA = ""

KBRANCH = "${KMACHINE}"
KMETA = "meta"

SRC_URI = "git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git;nocheckout=1;branch=master;bareclone=1 \
           file://defconfig \
           "

SRCREV = "76e10d158efb6d4516018846f60c2ab5501900bc"

LINUX_VERSION = "3.4"
LOCALCOUNT = "0"
LINUX_VERSION_EXTENSION ?= "-yoctized-${LINUX_KERNEL_TYPE}"
PR = "r0"
PV = "${LINUX_VERSION}+git${SRCPV}"

#COMPATIBLE_MACHINE = "(qemuarm|qemux86|qemuppc|qemumips|qemux86-64)"

# 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

#require recipes-kernel/linux/linux-tools.inc
Comment 1 Bruce Ashfield 2012-05-29 18:26:48 UTC
We'll be replacing linux-korg with linux-yocto-custom. It worked with
3.4 last I checked. I'll double check, since there are some pending
updates.

If you really want the 3.4 kernel, master branch, you'd be better off
using linux-yocto-dev and shortly linux-yocto_3.4.
Comment 2 Nitin Kamble 2012-05-29 19:37:54 UTC
Bruce,
   where is linux-yocto-dev recipe ? is it based on v3.4 ?
Comment 3 Bruce Ashfield 2012-05-29 20:54:37 UTC
You should see:

http://git.yoctoproject.org/cgit/cgit.cgi/poky-extras/tree/meta-kernel-dev/recipes-kernel/linux/linux-yocto-dev.bb

In your poky-extras. The tree is based on 3.4 and will shortly be
renamed linux-yocto_3.4.bb .. but is completely usable at the moment,
since it is the basis for the next yocto kernel.
Comment 4 Bruce Ashfield 2012-05-30 05:38:08 UTC
Are you working out of master ? You'll need to grab the latest 
example linux-korg example out of meta-kernel-dev in poky-extras and 
master of yocto-kernel-tools if you want linux-korg to work.

I have a pending review for the updates to kern tools, but ensure that
your SRCREV is set to 0859d2f73cc6f6973835fa5713b5a98a43ed43ff to get
all the fixes.

With that, and using the linux-korg reference in poky-extras, it will build.
Comment 5 Nitin Kamble 2012-05-30 21:38:17 UTC
I was on master only. I looked at the linux-korg.bb from poky-extras. And I changed my linux-korg recipe similarly. And now it is working as expected.
Comment 6 Bruce Ashfield 2012-06-12 13:00:35 UTC
Why are we changing the asignee for this bug ? Putting it back to myself.
Comment 7 Laurentiu Serban 2012-06-12 13:34:17 UTC
It was set to resolved fixed.
And the target milestone is 1.3M1
So it should be verified by someone...
Comment 8 Bruce Ashfield 2012-06-12 13:40:59 UTC
Aha. I can do the verification. But we don't need to change the assignee for the bug, just for verification .. do we ?
Comment 9 Darren Hart 2012-06-12 14:24:55 UTC
(In reply to comment #8)
> Aha. I can do the verification. But we don't need to change the assignee for
> the bug, just for verification .. do we ?

No, we do not need to change the assignee just to verify it, but if it is a long process to do the verification, it might make it easier for QA to track if it is assigned to them. I would try to use the RESOLVED state for the queries first and only reassign if that proves inadequate.
Comment 10 Bruce Ashfield 2012-06-12 15:55:45 UTC
verified on 

meta-yocto        = "master:cc96daa4443ca39e409040e3e4aff783658b8f6a"
meta-kernel-dev   = "master:86238cfede00c2fe5c43d6dcbf40c6f37748bac0"

linux-korg + a valid defconfig patches and builds.