From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: WRL error: "Can't locate Config_heavy-target.pl in @INC" -- OE versus WRL
Date: Sat, 12 Nov 2016 14:45:08 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.20.1611121436420.20479@localhost.localdomain> (raw)
(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.
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 \
while the WRL version contains:
perl-native-runtime \
python-native-runtime \
i have no idea what to make of this. thoughts?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next reply other threads:[~2016-11-12 19:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-12 19:45 Robert P. J. Day [this message]
2016-11-12 20:17 ` WRL error: "Can't locate Config_heavy-target.pl in @INC" -- OE versus WRL Mark Hatle
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=alpine.LFD.2.20.1611121436420.20479@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--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