Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/3] nasm: fix issue with repeat configure
Date: Sat, 31 Mar 2012 18:02:56 +0100	[thread overview]
Message-ID: <1333213376.18082.251.camel@ted> (raw)
In-Reply-To: <512eae1ae0678b247076db900304725702acc91e.1333145263.git.nitin.a.kamble@intel.com>

On Fri, 2012-03-30 at 15:28 -0700, nitin.a.kamble@intel.com wrote:
> From: Nitin A Kamble <nitin.a.kamble@intel.com>
> 
> This Fixes bug: [YOCTO #2176]
> 
> This fixes the following issue as mentioned in the bug:
> If nasm-native has to be rebuilt (due to a signature change) it will fail:
> 
> | checking for a BSD-compatible install... /usr/bin/install -c
> | /media/large/tmp/work/x86_64-linux/nasm-native-2.07-r1/nasm-2.07/configure:
> line 4261: syntax error near unexpected token `-W'
> | /media/large/tmp/work/x86_64-linux/nasm-native-2.07-r1/nasm-2.07/configure:
> line 4261: `PA_ADD_CFLAGS(-W)'
> | ERROR: oe_runconf failed
> NOTE: package nasm-native-2.07-r1: task do_configure: Failed
> 
> The failure appears to be caused by do_patch_fixaclocal being run a second time
> 
> Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
> ---
>  meta/recipes-devtools/nasm/nasm_2.07.bb |    8 ++++----
>  1 files changed, 4 insertions(+), 4 deletions(-)

Merged to master, thanks.

Richard




  reply	other threads:[~2012-03-31 17:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-30 22:28 [PATCH 0/3] Misc Fixes nitin.a.kamble
2012-03-30 22:28 ` [PATCH 1/3] nasm: fix issue with repeat configure nitin.a.kamble
2012-03-31 17:02   ` Richard Purdie [this message]
2012-03-30 22:28 ` [PATCH 2/3] cross-canadian.bbclass: fix rpath for sdk executables nitin.a.kamble
2012-03-31 17:02   ` Richard Purdie
2012-03-30 22:28 ` [PATCH 3/3] poky-tiny: avoid eglibc locale packaging nitin.a.kamble

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=1333213376.18082.251.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox