Error running bitbake with a fresh copy of OE-Core

Error running bitbake with a fresh copy of OE-Core

[Samuel Stirtzel]

[-- Attachment #1: Type: text/plain, Size: 2909 bytes --]

After setting up OE-Core like described in the Angstrom instructions (
http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/metaA--angstrom/tree/README<http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-angstrom/tree/README>
),
and running Bitbake console-image the following error occurs:

ERROR: Error executing a python function in
> /home/*user*/oe-core/setup-scripts/sources/meta-openembedded/meta-oe/recipes-devtools/gcc/
> gcc-cross-initial_4.5.bb:
> IOError: [Errno 36] File name too long:
> '/home/*user*/oe-core/setup-scripts/build/sstate-cache/sstate-gcc-cross-initial-armv5te-angstrom-linux-gnueabi-4.5-r39.0+svnr175127-x86_64_armv5te-2-1ce8da5cb101acb651e00e9a2c94ecde_populate-lic.tgz.siginfo'
> 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 7, in sstate_task_postfunc
> ERROR:
> ERROR:   File "sstate.bbclass", line 56, in sstate_package
> ERROR:
> ERROR:   File
> "/home/*user*/oe-core/setup-scripts/sources/bitbake/lib/bb/siggen.py", line
> 218, in dump_this_task
> ERROR:     bb.parse.siggen.dump_sigtask(fn, task, outfile, "customfile")
> ERROR:
> ERROR:   File
> "/home/*user*/oe-core/setup-scripts/sources/bitbake/lib/bb/siggen.py", line
> 189, in dump_sigtask
> ERROR:     p = pickle.Pickler(file(sigfile, "wb"), -1)
> 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:      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:      0009:
> ERROR:      0010:sstate_task_postfunc(d)
> ERROR:      0011:
> ERROR: (file: 'sstate_task_postfunc', lineno: 7, function:
> sstate_task_postfunc)
> ERROR: Function 'sstate_task_postfunc' failed
> ERROR: Logfile of failure stored in:
> /home/*user*/oe-core/tmp-eglibc/work/armv5te-angstrom-linux-gnueabi/gcc-cross-initial-4.5-r39.0+svnr175127/temp/log.do_populate_lic.12160


To provide further informations:
Currently building with MACHINE ?= "tx28"
The Bitbake procedure was reapeated with another machine configuration
(MACHINE ?= "beagleboard") and the same error showed up (respectively the
ARM version changed accordingly).

I also cleaned the temp and build directories, but with the same result,
help would be appreciated.


Regards
--Samuel

[-- Attachment #2: Type: text/html, Size: 3550 bytes --]

Re: Error running bitbake with a fresh copy of OE-Core

[Koen Kooi]

Op 14 jul 2011, om 10:52 heeft Samuel Stirtzel het volgende geschreven:

> File name too long: '/home/*user*/oe-core/setup-scripts/build/sstate-cache/sstate-gcc-cross-initial-armv5te-angstrom-linux-gnueabi-4.5-r39.0+svnr175127-x86_64_armv5te-2-1ce8da5cb101acb651e00e9a2c94ecde_populate-lic.tgz.siginfo'

That seems to be filesystem related, I know ext3, ext4 and xfs work fine, which one are you using?

Re: Error running bitbake with a fresh copy of OE-Core

[Paul Eggleton]

On Thursday 14 July 2011 10:25:28 Koen Kooi wrote:
> Op 14 jul 2011, om 10:52 heeft Samuel Stirtzel het volgende geschreven:
> > File name too long:
> > '/home/*user*/oe-core/setup-scripts/build/sstate-cache/sstate-gcc-cross-
> > initial-armv5te-angstrom-linux-gnueabi-4.5-r39.0+svnr175127-x86_64_armv5t
> > e-2-1ce8da5cb101acb651e00e9a2c94ecde_populate-lic.tgz.siginfo'
> 
> That seems to be filesystem related, I know ext3, ext4 and xfs work fine,
> which one are you using?

ecryptfs (encrypted home directory) perhaps? I thought we had a check for long 
filename creation in sanity.bbclass, maybe it isn't being tripped here for some 
reason...

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: Error running bitbake with a fresh copy of OE-Core

[Samuel Stirtzel]

[-- Attachment #1: Type: text/plain, Size: 1069 bytes --]

2011/7/14 Paul Eggleton <paul.eggleton@linux.intel.com>

> On Thursday 14 July 2011 10:25:28 Koen Kooi wrote:
> > Op 14 jul 2011, om 10:52 heeft Samuel Stirtzel het volgende geschreven:
> > > File name too long:
> > >
> '/home/*user*/oe-core/setup-scripts/build/sstate-cache/sstate-gcc-cross-
> > >
> initial-armv5te-angstrom-linux-gnueabi-4.5-r39.0+svnr175127-x86_64_armv5t
> > > e-2-1ce8da5cb101acb651e00e9a2c94ecde_populate-lic.tgz.siginfo'
> >
> > That seems to be filesystem related, I know ext3, ext4 and xfs work fine,
> > which one are you using?
>
> ecryptfs (encrypted home directory) perhaps? I thought we had a check for
> long
> filename creation in sanity.bbclass, maybe it isn't being tripped here for
> some
> reason...
>
> Cheers,
> Paul
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre
>

The filesystem of this pc is ext4 with encrypted home directory, so moving
my OE-Core directory out of my home directory could resolve my problems?
I will try this and write back if it worked.


Regards
--Samuel

[-- Attachment #2: Type: text/html, Size: 1695 bytes --]

Re: Error running bitbake with a fresh copy of OE-Core

[Samuel Stirtzel]

[-- Attachment #1: Type: text/plain, Size: 1425 bytes --]

2011/7/14 Samuel Stirtzel <s.stirtzel@googlemail.com>

>
>
> 2011/7/14 Paul Eggleton <paul.eggleton@linux.intel.com>
>
>> On Thursday 14 July 2011 10:25:28 Koen Kooi wrote:
>> > Op 14 jul 2011, om 10:52 heeft Samuel Stirtzel het volgende geschreven:
>> > > File name too long:
>> > >
>> '/home/*user*/oe-core/setup-scripts/build/sstate-cache/sstate-gcc-cross-
>> > >
>> initial-armv5te-angstrom-linux-gnueabi-4.5-r39.0+svnr175127-x86_64_armv5t
>> > > e-2-1ce8da5cb101acb651e00e9a2c94ecde_populate-lic.tgz.siginfo'
>> >
>> > That seems to be filesystem related, I know ext3, ext4 and xfs work
>> fine,
>> > which one are you using?
>>
>> ecryptfs (encrypted home directory) perhaps? I thought we had a check for
>> long
>> filename creation in sanity.bbclass, maybe it isn't being tripped here for
>> some
>> reason...
>>
>> Cheers,
>> Paul
>>
>> --
>>
>> Paul Eggleton
>> Intel Open Source Technology Centre
>>
>
> The filesystem of this pc is ext4 with encrypted home directory, so moving
> my OE-Core directory out of my home directory could resolve my problems?
> I will try this and write back if it worked.
>
>
> Regards
> --Samuel
>

After moving the directory and changing the config files and the
~/.oe/environment-oecore script accordingly, Bitbake is now running smoothly
and the error disappeared.
Thank you for helping me with this problem.



Regards
--Samuel

[-- Attachment #2: Type: text/html, Size: 2290 bytes --]