Re: [Gumstix-users] OpenEmbedded broken?

[j <vwy...@gm...>]

On 04/07/2012 10:34 AM, Patrik Svensson wrote:
>
> Have tried for a number of weeks now to build the simplest 
> console-image with ubuntu 11.10 according to instructions.
>
> First it failed with openssl which there was a cure for with a library 
> depend.
>
> Then it could not find correct kernel  404 error and so on.
>
> Was thinking of maybe switch to another build system maybe android, 
> guess number of users count.
>
> Anybody tried Texas Instrument Android kit for 2.3?
>
> // Patrik
>
>
>
> ------------------------------------------------------------------------------
> For Developers, A Lot Can Happen In A Second.
> Boundary is the first to Know...and Tell You.
> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
> http://p.sf.net/sfu/Boundary-d2dvs2
>
>
> _______________________________________________
> gumstix-users mailing list
> gum...@li...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users

I cant get a successful build on the stable gumstix branch with 11.10. 
10.04 or 11.04 have been the only ones I have had any success in. Though 
11.10 builds for me if you setup the new layered approach but you can 
also loose packages by going to the newer branches, so make sure you do 
not loose something you need first.

404's, file not found, failed to fetch, invalid checksums are all 
standard in the builds with stable gumstix OE, and you need to get use 
to them until you get things tweaked for your system. There seems to be 
changes many do locally, I know on my 10.04 build machine there were a 
few changes to source to make it actually build and complete an image, 
tried asking for others to post changes they have made locally but no 
one chimed in, was hoping to get some patches or something pushed so 
stable gumstix gets some updates, to eliminate issues that it should not 
continuously run into like checksum issues and so on. I honestly feel 
10.04 is your best OS to try and build that branch and get everything 
you need.

Also the failures, make sure you clean them and then start the package 
build again, only building the failures and see if they just need 
individual coaxing. (bitbake -c clean FailedRecipe; bitbake 
FailedRecipie). I also will do my first build with the -k option so it 
will continue as far as it can before crapping out, that way you can get 
everything that builds out of the way and only focus on failures. 
Sometimes I can get 404's on multiple try's then it will just work 
automagically. I have moved to the layered method and am much happier in 
the way it builds and the ease of the builds. But moving needed 
packages/programs over has proven to be a PIA for myself at least. I 
have never used Android on my overo's nor do I plan to. But OE is the 
easiest to get things working fully, ArchArmLinux is my fav OS at this 
point on overo's, though it is not without its own downfalls, and you 
have to patch their kernel to actually fully accommodate the overo, as 
they say they "support" it but its more like it just boots and happens 
to work for the most part, not actually fully supported, and not 
actively making changes to accommodate overo's even after offering 
patches I made and used to get a fully working install and all things 
recognized and functioning as they should, but no response from dev's, 
they seem more concerned with pogoplugs and similar types devices. 
Other's enjoy Debian/Ubuntu/Linario choices.

HTH and is not to much of a ramble, hate waiting for flights :p