All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Poky <poky@lists.pokylinux.org>
Subject: Re: bitbake listtasks broken
Date: Thu, 25 Nov 2010 04:38:06 -0700	[thread overview]
Message-ID: <4CEE4A9E.6030107@mlbassoc.com> (raw)
In-Reply-To: <4CEE4347.1070700@mlbassoc.com>

On 11/25/2010 04:06 AM, Gary Thomas wrote:
> Filed as bug #548
>
> This command [no longer?] produces any output:
> bitbake recipe -c listtasks
>
> $ bitbake qemu -c listtasks
> NOTE: Handling BitBake files: | (0756/0756) [100 %]
> Parsing of 756 .bb files complete (0 cached, 756 parsed). 913 targets, 34 skipped, 0 masked, 0 errors.
>
> OE Build Configuration:
> BB_VERSION = "1.11.0"
> METADATA_BRANCH = "local_master"
> METADATA_REVISION = "94b1fda09671b58aafb54983e4a6e499f6ffc369"
> TARGET_ARCH = "i586"
> TARGET_OS = "linux"
> MACHINE = "qemux86"
> DISTRO = "poky"
> DISTRO_VERSION = "0.9+snapshot-20101125"
> TARGET_FPU = ""
>
> NOTE: Resolving any missing task queue dependencies
> NOTE: Preparing runqueue
> NOTE: Executing runqueue
> NOTE: Full skip list set([])
> NOTE: Running task 1 of 1 (ID: 0, /tmp/poky-amltd/meta/recipes-devtools/qemu/qemu_0.12.4.bb, do_listtasks)
> NOTE: package qemu-0.12.4-r22: task do_listtasks: Started
> NOTE: package qemu-0.12.4-r22: task do_listtasks: Succeeded
> NOTE: Tasks Summary: Attempted 1 tasks of which 0 didn't need to be rerun and 0 failed.

To be fair, it does do something, but the results are hidden in
the temp/log.do_listtasks file.  Certainly not what the documentation
implies...

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


  reply	other threads:[~2010-11-25 11:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-25 11:06 bitbake listtasks broken Gary Thomas
2010-11-25 11:38 ` Gary Thomas [this message]
2010-11-26  2:29   ` Tian, Kevin
2010-11-28 15:42     ` Richard Purdie

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=4CEE4A9E.6030107@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=poky@lists.pokylinux.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.