All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: poky@yoctoproject.org
Subject: Re: llvm build regression caused by [71cc9de357484c469cc3a46f013b11c84c924aa0] bitbake: Fix script location after mishandled merge
Date: Mon, 06 Aug 2012 14:11:32 +0100	[thread overview]
Message-ID: <1344258692.9756.150.camel@ted> (raw)
In-Reply-To: <CAMKF1soaei9wyzPH60HnyA8RVafYXNoyghi_j=sBWiCM9mk+uw@mail.gmail.com>

On Sat, 2012-08-04 at 14:15 -0700, Khem Raj wrote:
> Actually I pasted wrong commit
> 
> Problem is due to
> 
> 
> commit 9df0a20d9562322162676ed2606bf4b0a1bd6726
> Author: Richard Purdie <richard.purdie@linuxfoundation.org>
> Date:   Fri Aug 3 10:24:32 2012 +0100
> 
>     bitbake: data_smart: Fix unanchored regexp causing strange parsing issue
> 
>     If this regular expression is unanchored, it would accept strings like:
> 
>     do_install_append1
>     do_install_appendsomelongstring
> 
>     and treat them like they were do_install_append. Clearly this
> isn't desirable.
>     Only one instance of this type of issue was found in OE-Core and
> has been fixed
>     so correcting the regexp should be safe to do.
> 
>     (Bitbake rev: 23bd5300b4a99218a15f4f6b0ab4091d63a602a5)
> 
>     Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> 

Have a look through the recipes and see if there is anything doing:

xxxx_append<something here>

and remove the <something here>.

Cheers,

Richard



  reply	other threads:[~2012-08-06 13:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-04 20:15 llvm build regression caused by [71cc9de357484c469cc3a46f013b11c84c924aa0] bitbake: Fix script location after mishandled merge Khem Raj
2012-08-04 21:15 ` Khem Raj
2012-08-06 13:11   ` Richard Purdie [this message]
2012-08-06 17:16     ` Khem Raj

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=1344258692.9756.150.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=poky@yoctoproject.org \
    --cc=raj.khem@gmail.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 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.