Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: core-image-sato fetchall fail due to circular dependency
Date: Wed, 18 Jul 2012 14:36:20 +0100	[thread overview]
Message-ID: <1342618580.513.4.camel@ted> (raw)
In-Reply-To: <CAF1ZMEdcbw78ViHnxiFH2BY4rweS8nzQoTG_=5EcUTjqPw8G+g@mail.gmail.com>

On Wed, 2012-07-18 at 11:27 +0800, Dennis.Yxun wrote:
> hi ALL:
>  hit following error, any ideas?
> 
> Dennis
> 
>  $ bitbake -c fetchall core-image-sato
> Parsing recipes: 100% |#########################################| Time: 00:00:38
> Parsing of 833 .bb files complete (0 cached, 833 parsed). 1132
> targets, 19 skipped, 0 masked, 0 errors.
> 
> Build Configuration:
> BB_VERSION        = "1.15.2"
> TARGET_ARCH       = "i586"
> TARGET_OS         = "linux"
> MACHINE           = "qemux86"
> DISTRO_VERSION    = "oe-core.0"
> TUNE_FEATURES     = "m32 i586"
> TARGET_FPU        = ""
> meta              = "master:2bd0aaf98c5d586638d82f5f22c1c24122a889a3"
> 
> NOTE: Resolving any missing task queue dependencies
> NOTE: Preparing runqueue
> ERROR: Task /mnt/work/oe/oe-core/meta/recipes-core/ncurses/ncurses_5.9.bb
> (do_fetchall) has circular dependency on
> /mnt/work/oe/oe-core/meta/recipes-core/eglibc/eglibc_2.15.bb
> (do_fetchall)
> 
> Summary: There was 1 ERROR message shown, returning a non-zero exit code.

Try updating bitbake. I'm not seeing that error here...

Cheers,

Richard




      reply	other threads:[~2012-07-18 13:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-18  3:27 core-image-sato fetchall fail due to circular dependency Dennis.Yxun
2012-07-18 13:36 ` Richard Purdie [this message]

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=1342618580.513.4.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@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