All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: WRL error: "Can't locate Config_heavy-target.pl in @INC" -- OE versus WRL
Date: Mon, 14 Nov 2016 09:40:25 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.20.1611140938130.15267@ca624034.mitel.com> (raw)
In-Reply-To: <ca53cb96-5c1e-35f1-55f3-8f61897de18f@windriver.com>


  i think i figured out the problem ... all of the perl recipes i was
trying to build (from meta-cpan) had the line:

  inherit cpan allarch

rather than just:

  inherit cpan

so the native perl built by WRL chokes on that, while the slightly
newer perl that comes with OE has a patch to handle that.

  at least, that's what *appears* to be happening. does that make any
sense?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================



      parent reply	other threads:[~2016-11-14 14:41 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
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 [this message]

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.1611140938130.15267@ca624034.mitel.com \
    --to=rpjday@crashcourse.ca \
    --cc=mark.hatle@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.