From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Parsing errors in current dev branch :(
Date: Wed, 26 Aug 2009 16:43:10 +0200 [thread overview]
Message-ID: <h73hlu$fls$1@ger.gmane.org> (raw)
In-Reply-To: <4A95468A.9080109@dresearch.de>
On 26-08-09 16:28, Steffen Sledz wrote:
>> git branch
> * org.openembedded.dev
>> git log | head -n 1
> commit 73b0cf99f965eeb5a08daf614b98fa6e23c1c848
>
> NOTE: Handling BitBake files: - (1265/7083) [17 %]ERROR: Could not include required file ../dvsdk/ti-dspbios.inc while parsing /home/DRESEARCH/sledz/work/openembedded/recipes/powervr-drivers/libgles-omap3_3.00.00.08.bb
> NOTE: Handling BitBake files: \ (1267/7083) [17 %]ERROR: Could not include required file ../dvsdk/ti-dspbios.inc while parsing /home/DRESEARCH/sledz/work/openembedded/recipes/powervr-drivers/libgles-omap3_3.00.00.06.bb
> ERROR: Could not include required file ../dvsdk/ti-dspbios.inc while parsing /home/DRESEARCH/sledz/work/openembedded/recipes/powervr-drivers/libgles-omap3_3.00.00.01.bb
> ERROR: Could not include required file ../dvsdk/ti-dspbios.inc while parsing /home/DRESEARCH/sledz/work/openembedded/recipes/powervr-drivers/libgles-omap3_3.00.00.05.bb
> NOTE: Handling BitBake files: \ (1271/7083) [17 %]ERROR: Could not include required file ../dvsdk/ti-dspbios.inc while parsing /home/DRESEARCH/sledz/work/openembedded/recipes/powervr-drivers/libgles-omap3_3.00.00.09.bb
> NOTE: Handling BitBake files: \ (7083/7083) [100 %]
> NOTE: Parsing finished. 6789 cached, 1 parsed, 288 skipped, 0 masked.
> ERROR: Parsing errors found, exiting...
That should be fixed now, sorry for the breakage. Note to self: to not
try to merge branches that move files around before drinking coffee.
next prev parent reply other threads:[~2009-08-26 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 14:28 Parsing errors in current dev branch :( Steffen Sledz
2009-08-26 14:43 ` Koen Kooi [this message]
2009-08-26 14:54 ` Steffen Sledz
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='h73hlu$fls$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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