All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: About bitbake-runtask
Date: Tue, 16 Aug 2011 16:27:01 +0800	[thread overview]
Message-ID: <4E4A29D5.4000801@windriver.com> (raw)
In-Reply-To: <1313090662.14274.466.camel@rex>

Hi experts,

I'm trying to fix it, but it seems it's not easy for me to finish it
by Aug. 24th, it would be great if anyone can help me.

The bug is:

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

Thank you very much!

// Robert

On 08/12/2011 03:24 AM, Richard Purdie wrote:
> On Tue, 2011-08-09 at 17:29 +0800, Robert Yang wrote:
>> 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
>
> Since I know that script has user and a valid use case we need to:
>
> a) Fix this to work after the fork() changes
> b) Include it in bitbake upstream
>
> b) never happened due to a).
>
> Cheers,
>
> Richard
>
>
>
>



      reply	other threads:[~2011-08-16  8:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-09  9:29 About bitbake-runtask Robert Yang
2011-08-11 19:24 ` Richard Purdie
2011-08-16  8:27   ` Robert Yang [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=4E4A29D5.4000801@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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.