All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: "paul.eggleton@linux.intel.com" <paul.eggleton@linux.intel.com>,
	"poky@pokylinux.org" <poky@pokylinux.org>
Subject: Re: about 'noexec' message
Date: Mon, 20 Dec 2010 15:04:37 +0000	[thread overview]
Message-ID: <1292857477.25087.4517.camel@rex> (raw)
In-Reply-To: <625BA99ED14B2D499DC4E29D8138F1504D5F40997F@shsmsx502.ccr.corp.intel.com>

On Fri, 2010-12-17 at 12:23 +0800, Tian, Kevin wrote:
> Unfortunately I think this causes another problem when using sstate. I got an error
> from m4-native when building from scratch (with prebuilt available):
> 
> ERROR: install: cannot stat `xxx/tmp/sysroots/i686-linux/usr/share/gnu-config/config.sub
> 
> Actually from the log gnu-config.do_populate_sysroot has been accelerated earlier in
> setscene stage, with necessary sysroot files installed. However later gnu-config-native
> is still considered requiring rebuild, and thus the installed sysroot files are removed again.
> The weird thing under this condition is that m4-native thought that do_populate_sysroot
> of gnu-config-native has been completed and thus doesn't wait for new build of 
> gnu-config-native to complete, which then triggers above error.
> 
> I haven't figure out the reason why this commit causes this confliction: sstate package
> is installed successfully but the package still requires rebuild. By reverting this change
> this error disappears.

I made some assumptions in the fix I pushed which weren't correct but
didn't show up under the testing I gave it. The real underlying issue is
that the XXX_setscene stamps are never created for setscene noexec
tasks. I've pushed a fix which does this now:

http://git.pokylinux.org/cgit.cgi/poky/commit/?id=a86f960f651c561bb104723aa0b4cd0922a3425a

Cheers,

Richard



  reply	other threads:[~2010-12-20 15:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-14 13:40 [PATCH 0/1] Fix weird rebuild issue even when sstate signature doesn't change Kevin Tian
2010-12-15  9:12 ` Richard Purdie
2010-12-15 11:12   ` Tian, Kevin
2010-12-15 16:10   ` Gary Thomas
2010-12-15 16:17     ` Paul Eggleton
2010-12-16  1:43     ` Tian, Kevin
2010-12-16  8:45     ` Tian, Kevin
2010-12-16  9:48       ` about 'noexec' message Tian, Kevin
2010-12-16 15:19         ` Richard Purdie
2010-12-17  2:48           ` Tian, Kevin
2010-12-17  4:23           ` Tian, Kevin
2010-12-20 15:04             ` Richard Purdie [this message]
2010-12-16 15:29       ` [PATCH 0/1] Fix weird rebuild issue even when sstate signature doesn't change Richard Purdie
2010-12-20 21:23     ` Richard Purdie

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=1292857477.25087.4517.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=kevin.tian@intel.com \
    --cc=paul.eggleton@linux.intel.com \
    --cc=poky@pokylinux.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.