[OE-core] [PATCH 37/58] gnu-config-native: add dependency on perl-native

Cui, Dexuan dexuan.cui at intel.com
Wed May 11 01:00:05 UTC 2011


Saul Wold wrote:
> On 05/10/2011 07:20 AM, Cui, Dexuan wrote:
>> Richard Purdie wrote:
>>> On Tue, 2011-05-10 at 22:02 +0800, Cui, Dexuan wrote:
>>>>> or we hardcode to /usr/bin/perl. Since the perl-native binary
>>>>> won't be in the path for any of these, autodetecting and letting
>>>>> it hardcode is probably fine. It has the advantage that if there
>>>>> are any binary modules ever involved, they'll match the version
>>>>> of perl they were built for regardless of whether perl-native is a
>>>>> dependency or not. If someone adds a perl-native dependency to
>>>>> autoconf-native, it will also still select the "correct" perl.
>>>>> 
>>>>> Whilst doing this we need to keep bug #968 in mind and ensure that
>>>>> if perl-native is used, all of perl-native is in the sysroot. That
>>>>> bug is where the perl binary was installed, the library was not
>>>>> and an error occurred. If it is in its own directory which is only
>>>>> added to the PATH for users with the correct dependency, we avoid
>>>>> this. 
>>>>> 
>>>>> As for bug #941, the bottom line is that however autoconf-native
>>>>> selects its perl version, the strings encoded in gnu-config should
>>>>> really match those in the other autoconf-native scripts.
>>>> I saw a commit that was once suspended was pushed into poky
>>>> master yesterday:
>>>> http://git.pokylinux.org/cgit/cgit.cgi/poky/commit/?id=605141a93443df042634b2219a8628a9004be023
>>>> Actually it does fix(or at least workaround) bug #941 and bug #968.
>>>> 
>>>> Looks there are much work to do if we install perl-native to its
>>>> own sysroot. At present we can use the above commit as a
>>>> workaround. 
>>> 
>>> Its merged as a workaround but I still think we need to clean this
>>> up properly and we need to continue working on it.
>> I actually meant the priority could be lowered since we have a
>> workaround. :-) Surely, I'll continue to investigate it.
>> 
> Just to be clear, just because we have a work around does not mean we
> can lower the priority, this is still a valid bug that needs a proper
> patch in a timely manner.
> 
> 941 is still a major bug and requires a fix before the milestone 1
> release stabilization period (May 20), which is 10 days from now.
OK, so I'll put more effort on this to get a complete fix.

Thanks,
-- Dexuan




More information about the Openembedded-core mailing list