From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Saul Wold <saul.wold@intel.com>
Cc: Darren Hart <dvhart@linux.intel.com>,
"poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: Git/perl build problems
Date: Mon, 13 Jun 2011 22:14:26 +0100 [thread overview]
Message-ID: <1307999666.15712.286.camel@rex> (raw)
In-Reply-To: <4DF67C8D.4010907@intel.com>
On Mon, 2011-06-13 at 14:09 -0700, Saul Wold wrote:
> On 06/13/2011 02:04 PM, Jeff Mitchell wrote:
> > On 06/13/2011 04:42 PM, Saul Wold wrote:
> >> Understood, but not fixed yet!
> >>
> >> The workaround at this point is to
> >>
> >> "bitbake -c cleansstate autoconf-native automake-native"
> >>
> >> Thanks should resolve this issue.
> >
> > Running that now, seems to be working. Would a simple revision bump to
> > those two packages fix the problem for any others?
> >
> That's my thought, but this issue is that it now uses the host perl, not
> any perl built by poky, so I am concerned that it also really need to
> inherit perlnative and I have not completely tested that yet.
No, everything is fine and working as intended and they should not need
perl-native. We should have bumped PR in hindsight and still could do
so, that would be fine.
Cheers,
Richard
next prev parent reply other threads:[~2011-06-13 21:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 19:44 Git/perl build problems Jeff Mitchell
2011-06-13 20:21 ` Darren Hart
2011-06-13 20:42 ` Saul Wold
2011-06-13 21:04 ` Jeff Mitchell
2011-06-13 21:09 ` Saul Wold
2011-06-13 21:14 ` Richard Purdie [this message]
2011-06-13 21:18 ` Saul Wold
2011-06-14 14:54 ` Jeff Mitchell
2011-06-16 21:06 ` Darren Hart
2011-06-16 22:58 ` Jeff Mitchell
2011-06-17 1:24 ` Cui, Dexuan
2011-06-17 2: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=1307999666.15712.286.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=dvhart@linux.intel.com \
--cc=poky@yoctoproject.org \
--cc=saul.wold@intel.com \
/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.