* could not include bb file even though it exists and directory included in BBPATH
@ 2010-07-25 20:13 Ossy
2010-07-25 20:26 ` Frans Meulenbroeks
0 siblings, 1 reply; 6+ messages in thread
From: Ossy @ 2010-07-25 20:13 UTC (permalink / raw)
To: openembedded-devel
Dear oe mailinglist,
I tried to set up oe and the sanity checker hasn't reported any
anomalies. But when building a simple image, bitbake wasn't able to
include console-base-image.bb.
But in fact this file is present in oe/recipes/images/* and BBPATH
includes the path to oe (which hopefully dives into recipes there).
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?
Thanks for any hint.
Kind regards,
Marcus
ossy@debian-virtual:~/buildroot/kom-dockstar$ ll
insgesamt 0
drwxr-xr-x 4 ossy ossy 27 23. Jul 20:37 build
drwxr-xr-x 4 ossy ossy 53 23. Jul 00:11 conf
drwxr-xr-x 3 ossy ossy 19 23. Jul 00:11 recipes
ossy@debian-virtual:~/buildroot/kom-dockstar$ echo $BBPATH
/home/ossy/kom/openembedded/:/home/ossy/buildroot/kom-dockstar/build:/home/ossy/buildroot/kom-dockstar
ossy@debian-virtual:~/buildroot/kom-dockstar$ ll
/home/ossy/kom/openembedded/recipes/images/console-*
-rw-r--r-- 1 ossy ossy 416 23. Jul 02:34
/home/ossy/kom/openembedded/recipes/images/console-base-image.bb
-rw-r--r-- 1 ossy ossy 184 23. Jul 02:34
/home/ossy/kom/openembedded/recipes/images/console-image.bb
-rw-r--r-- 1 ossy ossy 168 23. Jul 02:34
/home/ossy/kom/openembedded/recipes/images/console-mipv6-image.bb
ossy@debian-virtual:~/buildroot/kom-dockstar$ kom -L
990 oe ${oe}/recipes/*/*.bb
1000 PRJDIR ${PRJDIR}/recipes/*/*.bb
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
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
NOTE: Parsing finished. 7606 cached, 474 parsed, 334 skipped, 176 masked.
ERROR: Parsing errors found, exiting...
ossy@debian-virtual:~/buildroot/kom-dockstar$ cat conf/bblayers.conf |
grep BBFILE
BBFILES = " \
BBFILE_COLLECTIONS = " oe PRJDIR"
BBFILE_PATTERN_PRJDIR = "${PRJDIR}/recipes"
BBFILE_PRIORITY_PRJDIR = "1000"
BBFILE_PATTERN_oe = "recipes/*/*.bb"
BBFILE_PRIORITY_oe = "990"
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: could not include bb file even though it exists and directory included in BBPATH
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
0 siblings, 1 reply; 6+ messages in thread
From: Frans Meulenbroeks @ 2010-07-25 20:26 UTC (permalink / raw)
To: openembedded-devel
2010/7/25 Ossy <ossy1980@gmx.net>
> Dear oe mailinglist,
>
> I tried to set up oe and the sanity checker hasn't reported any anomalies.
> But when building a simple image, bitbake wasn't able to include
> console-base-image.bb.
>
> But in fact this file is present in oe/recipes/images/* and BBPATH includes
> the path to oe (which hopefully dives into recipes there).
>
> 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?
>
> Thanks for any hint.
>
> Kind regards,
> Marcus
>
>
>
> ossy@debian-virtual:~/buildroot/kom-dockstar$ ll
> insgesamt 0
> drwxr-xr-x 4 ossy ossy 27 23. Jul 20:37 build
> drwxr-xr-x 4 ossy ossy 53 23. Jul 00:11 conf
> drwxr-xr-x 3 ossy ossy 19 23. Jul 00:11 recipes
> 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 ?
> ossy@debian-virtual:~/buildroot/kom-dockstar$ ll
> /home/ossy/kom/openembedded/recipes/images/console-*
> -rw-r--r-- 1 ossy ossy 416 23. Jul 02:34
> /home/ossy/kom/openembedded/recipes/images/console-base-image.bb
> -rw-r--r-- 1 ossy ossy 184 23. Jul 02:34
> /home/ossy/kom/openembedded/recipes/images/console-image.bb
> -rw-r--r-- 1 ossy ossy 168 23. Jul 02:34
> /home/ossy/kom/openembedded/recipes/images/console-mipv6-image.bb
> ossy@debian-virtual:~/buildroot/kom-dockstar$ kom -L
> 990 oe ${oe}/recipes/*/*.bb
> 1000 PRJDIR ${PRJDIR}/recipes/*/*.bb
> 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
good luck, Frans
> 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
>
> NOTE: Parsing finished. 7606 cached, 474 parsed, 334 skipped, 176 masked.
> ERROR: Parsing errors found, exiting...
>
> ossy@debian-virtual:~/buildroot/kom-dockstar$ cat conf/bblayers.conf |
> grep BBFILE
> BBFILES = " \
> BBFILE_COLLECTIONS = " oe PRJDIR"
> BBFILE_PATTERN_PRJDIR = "${PRJDIR}/recipes"
> BBFILE_PRIORITY_PRJDIR = "1000"
> BBFILE_PATTERN_oe = "recipes/*/*.bb"
> BBFILE_PRIORITY_oe = "990"
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: could not include bb file even though it exists and directory included in BBPATH
2010-07-25 20:26 ` Frans Meulenbroeks
@ 2010-07-26 18:39 ` Ossy
2010-07-26 19:15 ` Frans Meulenbroeks
0 siblings, 1 reply; 6+ messages in thread
From: Ossy @ 2010-07-26 18:39 UTC (permalink / raw)
To: openembedded-devel
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: could not include bb file even though it exists and directory included in BBPATH
2010-07-26 18:39 ` Ossy
@ 2010-07-26 19:15 ` Frans Meulenbroeks
2010-07-26 21:09 ` Ossy
0 siblings, 1 reply; 6+ messages in thread
From: Frans Meulenbroeks @ 2010-07-26 19:15 UTC (permalink / raw)
To: openembedded-devel
2010/7/26 Ossy <ossy1980@gmx.net>
> 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.
>
I don't know kom so can't say anything about that.
>
> 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.
>
The BBPATH itself isok, but your tmp dir should not be inside your overlay
dir.
I would expect TMPDIR to be something like /home/ossy/kom/tmp
>
> 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...)
>
If stagemanager cannot unpack something is probably wrong in your source
tree.
My recipes/stage-manager has:
rans@linux-suse:~/oe/openembedded/recipes/stage-manager> ls -lR
.:
total 8
drwxr-xr-x 2 frans users 4096 Jul 21 22:13 files
-rw-r--r-- 1 frans users 626 Jul 9 15:26 stagemanager-native_0.0.1.bb
./files:
total 48
-rwxr-xr-x 1 frans users 5215 Aug 23 2009 stage-manager
-rwxr-xr-x 1 frans users 28781 Jul 21 22:13 stage-manager-ipkg
-rwxr-xr-x 1 frans users 6217 Aug 23 2009 stage-manager-ipkg-build
You should have these as well. If not that is the root of your problem.
If you have these, then probably your TMPDIR points to a nonexisting place
(e.g. if it still points to .../build/tmp and you also removed build)
The TMPDIR itself will be created if needed, but the parent dir must exist
as far as I know.
>
> Thanks for the help anyway!
>
No problem.
We all once had to start with this and face issues like the one you have.
Frans.
>
> Kind regards,
> Marcus
>
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: could not include bb file even though it exists and directory included in BBPATH
2010-07-26 19:15 ` Frans Meulenbroeks
@ 2010-07-26 21:09 ` Ossy
2010-07-27 7:06 ` Frans Meulenbroeks
0 siblings, 1 reply; 6+ messages in thread
From: Ossy @ 2010-07-26 21:09 UTC (permalink / raw)
To: openembedded-devel
Am 26.07.2010 21:15, schrieb Frans Meulenbroeks:
>> 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...)
>>
>
> If stagemanager cannot unpack something is probably wrong in your source
> tree.
> My recipes/stage-manager has:
>
> rans@linux-suse:~/oe/openembedded/recipes/stage-manager> ls -lR
> .:
> total 8
> drwxr-xr-x 2 frans users 4096 Jul 21 22:13 files
> -rw-r--r-- 1 frans users 626 Jul 9 15:26 stagemanager-native_0.0.1.bb
>
> ./files:
> total 48
> -rwxr-xr-x 1 frans users 5215 Aug 23 2009 stage-manager
> -rwxr-xr-x 1 frans users 28781 Jul 21 22:13 stage-manager-ipkg
> -rwxr-xr-x 1 frans users 6217 Aug 23 2009 stage-manager-ipkg-build
>
> You should have these as well. If not that is the root of your problem.
> If you have these, then probably your TMPDIR points to a nonexisting place
> (e.g. if it still points to .../build/tmp and you also removed build)
I DO have the same file in recipes/stage-manager.
I set the tempdir to something outside my PRJDIR (overlay DIR).
The tmpdir outside fills when I run bitbake minimal-image, but I still
run into the an error:
NOTE: Running task 6 of 1092 (ID: 14,
/home/ossy/kom/openembedded/recipes/images/minimal-image.bb,
do_distribute_sources)
NOTE: Running task 7 of 1092 (ID: 306,
/home/ossy/kom/openembedded/recipes/stage-manager/stagemanager-native_0.0.1.bb,
do_unpack)
NOTE: Unpacking
../../kom/openembedded/recipes/stage-manager/files/stage-manager to
../tmp/work/x86_64-linux/stagemanager-native-0.0.1-r13/
NOTE: Unpacking
../../kom/openembedded/recipes/stage-manager/files/stage-manager-ipkg to
../tmp/work/x86_64-linux/stagemanager-native-0.0.1-r13/
NOTE: Unpacking
../../kom/openembedded/recipes/stage-manager/files/stage-manager-ipkg-build
to ../tmp/work/x86_64-linux/stagemanager-native-0.0.1-r13/
ERROR: Task 0
(/home/ossy/kom/openembedded/recipes/images/minimal-image.bb, do_unpack)
failed
NOTE: Waiting for 2 active tasks to finish
NOTE: 1: /home/ossy/kom/openembedded/recipes/images/minimal-image.bb,
do_distribute_sources (2247)
NOTE: 2:
/home/ossy/kom/openembedded/recipes/stage-manager/stagemanager-native_0.0.1.bb,
do_unpack (2248)
NOTE: Waiting for 1 active tasks to finish
NOTE: 1:
/home/ossy/kom/openembedded/recipes/stage-manager/stagemanager-native_0.0.1.bb,
do_unpack (2248)
NOTE: Tasks Summary: Attempted 4 tasks of which 0 didn't need to be
rerun and 1 failed.
ERROR: '/home/ossy/kom/openembedded/recipes/images/minimal-image.bb' failed
NOTE: oestats: build failed, see
http://tinderbox.openembedded.net/builds/79904/
Is there a problem with running multiple tasks? bitbake doesn't wait
correctly until the other task finishes? I'm running bitbake 1.8.18
Regards,
Marcus
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: could not include bb file even though it exists and directory included in BBPATH
2010-07-26 21:09 ` Ossy
@ 2010-07-27 7:06 ` Frans Meulenbroeks
0 siblings, 0 replies; 6+ messages in thread
From: Frans Meulenbroeks @ 2010-07-27 7:06 UTC (permalink / raw)
To: openembedded-devel
2010/7/26 Ossy <ossy1980@gmx.net>
> Am 26.07.2010 21:15, schrieb Frans Meulenbroeks:
>
>> 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...)
>>>
>>>
>> If stagemanager cannot unpack something is probably wrong in your source
>> tree.
>> My recipes/stage-manager has:
>>
>> rans@linux-suse:~/oe/openembedded/recipes/stage-manager> ls -lR
>> .:
>> total 8
>> drwxr-xr-x 2 frans users 4096 Jul 21 22:13 files
>> -rw-r--r-- 1 frans users 626 Jul 9 15:26 stagemanager-native_0.0.1.bb
>>
>> ./files:
>> total 48
>> -rwxr-xr-x 1 frans users 5215 Aug 23 2009 stage-manager
>> -rwxr-xr-x 1 frans users 28781 Jul 21 22:13 stage-manager-ipkg
>> -rwxr-xr-x 1 frans users 6217 Aug 23 2009 stage-manager-ipkg-build
>>
>> You should have these as well. If not that is the root of your problem.
>> If you have these, then probably your TMPDIR points to a nonexisting place
>> (e.g. if it still points to .../build/tmp and you also removed build)
>>
>
> I DO have the same file in recipes/stage-manager.
> I set the tempdir to something outside my PRJDIR (overlay DIR).
> The tmpdir outside fills when I run bitbake minimal-image, but I still run
> into the an error:
> NOTE: Running task 6 of 1092 (ID: 14,
> /home/ossy/kom/openembedded/recipes/images/minimal-image.bb,
> do_distribute_sources)
> NOTE: Running task 7 of 1092 (ID: 306,
> /home/ossy/kom/openembedded/recipes/stage-manager/
> stagemanager-native_0.0.1.bb, do_unpack)
> NOTE: Unpacking
> ../../kom/openembedded/recipes/stage-manager/files/stage-manager to
> ../tmp/work/x86_64-linux/stagemanager-native-0.0.1-r13/
> NOTE: Unpacking
> ../../kom/openembedded/recipes/stage-manager/files/stage-manager-ipkg to
> ../tmp/work/x86_64-linux/stagemanager-native-0.0.1-r13/
> NOTE: Unpacking
> ../../kom/openembedded/recipes/stage-manager/files/stage-manager-ipkg-build
> to ../tmp/work/x86_64-linux/stagemanager-native-0.0.1-r13/
> ERROR: Task 0 (/home/ossy/kom/openembedded/recipes/images/minimal-image.bb,
> do_unpack) failed
> NOTE: Waiting for 2 active tasks to finish
> NOTE: 1: /home/ossy/kom/openembedded/recipes/images/minimal-image.bb,
> do_distribute_sources (2247)
> NOTE: 2: /home/ossy/kom/openembedded/recipes/stage-manager/
> stagemanager-native_0.0.1.bb, do_unpack (2248)
> NOTE: Waiting for 1 active tasks to finish
> NOTE: 1: /home/ossy/kom/openembedded/recipes/stage-manager/
> stagemanager-native_0.0.1.bb, do_unpack (2248)
> NOTE: Tasks Summary: Attempted 4 tasks of which 0 didn't need to be rerun
> and 1 failed.
> ERROR: '/home/ossy/kom/openembedded/recipes/images/minimal-image.bb'
> failed
> NOTE: oestats: build failed, see
> http://tinderbox.openembedded.net/builds/79904/
>
>
> Is there a problem with running multiple tasks? bitbake doesn't wait
> correctly until the other task finishes? I'm running bitbake 1.8.18
>
mutlple tasks should not be a problem (I use that all the time), but if I
recall correctly it can be disabled in local.conf
Have you specified an absolute path to TMPDIR (e.g. /home/ossy/kom/tmp) ?
This part: ../tmp/work/x86_64-linux/stagemanager-native-0.0.1-r13/ does not
look good
(especially the ../tmp part of it).
Can you verify TMPDIR and probably also mention it in your previous mail.
If you want to you can also join #oe on freenode irc for faster feedback.
Frans
>
> Regards,
> Marcus
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2010-07-27 7:06 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2010-07-26 19:15 ` Frans Meulenbroeks
2010-07-26 21:09 ` Ossy
2010-07-27 7:06 ` Frans Meulenbroeks
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.