From: Richard Purdie <rpurdie@linux.intel.com>
To: "Kamble, Nitin A" <nitin.a.kamble@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: strange bitbake error
Date: Wed, 08 Dec 2010 10:35:01 +0000 [thread overview]
Message-ID: <1291804501.1554.264.camel@rex> (raw)
In-Reply-To: <9DA5872FEF993D41B7173F58FCF6BE940254AA53@orsmsx504.amr.corp.intel.com>
Hi Nitin,
On Tue, 2010-12-07 at 19:15 -0800, Kamble, Nitin A wrote:
> I am getting following bitbake error. I also tried passing –D option
> to bitbake, but I did not find anything useful. Also bellow is the
> change which is causing this error.
>
> I don’t see anything oblivious here. As I understand just changing the
> recipe from cvs to git src_uri has caused this issue.
Its probably exactly this change the breaks things. git SRC_URIs have a
dependency on git-native. git-native probably depends on
gnu-config-native indirectly. The end result is a circular dependency.
Bitbake tried to work this out but obviously got lost in the circular
logic.
It did try and warn you with:
"""
> ERROR: Unbuildable tasks were found.
>
> These are usually caused by circular dependencies and any circular
> dependency chains found will be printed below. Increase the debug
> level to see a list of unbuildable tasks.
"""
Cheers,
Richard
next prev parent reply other threads:[~2010-12-08 10:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 3:15 strange bitbake error Kamble, Nitin A
2010-12-08 10:35 ` Richard Purdie [this message]
2010-12-08 16:29 ` Kamble, Nitin A
2010-12-08 17:46 ` Richard Purdie
2010-12-09 0:31 ` Kamble, Nitin A
-- strict thread matches above, loose matches on Subject: below --
2017-01-25 6:50 Strange " Gary Thomas
2017-01-25 7:05 ` 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=1291804501.1554.264.camel@rex \
--to=rpurdie@linux.intel.com \
--cc=nitin.a.kamble@intel.com \
--cc=yocto@yoctoproject.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.