From: Jamie Lenehan <lenehan@twibble.org>
To: Nicolas FR <nicolasfr@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: Bitbaking a recipe which refers to a missing bbclass
Date: Wed, 11 Oct 2006 08:06:01 +1000 [thread overview]
Message-ID: <20061010220601.GA20799@twibble.org> (raw)
In-Reply-To: <b9481e140610100631u25d9bc4dm7f6483c20e3c482d@mail.gmail.com>
On Tue, Oct 10, 2006 at 03:31:42PM +0200, "Nicolas FR" wrote:
> Hi,
>
> I have noticed that when bitbaking a recipe which refers to a missing
> .bbclass definition, there where no warning / error.
I've noticed the same thing and I agree that it's rather annoying.
I'd much rather it fail then continue on and do something else.
--
Jamie Lenehan <lenehan@twibble.org>
next prev parent reply other threads:[~2006-10-10 22:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-10 13:31 Bitbaking a recipe which refers to a missing bbclass Nicolas FR
2006-10-10 22:06 ` Jamie Lenehan [this message]
2006-10-10 22:44 ` Justin Patrin
2006-10-13 10:46 ` Michael 'Mickey' Lauer
2006-10-13 10:53 ` Nicolas FR
2006-10-14 2:07 ` Jamie Lenehan
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=20061010220601.GA20799@twibble.org \
--to=lenehan@twibble.org \
--cc=nicolasfr@gmail.com \
--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