[yocto] Kernel Panics on armv4t with gcc.4.5.1

Gary Thomas gary at mlbassoc.com
Wed Feb 2 07:28:37 PST 2011


On 02/02/2011 06:45 AM, Gary Thomas wrote:
> On 01/31/2011 05:41 PM, Kamble, Nitin A wrote:
>> Diego,
>>
>> Can you try with 4.5.2 gcc from this branch: http://git.pokylinux.org/cgit/cgit.cgi/poky-contrib/log/?h=nitin/khem_gcc_nitin
>
> I too am having trouble (OMAP-L138 == armv5te/arm926ejs)
>
> Nitin, I tried using your branch, but it failed to build:
>
> NOTE: package gcc-cross-intermediate-4.5.2-r3: task do_populate_sysroot: Started
> ERROR: Error executing a python function in /home/local/poky-contrib/meta/recipes-devtools/gcc/gcc-cross-intermediate_4.5.2.bb:
> OSError: [Errno 2] No such file or directory:
> '/home/local/efacec_omap_4.5.2/tmp/work/armv5te-poky-linux-gnueabi/gcc-cross-intermediate-4.5.2-r3/sysroot-destdir///home/local/efacec_omap_4.5.2/tmp/sysroots/cobra-omapl138p78//lib'
>
> ERROR: The stack trace of python calls that resulted in this exception/failure was:
> ERROR: File "sstate_task_postfunc", line 10, in <module>
> ERROR:
> ERROR: File "sstate_task_postfunc", line 4, in sstate_task_postfunc
> ERROR:
> ERROR: File "sstate.bbclass", line 17, in sstate_install
> ERROR:
> ERROR: File "/home/local/poky-contrib/meta/lib/oe/path.py", line 56, in copytree
> ERROR: names = os.listdir(src)
> ERROR:
> ERROR: The code that was being executed was:
> ERROR: 0006: bb.build.exec_func(intercept, d)
> ERROR: 0007: sstate_package(shared_state, d)
> ERROR: 0008:
> ERROR: 0009:
> ERROR: *** 0010:sstate_task_postfunc(d)
> ERROR: 0011:
> ERROR: (file: 'sstate_task_postfunc', lineno: 10, function: <module>)
> ERROR: 0001:
> ERROR: 0002:def sstate_task_postfunc(d):
> ERROR: 0003: shared_state = sstate_state_fromvars(d)
> ERROR: *** 0004: sstate_install(shared_state, d)
> ERROR: 0005: for intercept in shared_state['interceptfuncs']:
> ERROR: 0006: bb.build.exec_func(intercept, d)
> ERROR: 0007: sstate_package(shared_state, d)
> ERROR: 0008:
> ERROR: (file: 'sstate_task_postfunc', lineno: 4, function: sstate_task_postfunc)
> ERROR: Function 'sstate_task_postfunc' failed
>
>
> Any ideas how to fix this?

Just to check, I applied the patches from Nitin's contrib tree
to poky/master and rebuilt - same results.  I used the sequence
   5b7e96d852778f1164198040cbd165241ea51e40..HEAD

>
>> *From:*yocto-bounces at yoctoproject.org [mailto:yocto-bounces at yoctoproject.org] *On Behalf Of *Diego Sueiro
>> *Sent:* Monday, January 31, 2011 10:53 AM
>> *To:* yocto at yoctoproject.org
>> *Subject:* [yocto] Kernel Panics on armv4t with gcc.4.5.1
>>
>> Folks,
>>
>> I'm not a kernel and neither a gcc expert developer, and after searching for a solution for the last 2 weeks I've decided to appeal to the list.
>>
>> I'm trying to build a kernel image (2.6.32 and 2.6.30) for mini2440 (armv4t) with Yocto Project (poky master branch) and I'm facing a strange issue.
>>
>> If I compile the kernel with Yocto gcc recipes (gcc 4.5.1) the kernel will panic on init (console printed message is attached for kernel 2.6.30 and 2.6.32).
>>
>> But, if I compile the kernel with meta-oe gcc recipes (gcc 4.5) everything will be ok.
>>
>> Just for your reference these is the gcc recipes which I'm using:
>>
>> http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-devtools/gcc
>>
>> http://git.openembedded.org/cgit.cgi/meta-openembedded/tree/recipes-devtools/gcc
>>
>> I've compiled with and without thumb instructions, but the issue remains.
>>
>> I've tried to apply the patches gcc-armv4-pass-fix-v4bx-to-ld.patch and gcc-arm-volatile-bitfield-fix.patch, but no success.
>>
>> Kind Regards,
>>
>> --
>>
>> *dS
>> Diego Sueiro
>>
>> /*long live rock 'n roll*/
>>
>>
>>
>> _______________________________________________
>> yocto mailing list
>> yocto at yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------



More information about the yocto mailing list