From: Ossy <ossy1980@gmx.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: could not include bb file even though it exists and directory included in BBPATH
Date: Mon, 26 Jul 2010 20:39:31 +0200 [thread overview]
Message-ID: <4C4DD663.1070902@gmx.net> (raw)
In-Reply-To: <AANLkTinQG5SA2sGRj1xapuhfDCxQF4Sss7BHeS=nLesA@mail.gmail.com>
Am 25.07.2010 22:26, schrieb Frans Meulenbroeks:
> 2010/7/25 Ossy<ossy1980@gmx.net>
>
>> I used kom to setup a new overlay project. Since listing the images gives
>> all images in oe, I'm sure that bitbake has access to those bb-files. The
>> conf/bbplayers.conf includes BBFILES to oe, too.
>>
>> Where may I misconfigured the setup?
>>
>> ossy@debian-virtual:~/buildroot/kom-dockstar$ echo $BBPATH
>>
>> /home/ossy/kom/openembedded/:/home/ossy/buildroot/kom-dockstar/build:/home/ossy/buildroot/kom-dockstar
>>
>
> Why do you have the last two paths ?
I used kom to setup an overlay. My current understanding is, that I can
start up with an "empty" overlay which initially links to oe. In the
future I will overwrite some settings and package defintions with
"local" (user defined overlay) definitions.
Correct me if I'm completly wrong. After reading some tutorials and
discovering the mailinglist. I thought, defining
OE_BBDIR+MYSPECIAL_BBDIR is a valid way.
>> ossy@debian-virtual:~/buildroot/kom-dockstar$ bitbake minimal-image
>> NOTE: Handling BitBake files: \ (8414/8416) [99 %]ERROR: Could not include
>> required file console-base-image.bb while parsing
>> /home/ossy/buildroot/kom-dockstar/build/tmp/deploy/glibc/sources/MIT/console-image/
>> console-image.bb
>>
>
> This suggests hat it is parsing a console-image.bb file which resides in
> your tmp/deploy dir.
> (and not the one in recipes/images).
> No idea how it ended up there. I suggest to clean at least that file, but
> preferably the whole tmp dir and build from scratch
Yepp. That helped: rm -r build/tmp
Unfortunatly I'm still not able to create a minimal-image:
ERROR: Task 306
(/home/ossy/kom/openembedded/recipes/stage-manager/stagemanager-native_0.0.1.bb,
do_unpack) failed
I guess the stagemanager is an essential tool and should be well tested.
So were can I find some output which action went wrong?
(unpacking seems not that difficult to fail...)
Thanks for the help anyway!
Kind regards,
Marcus
next prev parent reply other threads:[~2010-07-26 18:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-25 20:13 could not include bb file even though it exists and directory included in BBPATH Ossy
2010-07-25 20:26 ` Frans Meulenbroeks
2010-07-26 18:39 ` Ossy [this message]
2010-07-26 19:15 ` Frans Meulenbroeks
2010-07-26 21:09 ` Ossy
2010-07-27 7:06 ` Frans Meulenbroeks
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=4C4DD663.1070902@gmx.net \
--to=ossy1980@gmx.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.