From: Kang Kai <Kai.Kang@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Some problems about nativesdk-perl
Date: Sat, 29 Sep 2012 14:20:26 +0800 [thread overview]
Message-ID: <50669329.1040607@windriver.com> (raw)
In-Reply-To: <1348838392.15753.50.camel@ted>
On 2012年09月28日 21:19, Richard Purdie wrote:
> On Fri, 2012-09-28 at 19:48 +0800, Kang Kai wrote:
>> Hi Richard,
>>
>> I meet 2 problems about nativesdk-perl.
>>
>> First one is that nativesdk-perl-modules doesn't depends on the single
>> nativesdk-perl-module-xxx which I asked you yesterday, but I still
>> don't know how to fix it.
>> I tried to add one line to perl_5.14.2.bb:
>> RRECOMMENDS_perl-modules_virtclass-nativesdk +=
>> "nativesdk-perl-module-config"
>>
>> and it will cover the original value and make nativesdk-perl-modules
>> only depends on nativesdk-perl-module-config.
>> Doesn't "+=" work for nativesdk ?
> I will need to investigate this issue further to comment and I'm short
> on time at the moment.
OK. Thanks.
>
>> The second issue is the latest commit for perl(Yocto commit
>> 876ec81c039132d07a5f3d99bae40d6154351d41) . I build
>> meta-toolchain-gmae with it,
>> and the perl @INC path remove the "/opt/poky/1.2
>> +snapshot/sysroots/x86_64-pokysdk-linux" prefix.
>> Is that the right operation?
> No, please try with the patch I just sent applied as this will hopefully
> fix it.
The perl @INC path prefix for toolchain("/opt/poky/1.2+snapshot/...) has
been added back by your patch.
But there are still one path in @INC include build environment
directories, it seems that the dirs are compiled into libperl.so. So
use sed when do_packages
could not fix this issue.
Regards,
Kai
>
> Cheers,
>
> Richard
>
>
prev parent reply other threads:[~2012-09-29 6:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-28 11:48 Some problems about nativesdk-perl Kang Kai
2012-09-28 13:19 ` Richard Purdie
2012-09-29 6:20 ` Kang Kai [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=50669329.1040607@windriver.com \
--to=kai.kang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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