From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Scott Garman <scott.a.garman@intel.com>
Cc: "poky@pokylinux.org" <poky@pokylinux.org>
Subject: Re: Shared state prebuild copy bug report (bug #602)
Date: Mon, 20 Dec 2010 22:58:56 +0000 [thread overview]
Message-ID: <1292885936.25087.5158.camel@rex> (raw)
In-Reply-To: <4D0AF87A.7060201@intel.com>
On Thu, 2010-12-16 at 21:43 -0800, Scott Garman wrote:
> On 12/16/2010 08:47 PM, Tian, Kevin wrote:
> >
> > 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.
I've committed a workaround for this in the form of:
http://git.pokylinux.org/cgit.cgi/poky/commit/?h=master&id=9975c00c1a6a9ae1c39678dec0986f4c62418c96
which means perl-native will always be rebuilt but at least builds
should then work.
I've left bug #602 open as a hint to investigate a proper fix for this,
maybe by setting an environment variable and/or a wrapper script.
At present the aim is to get the sstate packages working, then we can
look at details like this.
Cheers,
Richard
prev parent reply other threads:[~2010-12-20 23:00 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 ` Shared state prebuild copy bug report (bug #602) Scott Garman
2010-12-20 22:58 ` Richard Purdie [this message]
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=1292885936.25087.5158.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=poky@pokylinux.org \
--cc=scott.a.garman@intel.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.