From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Cc: gumstix-users@lists.sourceforge.net
Subject: Re: What to do about the poor bitbake Quality Control?
Date: Sun, 15 Aug 2010 23:22:15 +0200 [thread overview]
Message-ID: <i49lq7$jft$1@dough.gmane.org> (raw)
In-Reply-To: <AANLkTi=gYuoD-3RO=c5GpEbOZoHsAJOijrXXGnzcdNe9@mail.gmail.com>
-----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
"some random tree", which is unsupported. Complain to the people in
charge of that tree and tell them to fix things.
If people don't care enough to get there stuff upstream, upstream won't
care about problems in that tree.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFMaFqHMkyGM64RGpERAnigAJ9sMzq5aph9ONHXjOc016N26xNvFwCgs2XJ
GeX7r5WwkbKeoGi3rSShMdk=
=miVm
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-08-15 21:22 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
2010-08-17 15:02 ` Cliff Brake
2010-08-18 8:30 ` Martyn Welch
2010-08-15 21:22 ` Koen Kooi [this message]
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='i49lq7$jft$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.