All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Garman <scott.a.garman@intel.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: "poky@pokylinux.org" <poky@pokylinux.org>
Subject: Re: Shared state prebuild copy bug report (bug #602)
Date: Thu, 16 Dec 2010 21:43:22 -0800	[thread overview]
Message-ID: <4D0AF87A.7060201@intel.com> (raw)
In-Reply-To: <625BA99ED14B2D499DC4E29D8138F1504D5F409997@shsmsx502.ccr.corp.intel.com>

On 12/16/2010 08:47 PM, Tian, Kevin wrote:
>> It appears that @INC is encoded into the perl interpreter itself. cd
>> into your native sysroot directory and run ./usr/bin/perl -V
>>
>> To reproduce this, bitbake an image in one directory. Then, create a
>> separate directory somewhere else, and copy your sstate-cache over to
>> the second build area. Finally (and this is important), rename your
>> original build area.
>>
>> I'd bet that will make this reproducable.
>>
>
> I assume that you're not using the latest master, correct? I'm asking here as I
> encountered other errors earlier than this one due to a 'noexec' change from RP
> yesterday, and thus your info would confirm my guess. :-)

No, I managed to do this test with today's commit 
(ac4364698618a541624d1a00f27b638815e5a3f5).

> Then after revert that commit, now I do reproduce this with same error as yours,
> except that it happens on git-native. This is understood as I think all perl related
> scripts will hit this issue.

This will impact a ton of recipes as perl is used heavily by autotools.

> However I haven't found which bit contains that bad link pointing to original build
> directory. I checked tmp/sysroot/i686-linux/usr/lib/perl/5.8.8/Config.pm, where
> all hard paths are changed to new build directory correctly... :/

Thanks for looking into this.

Scott

-- 
Scott Garman
Embedded Linux Distro Engineer - Yocto Project


  parent reply	other threads:[~2010-12-17  5:43 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-17  1:38 Shared state prebuild copy bug report (bug #602) Scott Garman
2010-12-17  2:06 ` Tian, Kevin
2010-12-17  2:15   ` Scott Garman
2010-12-17  2:19     ` Tian, Kevin
2010-12-17  2:30       ` Scott Garman
2010-12-17  2:35         ` Tian, Kevin
2010-12-17  4:47         ` Tian, Kevin
2010-12-17  5:29           ` perl binary hard-code path hurts sstate Tian, Kevin
2010-12-17 13:49             ` Chris Larson
2010-12-17 13:58               ` Richard Purdie
2010-12-17 15:08                 ` Gary Thomas
2010-12-21  1:09                   ` Tian, Kevin
2010-12-21 11:51                     ` Tian, Kevin
2010-12-21 12:30                       ` Gary Thomas
2010-12-21 15:14                         ` Gary Thomas
2010-12-22  1:25                           ` Tian, Kevin
2010-12-22 12:07                             ` Tian, Kevin
2010-12-22 12:35                               ` Gary Thomas
2010-12-22 13:38                                 ` Tian, Kevin
2010-12-22 13:42                                   ` Tian, Kevin
2010-12-23  4:52                           ` Tian, Kevin
2010-12-21 11:43                 ` Tian, Kevin
2010-12-17  5:43           ` Scott Garman [this message]
2010-12-20 22:58             ` Shared state prebuild copy bug report (bug #602) 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=4D0AF87A.7060201@intel.com \
    --to=scott.a.garman@intel.com \
    --cc=kevin.tian@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.