OpenEmbedded - Random Source Corruption

[blakeyez]

Hi all

I have been playing with openembedded the past few days, trying to see if I can get it to at least build a workable image which I can then play with and customize.

However, in the process of building, it seems that the source for various packages gets corrupted along the way.  It has happened twice now building gcc (once on the 'gcc-cross-initial' package and once on 'gcc-cross'), and once on ipkg.  The compile fails with various error messages centering around 1 or 2 lines in a specific file, complaining about various things being undefined.  When I look at the file that the compile fails on, the line above the one that's being complained about always has a string of about 50 occurences of '^@^@^@^@".  This seems to happen on random lines, in random files.  I haven't dug deep enough to find out whether those lines are ones modified by the various oe patches for these packages, but in any case this corruption is a PAIN.

I still haven't figured out how to consistently force a complete rebuild of the package that errors out (including re-downloading the source, extracting it, patching it then building) without deleting my entire build directory first.  So each time it's just trial-and-error, which is not a good situation.

Has anyone else experienced this problem?  Any advice?

TIA
Dave

[blakeyez]

Ok, so I have found a bit of a workaround for now.  I must have been blind and missed the 'stamps' dir in my build directory, but after deleting the stamps for the failing package, along with its work directory, I am usually able to get past the point where it breaks.

It seems as if the patches (or the patcher itself) are causing the corruption but I can't see why...

I'll keep playing, here, and see what I come up with.

Dave

[blakeyez]

I have *finally* been able to successfully create a complete image (not tested yet ) via OpenEmbedded.  I am quite impressed with the build system, despite my little issue with corrupted source code.

In this most recent build attempt, three packages failed (fakeroot, perl, and firefox), and all three had two things in common.  THey all have patches applied by the OE build system, and they all ended up with a string of ^@ characters in the file that failed to parse.  However, if I deleted the build/tmp/work/[packagename] directory, along with all the build/tmp/stamps/[packagename].do_* files, and re-issued the 'oemake gpe-image' command, the build would go without a hitch.  I never had a reoccurrance of the same issue on the same package when I followed this procedure.

There is something very odd at work here - either that or someone really doesn't want me building custom images!

Any OE developers want to pipe up on this subject?

Dave

[Mickeyl]

Use oe@handhelds.org for OE support. Let's at least one time try not to fragment information.

[blakeyez]

Ok, sorry about that, wasn't 100% sure where to post .

I'll drop a mail off to that list.

Dave

[dino]

Ok, sorry about that, wasn't 100% sure where to post .

I was guilty of doing the same last week.  I've found the OE Mailing List list  quick to respond and very helpful.

Mailing Address: oe@handhelds.org

To subscribe send and mail to oe-request@handhelds.org with "subscribe" in the subject line or use the web subscription form at https://handhelds.org/mailman/listinfo/oe