Re: [RFC v1 PATCH 00/16] populate perl-native into its own directory

[Tom Rini <tom_rini@mentor.com>]

On 06/09/2011 01:04 AM, Richard Purdie wrote:
> On Thu, 2011-06-02 at 09:55 -0700, Tom Rini wrote:
>> On 06/02/2011 09:35 AM, Richard Purdie wrote:
>>> On Thu, 2011-06-02 at 09:28 -0700, Tom Rini wrote:
>>>>   Even if we're using the sstate
>>>> cache from /foo/oecore/tmp over in /bar/oecore/tmp (and /foo/oecore/tmp
>>>> is rm -rf'd) ?  Since we've got a create_wrapper around perl and
>>>> perl${PV} it should be I suppose (or is easily added there), but I'd
>>>> feel a lot better with some testing of the above case (and the updates
>>>> to cpan*bbclass).
>>>
>>> I only took the perl-native DEPENDS patch on the condition this gets
>>> fixed properly. The patches that are there look to do that, at least for
>>> OE-Core. If there are further issues we're going to have to take them as
>>> they arise as I have an objection to crippling the build dependencies
>>> because perl is broken. Really this could use some TLC from someone with
>>> experience in the area...
>>
>> Well, I guess I'd boil down what I said above into a request like this
>> for v3:
>> - Modify cpan.bbclass to NOT set PERL_INC / PERL_LIB / PERL_ARCHLIB /
>> PERLHOSTLIB.
> 
> The first three of these are all about the *target* perl location and I
> think we still need them due the mess that perl's build system is. With
> the patch series in question they won't actually point at perl-native in
> the target case and they are only really used for cross compiling
> purposes.
> 
> PERLHOSTLIB is used by the target perl when cross compiling to find
> native .so files. perl-native will always be present at this point and
> again, it seems like a valid use case.
> 
> Summary is that I don't think perl-native is broken in any way but we do
> need those variables.

Maybe I'm having a dense morning here, but isn't that the point?  The
combination of perl's build system is messy and if we bring in cpan it
needs not only target perl locations (to dump things into) but may call
'perl' to do things and if we're on perl 5.14 and your host is only 5.10
or 5.12, bad things can happen.  And since cpan.bbclass isn't brought in
by target perl recipe, what now? :)

-- 
Tom Rini
Mentor Graphics Corporation