From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Cc: "General mailing list for gumstix users."
<gumstix-users@lists.sourceforge.net>
Subject: Re: What to do about the poor bitbake Quality Control?
Date: Sun, 15 Aug 2010 21:38:45 -0600 [thread overview]
Message-ID: <4C68B2C5.5030908@mlbassoc.com> (raw)
In-Reply-To: <AANLkTim_u5O3bLgdLiwE4fPCnbjRoUY1+Pad9iB8qXPW@mail.gmail.com>
On 08/14/2010 01:01 PM, Frans Meulenbroeks wrote:
> 2010/8/14 AJ ONeal<coolaj86@gmail.com>:
>> 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 from 4 to 20 hours in.
>>
>> Fortunately, I do have a machine that did build omap3-console-image a few
>> weeks ago at work. But I've never been able to get it on my machine at home
>> (same os) to start playing around with.
>>
>> What needs to happen in order for things to git checked that they work with
>> at least a few common meta-tasks before being pushed out?
>> And is there anything I can do to help? (Donate some machine time to run
>> tests, for example)
>>
>>
>> Obviously, we all have our day jobs and whatnot, but this is becoming really
>> frustrating for me and I'd like to see things improve.
>>
>
> If you are using dev head, you're living on the edge. If you can't
> stand that better use the stable branch.
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...
> 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 that and perhaps temporariy locally revert that commit if you
> cannot fix it).
>
> Having said that:
> I don't really see many issues. Maybe I'm building a different set of
> packages or for a different set of hw or for a different distro.
Turning a blind eye, I would say. I (and others) have nearly 0%
success building any Angstrom image on an x86_64 based host. I've tried
the latest Ubuntu and Fedora - neither works, both yield different failures.
At least I have i686 build hosts to fall back on, but there are issues there
as well.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2010-08-16 3:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-14 15:46 What to do about the poor bitbake Quality Control? AJ ONeal
2010-08-14 16:16 ` J. L.
2010-08-14 17:06 ` AJ ONeal
2010-08-14 18:19 ` J. L.
2010-08-14 19:01 ` Frans Meulenbroeks
2010-08-14 19:04 ` Frans Meulenbroeks
2010-08-14 21:53 ` AJ ONeal
2010-08-15 7:27 ` Frans Meulenbroeks
2010-08-14 19:14 ` Philip Balister
2010-08-14 21:08 ` Elvis Dowson
2010-08-16 3:38 ` Gary Thomas [this message]
2010-08-17 15:02 ` Cliff Brake
2010-08-18 8:30 ` Martyn Welch
2010-08-15 21:22 ` Koen Kooi
2010-08-16 3:39 ` Gary Thomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C68B2C5.5030908@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=gumstix-users@lists.sourceforge.net \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox