Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [RFC v1 PATCH 00/16] populate perl-native into its own	directory
Date: Thu, 2 Jun 2011 07:25:45 -0700	[thread overview]
Message-ID: <4DE79D69.7080806@mentor.com> (raw)
In-Reply-To: <1307023591.27470.549.camel@rex>

On 06/02/2011 07:06 AM, Richard Purdie wrote:
> On Wed, 2011-06-01 at 13:59 -0700, Tom Rini wrote:
>> On 06/01/2011 01:45 PM, Phil Blundell wrote:
>>> On Wed, 2011-06-01 at 13:42 -0700, Tom Rini wrote:
>>>> What falls down in this case is that  once
>>>> perl-native is built (and in our PATH), if it's a different version than
>>>> system-wide perl, stuff starts failing on version mis-match.
>>>
>>> I think that's the bit that I'm not properly understanding.  Which
>>> versions are mismatching, exactly?  
>>>
>>> Surely the local perl from the sysroot ought to be completely
>>> self-contained and shouldn't be using any bits from the host perl
>>> install at that point.
>>
>> So this jogs my memory a bit!  It's not so much perl itself but stuff
>> that uses perl that can get dirty and then no, you have stuff thats
>> built for system perl and stuff that's built with perl-native clashing.
>>
>> Relying even more on memory, I think help2man was one of the "easy"
>> culprits and since we also modify the env, we do things like have
>> help2man run with PERL5LIB and so on pointing system-wide perl at
>> perl-native's lib directory and so forth.
> 
> But with the proposed patch series either:
> 
> a) help2man depends perlnative.bbclass
> 
> In this case it can depend on perl-native being there, its in path and
> things work as per OE.dev.
> 
> b) help2man doesn't depend in perlnative.bbclass
> 
> It only sees the system perl.
> 
> So I'm still not clear where the problem is?

Well, help2man-native is (or needs to be) a dep listed in
autotools.bbclass (since so many things need it, hence why it oe-core
still just has it as a required host utility instead of building it).

But help2man is just the easy/common case.  Heck, it _may_ blow up even
with the host help2man instead of help2man-native, if a recipe uses
system-wide help2man and perlnative.bbclass.  The root problem (again,
from memory) is that since we modify PERL5LIB and so on, when we do
that, we've opened ourselves up for system-wide perl trying to use
perl-native's stuff.

-- 
Tom Rini
Mentor Graphics Corporation



  reply	other threads:[~2011-06-02 14:29 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-01 13:18 [RFC v1 PATCH 00/16] populate perl-native into its own directory Dexuan Cui
2011-06-01 13:18 ` [RFC v1 PATCH 01/16] native.bbclass: allow a native package to be populated into its own dir Dexuan Cui
2011-06-01 13:40   ` Phil Blundell
2011-06-02  6:04     ` Cui, Dexuan
2011-06-02 13:50       ` Cui, Dexuan
2011-06-01 13:18 ` [RFC v1 PATCH 02/16] perl-native: populate " Dexuan Cui
2011-06-01 13:18 ` [RFC v1 PATCH 03/16] perlnative.bbclass: add the file Dexuan Cui
2011-06-01 13:18 ` [RFC v1 PATCH 04/16] gnu-config-native: should depend on perl-native-runtime rather than perl-native Dexuan Cui
2011-06-01 13:18 ` [RFC v1 PATCH 05/16] libcap: " Dexuan Cui
2011-06-01 13:18 ` [RFC v1 PATCH 06/16] openssl: " Dexuan Cui
2011-06-01 13:18 ` [RFC v1 PATCH 07/16] git: " Dexuan Cui
2011-06-10  0:10   ` Joshua Lock
2011-06-10  7:28     ` Cui, Dexuan
2011-06-01 13:18 ` [RFC v1 PATCH 08/16] coreutils: remove unnecessary dependency on perl Dexuan Cui
2011-06-01 13:18 ` [RFC v1 PATCH 09/16] dpkg: should depend on perl-native-runtime rather than perl-native Dexuan Cui
2011-06-01 13:18 ` [RFC v1 PATCH 10/16] webkit-gtk: " Dexuan Cui
2011-06-01 13:18 ` [RFC v1 PATCH 11/16] perl: inherit perlnative Dexuan Cui
2011-06-01 13:18 ` [RFC v1 PATCH 12/16] cpan.bbclass, cpan-base.bbclas: update them for the perlnative change Dexuan Cui
2011-06-01 13:18 ` [RFC v1 PATCH 13/16] libxml-parser-perl: inherit perlnative Dexuan Cui
2011-06-01 13:18 ` [RFC v1 PATCH 14/16] libconvert-asn1-perl: fix EXTRA_PERLFLAGS due to the perl-native change Dexuan Cui
2011-06-01 13:18 ` [RFC v1 PATCH 15/16] libxml-simple-perl: fix EXTRA_PERLFLAGS due the the perlnative change Dexuan Cui
2011-06-01 13:18 ` [RFC v1 PATCH 16/16] icon-naming-utils-native: inherit perlnative Dexuan Cui
2011-06-01 13:38 ` [RFC v1 PATCH 00/16] populate perl-native into its own directory Richard Purdie
2011-06-01 17:17 ` Tom Rini
2011-06-01 17:56   ` Richard Purdie
2011-06-01 19:39     ` Tom Rini
2011-06-01 20:05       ` Phil Blundell
2011-06-01 20:42         ` Tom Rini
2011-06-01 20:45           ` Phil Blundell
2011-06-01 20:59             ` Tom Rini
2011-06-02 14:06               ` Richard Purdie
2011-06-02 14:25                 ` Tom Rini [this message]
2011-06-02 14:37                   ` Phil Blundell
2011-06-02 16:28                     ` Tom Rini
2011-06-02 16:35                       ` Richard Purdie
2011-06-02 16:55                         ` Tom Rini
2011-06-09  8:04                           ` Richard Purdie
2011-06-09  8:08                             ` Richard Purdie
2011-06-09 13:51                               ` Cui, Dexuan
2011-06-09 13:56                                 ` Richard Purdie
2011-06-10  6:13                                   ` Cui, Dexuan
2011-06-10 14:23                               ` Tom Rini
2011-06-10 14:26                             ` Tom Rini
2011-06-02 13:46           ` Cui, Dexuan

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=4DE79D69.7080806@mentor.com \
    --to=tom_rini@mentor.com \
    --cc=openembedded-core@lists.openembedded.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