[yocto] This one can't be me...

Darren Hart dvhart at linux.intel.com
Thu Apr 4 10:17:14 PDT 2013



On 04/03/2013 05:32 PM, Paul D. DeRocco wrote:
>> From: Bodke, Kishore K
>>
>> It's surprising that you don't see anything under 
>> /home/pauld/yocto-atom/build/tmp/work/cedartrail_nopvr-poky-li
> nux/linux-yoct
>> o-3.0.32+git1+a4ac64fe873f08ef718e2849b88914725dc99c1c_1+1e79e
> 03d115ed177882
>> ab53909a4f3555e434833-r4.1/linux-cedartrail-nopvr-standard-build
>>
>> It means that Kernel is not getting build for you?
>> How come you were able to generate the .hddimg and trying to boot?
>>
>> Do you have the rootfs under 
>> build/tmp/work/Cedartrail*/core-image-sato/?
> 
> Some gremlin made that first directory go away. I've successfully rebuilt
> it.
> 
> There is a rootfs directory in the second directory, and it contains things
> like /dev/ram?. I captured a tree listing of my build a while back, and it
> had those device nodes, too.
> 
> If I loop mount the .ext3 file that my panicking build produced, it has
> /dev/ram? device nodes, too.
> 

I believe those are generated by devtmpfs anyway.


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



More information about the yocto mailing list