All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <darren.hart@intel.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: kernel-tools failure for linux-yoctort_3.0.bb for poky/edison branch.
Date: Tue, 13 Dec 2011 15:15:13 -0800	[thread overview]
Message-ID: <4EE7DC81.6030609@intel.com> (raw)
In-Reply-To: <4EE7DA4D.4080500@windriver.com>

On 12/13/2011 03:05 PM, Bruce Ashfield wrote:
> On 11-12-13 5:50 PM, Bodke, Kishore K wrote:
>> Hi,
>>
>> I get failure for the linux-yoctort_3.0.bb file for the poky Edison branch.
>>
>> Darren told that it was fixed and merged to master.
> 
> This shouldn't be happening on edison at all. The changes to the
> kernel recipes/tools to use the merge_config.sh should never have
> showed up in edison. That's yocto 1.2 development work.
> 
> So the fix for this is to find out what leaked into edison and
> revert it. I'll have a look at that later tonight.

No no. Kishore is using meta-kernel-dev. As such he is getting the
latest linux-yocto repository and SRC_REVs. The question, I think, is
really why isn't the kern-tools-native bbappend from meta-kernel-dev
doing this for him.

--
Darren

> 
> Bruce
> 
>>
>> I wanted to bring to the list about this error message.
>>
>> ERROR: Function 'do_kernel_configme' failed (see
>> /usr/local/src/yocto_1_1_release/poky/build1/tmp/work/crystalforest-poky-linux/linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1/temp/log.do_kernel_configme.18502
>> for further information)
>>
>> ERROR: Logfile of failure stored in:
>> /usr/local/src/yocto_1_1_release/poky/build1/tmp/work/crystalforest-poky-linux/linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1/temp/log.do_kernel_configme.18502
>>
>> Log data follows:
>>
>> | [INFO] doing kernel configme
>>
>> | [INFO] Branch yocto/standard/preempt-rt/base used by
>> common-pc-preempt-rt.scc
>>
>> | [INFO] collecting configs in ./meta/meta-series
>>
>> | mv: cannot stat
>> `/usr/local/src/yocto_1_1_release/poky/build1/tmp/work/crystalforest-poky-linux/linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1/linux-crystalforest-preempt-rt-build/.tmp.config*':
>> No such file or directory
>>
>> | creation of pre-processed config data failed
>>
>> | config of yocto/standard/preempt-rt/base (common-pc-preempt-rt.scc) failed
>>
>> | ERROR: Function 'do_kernel_configme' failed (see
>> /usr/local/src/yocto_1_1_release/poky/build1/tmp/work/crystalforest-poky-linux/linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1/temp/log.do_kernel_configme.18502
>> for further information)
>>
>> NOTE: package
>> linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1:
>> task do_kernel_configme: Failed
>>
>> ERROR: Task 716
>> (/usr/local/src/yocto_1_1_release/poky/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb,
>> do_kernel_configme) failed with exit code '1'
>>
>> Waiting for 7 active tasks to finish:
>>
>> 0: acl-native-2.2.51-r2 do_configure (pid 12164)
>>
>> 1: elfutils-native-0.148-r3 do_install (pid 19851)
>>
>> 2: kbproto-native-1_1.0.5-r0 do_configure (pid 20113)
>>
>> 3: font-util-native-1.2.0-r2.1 do_configure (pid 14632)
>>
>> 4: bison-native-2.5-r1 do_configure (pid 20206)
>>
>> 5: dbus-native-1.4.12-r0 do_configure (pid 20209)
>>
>> 6: opensp-native-1.5-r2 do_configure (pid 20213)
>>
>> Waiting for 6 active tasks to finish:
>>
>> 0: acl-native-2.2.51-r2 do_configure (pid 12164)
>>
>> 1: elfutils-native-0.148-r3 do_install (pid 19851)
>>
>> 2: kbproto-native-1_1.0.5-r0 do_configure (pid 20113)
>>
>> 3: font-util-native-1.2.0-r2.1 do_configure (pid 14632)
>>
>> 4: bison-native-2.5-r1 do_configure (pid 20206)
>>
>> 5: dbus-native-1.4.12-r0 do_configure (pid 20209)
>>
>> NOTE: package opensp-native-1.5-r2: task do_configure: Succeeded
>>
>> Waiting for 5 active tasks to finish:
>>
>> 0: acl-native-2.2.51-r2 do_configure (pid 12164)
>>
>> 1: elfutils-native-0.148-r3 do_install (pid 19851)
>>
>> 2: kbproto-native-1_1.0.5-r0 do_configure (pid 20113)
>>
>> 3: bison-native-2.5-r1 do_configure (pid 20206)
>>
>> 4: dbus-native-1.4.12-r0 do_configure (pid 20209)
>>
>> NOTE: package font-util-native-1.2.0-r2.1: task do_configure: Succeeded
>>
>> Waiting for 4 active tasks to finish:
>>
>> 0: acl-native-2.2.51-r2 do_configure (pid 12164)
>>
>> 1: elfutils-native-0.148-r3 do_install (pid 19851)
>>
>> 2: kbproto-native-1_1.0.5-r0 do_configure (pid 20113)
>>
>> 3: bison-native-2.5-r1 do_configure (pid 20206)
>>
>> NOTE: package dbus-native-1.4.12-r0: task do_configure: Succeeded
>>
>> Waiting for 3 active tasks to finish:
>>
>> 0: elfutils-native-0.148-r3 do_install (pid 19851)
>>
>> 1: kbproto-native-1_1.0.5-r0 do_configure (pid 20113)
>>
>> 2: bison-native-2.5-r1 do_configure (pid 20206)
>>
>> NOTE: package acl-native-2.2.51-r2: task do_configure: Succeeded
>>
>> Waiting for 2 active tasks to finish:
>>
>> 0: elfutils-native-0.148-r3 do_install (pid 19851)
>>
>> 1: bison-native-2.5-r1 do_configure (pid 20206)
>>
>> NOTE: package kbproto-native-1_1.0.5-r0: task do_configure: Succeeded
>>
>> Waiting for 1 active tasks to finish:
>>
>> 0: bison-native-2.5-r1 do_configure (pid 20206)
>>
>> NOTE: package elfutils-native-0.148-r3: task do_install: Succeeded
>>
>> NOTE: package bison-native-2.5-r1: task do_configure: Succeeded
>>
>> ERROR:
>> '/usr/local/src/yocto_1_1_release/poky/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb'
>> failed
>>
>> Thanks
>>
>> Kishore.
>>
> 


-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel


  reply	other threads:[~2011-12-13 23:15 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-13 22:50 kernel-tools failure for linux-yoctort_3.0.bb for poky/edison branch Bodke, Kishore K
2011-12-13 23:05 ` Bruce Ashfield
2011-12-13 23:15   ` Darren Hart [this message]
2011-12-13 23:17     ` Bodke, Kishore K
2011-12-13 23:24       ` Bruce Ashfield
2011-12-13 23:26         ` Bodke, Kishore K
2011-12-14  5:13           ` Bruce Ashfield
2011-12-14  5:47             ` Darren Hart
2011-12-14 14:07               ` Bruce Ashfield
2011-12-16 19:27                 ` Bodke, Kishore K
2011-12-16 19:29                   ` Bruce Ashfield
2011-12-16 19:32                   ` Darren Hart
2011-12-16 19:39                     ` Bodke, Kishore K
2011-12-16 20:18                       ` Darren Hart
2011-12-16 22:12                         ` Bodke, Kishore K
2011-12-16 23:07                           ` Darren Hart
2011-12-17  1:06                             ` Bodke, Kishore K
2011-12-17  1:22                             ` Bodke, Kishore K
2011-12-17  1:34                               ` Darren Hart
2011-12-17  3:03                                 ` Bruce Ashfield
2011-12-17  3:17                                   ` Darren Hart
2011-12-19 22:11                                     ` Bodke, Kishore K
2012-01-12 20:39                                   ` Tom Zanussi
2012-01-12 20:52                                     ` Darren Hart
2012-01-12 21:27                                       ` Bruce Ashfield
2012-01-13 15:41                                     ` Bruce Ashfield
2012-01-13 15:45                                       ` Tom Zanussi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4EE7DC81.6030609@intel.com \
    --to=darren.hart@intel.com \
    --cc=bruce.ashfield@windriver.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.