[poky] Shared state prebuild copy bug report (bug #602)

[Tian, Kevin]

>From: Garman, Scott A
>Sent: Friday, December 17, 2010 10:16 AM
>
>On 12/16/2010 06:06 PM, Tian, Kevin wrote:
>>> From: Scott Garman
>>> Sent: Friday, December 17, 2010 9:39 AM
>>> To: poky at pokylinux.org
>>> Subject: [poky] Shared state prebuild copy bug report (bug #602)
>>>
>>> Hello,
>>>
>>> I did a build of poky-image-lsb from Poky master today and tried copying
>>> the shared state prebuilds (sstate-cache) to my laptop. Things looked
>>> good for a while as it populated my sysroot area from the prebuilds, but
>>> then it started building autoconf-native and ran into the following
>>> error during do_compile:
>>>
>>> Can't locate Data/Dumper.pm in @INC (@INC contains: ../lib
>>> /toastssd/poky/build/tmp/sysroots/x86_64-linux/usr/lib/perl/5.8.8
>>> /toastssd/poky/build/tmp/sysroots/x86_64-  linux/usr/lib/perl/5.8.8
>>> /toastssd/poky/build/tmp/sysroots/x86_64-linux/usr/lib/perl/5.8.8
>>> /toastssd/poky/build/tmp/sysroots/x86_64-linux/usr/lib/perl /toastssd/
>>> poky/build/tmp/sysroots/x86_64-linux/usr/lib/perl/5.8.8
>>> /toastssd/poky/build/tmp/sysroots/x86_64-linux/usr/lib/perl/5.8.8
>>> /toastssd/poky/build/tmp/sysroots/x86_64-  linux/usr/lib/perl .) at
>>> ../lib/Autom4te/C4che.pm line 33.
>>>
>>> "/toastssd" is a path specific to the original build machine, but does
>>> not exist on my laptop.
>>>
>>> I have reported this as bug #602.
>>>
>>> Scott
>>>
>>
>> That's interesting. Does similar error if you try it on same machine?
>
>Do you mean rebuild poky-image-lsb from scratch on my laptop? I would
>imaging that error would not occur.

No, I mean you have to different builds pointing to same sstate_cache, with
the 1st build filling it first and then the 2nd build to reuse it. Ideally there
should be no hard dir encoded in the sstate package, or else it surely breaks.

>
>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?

Thanks
Kevin