Re: [oe] What to do about the poor bitbake Quality Control?

2010-08-18 Thread Martyn Welch
On 17/08/10 16:02, Cliff Brake wrote: I think it would be very useful to have a "stable" branch that is only synchronised with dev when X number of targets build from a clean build. It seems like this would be high value, with little effort. Of course there will be corner things that break, but

Re: [oe] What to do about the poor bitbake Quality Control?

2010-08-17 Thread Cliff Brake
On Sun, Aug 15, 2010 at 11:38 PM, Gary Thomas wrote: > The biggest problem (as discussed at great length already) is that the > distance from 'dev' to 'stable' can be measured in years :-(  'stable' > just isn't useful at all for "current" work... I must admit that some percentage of the time I

Re: [oe] What to do about the poor bitbake Quality Control?

2010-08-15 Thread Gary Thomas
On 08/15/2010 03:22 PM, Koen Kooi wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 14-08-10 17:46, AJ ONeal wrote: This is about the 4th time that I've `rm -rf`-d everything and started from scratch and never yet got a working `bitbake omap3-console-image` That recipe isn't in OE, so i

Re: [oe] What to do about the poor bitbake Quality Control?

2010-08-15 Thread Gary Thomas
On 08/14/2010 01:01 PM, Frans Meulenbroeks wrote: 2010/8/14 AJ ONeal: This is about the 4th time that I've `rm -rf`-d everything and started from scratch and never yet got a working `bitbake omap3-console-image` Every time I `git pull` it's a different set of problems. It's never the same packa

Re: [oe] What to do about the poor bitbake Quality Control?

2010-08-15 Thread Koen Kooi
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 14-08-10 17:46, AJ ONeal wrote: > This is about the 4th time that I've `rm -rf`-d everything and started from > scratch and never yet got a working `bitbake omap3-console-image` That recipe isn't in OE, so it seems you're building from what we call

Re: [oe] What to do about the poor bitbake Quality Control?

2010-08-15 Thread Frans Meulenbroeks
2010/8/14 AJ ONeal : > How do I enable logging to tenderbox? I'd be happy to do that. > I googled it to little avail: > http://www.google.com/search?hl=en&q=tinderbox+openembedded Add this to your local.conf: INHERIT += "oestats-client" OESTATS_SERVER = "tinderbox.openembedded.net" OESTATS_BUILDE

Re: [oe] What to do about the poor bitbake Quality Control?

2010-08-14 Thread AJ ONeal
How do I enable logging to tenderbox? I'd be happy to do that. I googled it to little avail: http://www.google.com/search?hl=en&q=tinderbox+openembedded For reference, here's the process I've been following: rm ~/overo-oe -rf # *clean it all out* mkdir -p ~/overo-oe cd ~/overo-

Re: [oe] What to do about the poor bitbake Quality Control?

2010-08-14 Thread Elvis Dowson
Hi, On Aug 14, 2010, at 11:14 PM, Philip Balister wrote: > On 08/14/2010 12:01 PM, Frans Meulenbroeks wrote: >> 2010/8/14 AJ ONeal: >>> This is about the 4th time that I've `rm -rf`-d everything and started from >>> scratch and never yet got a working `bitbake omap3-console-image` >>> >>> Every

Re: [oe] What to do about the poor bitbake Quality Control?

2010-08-14 Thread Philip Balister
On 08/14/2010 12:01 PM, Frans Meulenbroeks wrote: 2010/8/14 AJ ONeal: This is about the 4th time that I've `rm -rf`-d everything and started from scratch and never yet got a working `bitbake omap3-console-image` Every time I `git pull` it's a different set of problems. It's never the same packa

Re: [oe] What to do about the poor bitbake Quality Control?

2010-08-14 Thread Frans Meulenbroeks
2010/8/14 Frans Meulenbroeks : > > If you are using dev head, you're living on the edge. If you can't > stand that better use the stable branch. > > As far as there are issues: > Either report them, or better fix them. > (or as a workaround you could find the commit wthat broke it and > report tha

Re: [oe] What to do about the poor bitbake Quality Control?

2010-08-14 Thread Frans Meulenbroeks
2010/8/14 AJ ONeal : > This is about the 4th time that I've `rm -rf`-d everything and started from > scratch and never yet got a working `bitbake omap3-console-image` > > Every time I `git pull` it's a different set of problems. It's never the > same package twice, but they never all compile for th

Re: [oe] What to do about the poor bitbake Quality Control?

2010-08-14 Thread J. L.
Right on thanks that does seem to answer a couple questions I have come across so far especially the devshell. I will give making my recipe another shot again today and see if I can get further with it or even crazier get it to build correctly. Thanks again hopefully we will see some other input to

Re: [oe] What to do about the poor bitbake Quality Control?

2010-08-14 Thread AJ ONeal
I've been compiling some common general issues http://fastr.github.com/articles/Troubleshooting-bitbake.html Here's some quick-n-dirty instructions akin to using devshell: 1. cd ${OVEROTOP}/tmp/work/${ARCH}/${PACKAGE}_${VER}_r${REV}/${BUILD} - ${ARCH} is probably armv7a-angstrom-linux-g

Re: [oe] What to do about the poor bitbake Quality Control?

2010-08-14 Thread J. L.
I agree with you AJ, its become a serious pain to just get a built image. I myself have only built once completely and have yet to again since figuring out the changes I needed to make to that image. I would like to help myself but someone like me whose not very competent in this area finds the doc

[oe] What to do about the poor bitbake Quality Control?

2010-08-14 Thread AJ ONeal
This is about the 4th time that I've `rm -rf`-d everything and started from scratch and never yet got a working `bitbake omap3-console-image` Every time I `git pull` it's a different set of problems. It's never the same package twice, but they never all compile for the basic console image anywhere