Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: poky@yoctoproject.org, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/1] gnu-config make sure we use perl-native
Date: Fri, 11 Mar 2011 17:34:20 -0800	[thread overview]
Message-ID: <4D7ACD9C.3010002@linux.intel.com> (raw)
In-Reply-To: <cover.1299891748.git.sgw@linux.intel.com>

On 03/11/2011 05:15 PM, Saul Wold wrote:
> From: Saul Wold<sgw@linux.intel.com>
>
> During a world build I was getting a perl version mismatch between
> the perl-native and the host perl. This change ensures that
> perl-native is used always.
>

Never mind this patch, Saul's brain is not functioning well today,
I completely missed the comment!

Back to the drawing board on why the miss-match is occuring in Config.pm 
then.

Sau!
> Pull URL: git://git.pokylinux.org/poky-contrib.git
>    Branch: sgw/gnu-config
>    Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=sgw/gnu-config
>
> Thanks,
>      Saul Wold<sgw@linux.intel.com>
> ---
>
>
> Saul Wold (1):
>    gnu-config: Ensure that we use perl-native to avoid version
>      mis-matches
>
>   .../gnu-config/gnu-config_20080123.bb              |    4 +---
>   1 files changed, 1 insertions(+), 3 deletions(-)
>



  parent reply	other threads:[~2011-03-12  1:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-12  1:15 [PATCH 0/1] gnu-config make sure we use perl-native Saul Wold
2011-03-12  1:15 ` [PATCH 1/1] gnu-config: Ensure that we use perl-native to avoid version mis-matches Saul Wold
2011-03-12  1:34 ` Saul Wold [this message]
2011-03-12  2:31   ` [poky] [PATCH 0/1] gnu-config make sure we use perl-native Khem Raj
2011-03-14 11:51     ` Paul Eggleton
2011-03-14 12:18       ` Koen Kooi
2011-03-14 12:55         ` Richard Purdie
2011-03-17 11:48         ` Richard Purdie

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=4D7ACD9C.3010002@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=poky@yoctoproject.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