public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>,
	"Robert P. J. Day" <rpjday@crashcourse.ca>
Subject: Re: WRL error: "Can't locate Config_heavy-target.pl in @INC" -- OE versus WRL
Date: Sat, 12 Nov 2016 15:17:25 -0500	[thread overview]
Message-ID: <ca53cb96-5c1e-35f1-55f3-8f61897de18f@windriver.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1611121436420.20479@localhost.localdomain>

On 11/12/16 2:45 PM, Robert P. J. Day wrote:
> 
>   (note: this is actually an error i'm getting under wind river linux
> 8, i'm just curious as to why OE works just fine.)
> 
>   as mentioned, when trying to build a trivial hand-rolled perl recipe
> under wind river linux 8, i'm getting:
> 
> | Can't locate Config_heavy-target.pl in @INC (@INC contains: ... long
> path snipped ...) at
> .../tmp/sysroots/x86_64-linux/usr/lib/perl-native/perl/5.22.0/Config.pm
> line 88.

My suspicion is that you are not using the buildtools-tarball with your OE
build, but Wind River Linux automatically uses this in an attempt to avoid host
incompatibilities with all of the random hosts our customers use.

To use the OE version of buildtools-tarball, you will have to build it, extract
it and then source the environment file.

>   but building precisely the same recipe under regular OE (actually,
> poky) works just fine. i did some searching, and found this:
> 
> https://patchwork.openembedded.org/patch/111047/
> 
> but i have no idea what it means. i also notice that the standard
> bitbake.conf (which i haven't looked at in a while), now contains a
> few more ASSUME_PROVIDED entries, including:
> 
>     hostperl-runtime-native \
>     hostpython-runtime-native \

f4dade8e meta/conf/bitbake.conf         (Ed Bartosh                2016-01-07
13:39:39 +0200 179)     hostperl-runtime-native \
8a474057 meta/conf/bitbake.conf         (Ed Bartosh                2016-01-13
10:03:04 +0200 180)     hostpython-runtime-native \

These are newer then Wind River Linux 8, which is based on Yocto Project 2.0 /
Jethro which was released around Nov 2015.

> while the WRL version contains:
> 
>     perl-native-runtime \
>     python-native-runtime \

You you look at Jethro you will see:

34927dfa meta/conf/bitbake.conf         (Richard Purdie          2007-12-18
15:04:06 +0000 174)     perl-native-runtime \
34927dfa meta/conf/bitbake.conf         (Richard Purdie          2007-12-18
15:04:06 +0000 175)     python-native-runtime \

So you are attempting to compare apples to oranges (master/morty/krogoth against
jethro.)

--Mark

> i have no idea what to make of this. thoughts?
> 
> rday
> 



  reply	other threads:[~2016-11-12 20:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-12 19:45 WRL error: "Can't locate Config_heavy-target.pl in @INC" -- OE versus WRL Robert P. J. Day
2016-11-12 20:17 ` Mark Hatle [this message]
2016-11-13  9:49   ` Robert P. J. Day
2016-11-13 16:16     ` Mark Hatle
2016-11-14 14:40   ` Robert P. J. Day

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=ca53cb96-5c1e-35f1-55f3-8f61897de18f@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=rpjday@crashcourse.ca \
    /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