Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Subject: Re: [PATCH 1/1] base.bbclass: Use bb.event.ParseStarted for HOSTTOOLS
Date: Wed, 30 Jan 2019 17:06:15 +0800	[thread overview]
Message-ID: <9c2e4334-e452-6ca4-f7ef-5845c5abae52@windriver.com> (raw)
In-Reply-To: <8b20fa4c993e073ec37b0fd6c309a52c4939959c.1548667130.git.liezhi.yang@windriver.com>

Sorry, this patch doesn't work, it breaks fresh  build's sanity check since
the hosttools are bot ready when run sanity check.

ERROR:  OE-core's config sanity checker detected a potential misconfiguration.
     Either fix the cause of this error or at your own risk disable the checker 
(see sanity.conf).
     Following is the list of potential problems / advisories:

     Please install the following missing utilities: GNU make,C Compiler (gcc 
),C++ Compiler (g++ 
),patch,diffstat,makeinfo,git,bzip2,tar,gzip,gawk,chrpath,wget,cpio,perl,file,which


Please ignore this patch.

// Robert

On 1/28/19 5:19 PM, Robert Yang wrote:
> Fixed:
> $ export BB_SERVER_TIMEOUT=-1
> $ bitbake quilt-native
> $ rm -fr tmp
> $ bitbake quilt-native
> ERROR: Error running gcc  --version: /bin/sh: gcc: command not found
> 
> This is because bb.event.ParseStarted fires only once when server is running,
> but bb.event.ParseStarted fires every time when build configs are changed, so
> use bb.event.ParseStarted to fix the problem.
> 
> [YOCTO #13022]
> 
> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
> ---
>   meta/classes/base.bbclass | 11 +++++++++--
>   1 file changed, 9 insertions(+), 2 deletions(-)
> 
> diff --git a/meta/classes/base.bbclass b/meta/classes/base.bbclass
> index f1a3c0e..c273a29 100644
> --- a/meta/classes/base.bbclass
> +++ b/meta/classes/base.bbclass
> @@ -220,11 +220,18 @@ def buildcfg_neededvars(d):
>           bb.fatal('The following variable(s) were not set: %s\nPlease set them directly, or choose a MACHINE or DISTRO that sets them.' % ', '.join(pesteruser))
>   
>   addhandler base_eventhandler
> -base_eventhandler[eventmask] = "bb.event.ConfigParsed bb.event.MultiConfigParsed bb.event.BuildStarted bb.event.RecipePreFinalise bb.runqueue.sceneQueueComplete bb.event.RecipeParsed"
> +base_eventhandler[eventmask] = "\
> +	bb.event.ParseStarted \
> +	bb.event.MultiConfigParsed \
> +	bb.event.BuildStarted \
> +	bb.event.RecipePreFinalise \
> +	bb.runqueue.sceneQueueComplete \
> +	bb.event.RecipeParsed \
> +"
>   python base_eventhandler() {
>       import bb.runqueue
>   
> -    if isinstance(e, bb.event.ConfigParsed):
> +    if isinstance(e, bb.event.ParseStarted):
>           if not d.getVar("NATIVELSBSTRING", False):
>               d.setVar("NATIVELSBSTRING", lsb_distro_identifier(d))
>           d.setVar('BB_VERSION', bb.__version__)
> 


      parent reply	other threads:[~2019-01-30  9:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-28  9:19 [PATCH 0/1] base.bbclass: Use bb.event.ParseStarted for HOSTTOOLS Robert Yang
2019-01-28  9:19 ` [PATCH 1/1] " Robert Yang
2019-01-28 11:46   ` Peter Kjellerstedt
2019-01-29  8:40     ` Robert Yang
2019-01-30  9:06   ` 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=9c2e4334-e452-6ca4-f7ef-5845c5abae52@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=peter.kjellerstedt@axis.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