Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: "Purdie, Richard" <richard.purdie@intel.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: About bitbake-runtask
Date: Tue, 9 Aug 2011 17:29:33 +0800	[thread overview]
Message-ID: <4E40FDFD.3060809@windriver.com> (raw)

Hi Richard,

The bitbake-runtask doesn't work currently, it seems that we have decommissioned it:

commit 1f3e313fd5cc5ae8ea838bf8fcdedace3cb72584
Author: Richard Purdie <rpurdie@linux.intel.com>
Date:   Wed Dec 8 00:08:04 2010 +0000

     bitbake Revert bitbake exec() and go back to fork() for performace wins 
(first draft)

But it is still in bitbake/bin/bitbake-runtask. There is a bug for tracking
this, what shall we do for it? Remove the bitbake-runtask or fix it and make
it work?

Bug 1229 - bitbake-runtask doesn't work in both 1.0.1 and 1.1

-- 
Thanks

Robert



             reply	other threads:[~2011-08-09 11:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-09  9:29 Robert Yang [this message]
2011-08-11 19:24 ` About bitbake-runtask Richard Purdie
2011-08-16  8:27   ` Robert Yang

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=4E40FDFD.3060809@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=richard.purdie@intel.com \
    /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