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 18:30:27 -0800 [thread overview]
Message-ID: <4D0ACB43.8050909@intel.com> (raw)
In-Reply-To: <625BA99ED14B2D499DC4E29D8138F1504D5F409868@shsmsx502.ccr.corp.intel.com>
On 12/16/2010 06:19 PM, Tian, Kevin wrote:
>> I'm guessing Perl creates a configuration file somewhere in the sysroot
>> which contains full pathnames to it's Perl module directories. That
>> config file gets rolled into the prebuild package and cannot be used on
>> another build directory.
>>
>
> I think so, just curious how it may be reproduced in my side. I just have one
> linux box in front now. :/
>
> Or could you search which file @INC actually points to and its content?
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.
Scott
--
Scott Garman
Embedded Linux Distro Engineer - Yocto Project
next prev parent reply other threads:[~2010-12-17 2:31 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 [this message]
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 ` Shared state prebuild copy bug report (bug #602) Scott Garman
2010-12-20 22:58 ` 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=4D0ACB43.8050909@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox