Patchwork [*RFC,CONSOLIDATED,PULL,RFC*,03/23] git: restore the dependency on perl-native

From: Dexuan Cui <dexuan.cui@intel.com>

[YOCTO #1155]

I thought git-native could depend on perl-native-runtime and tests on
Ubuntu 9.04/10.10 and Fedora 13 show it could buid fine (looks these distros
install perl-ExtUtils-MakeMaker by default).

However Joshua reported on Fedora 15 i686 host, git-native can't build unless
he manually installed perl-ExtUtils-MakeMaker to the host.

This makes me think we may as well make git-native depend on perl-native.

Signed-off-by: Dexuan Cui <dexuan.cui@intel.com>
---
 meta/recipes-devtools/git/git.inc        |    6 +++---
 meta/recipes-devtools/git/git_1.7.5.1.bb |    2 +-
 2 files changed, 4 insertions(+), 4 deletions(-)

On Sun, 2011-06-12 at 23:54 -0700, Saul Wold wrote:
> -inherit autotools
> +inherit autotools perlnative

This broke the tree for me.  Now I get:

NOTE: Out of date cache found, rebuilding...
ERROR: Could not inherit file
classes/perlnative.bbclass###########################################
| ETA:  00:00:03
ERROR: Command execution failed: Exited with 1

Am I meant to have perlnative.bbclass somewhere?  It isn't in
meta/classes.

p.

Op 14 jun 2011, om 14:53 heeft Phil Blundell het volgende geschreven:

> On Sun, 2011-06-12 at 23:54 -0700, Saul Wold wrote:
>> -inherit autotools
>> +inherit autotools perlnative
> 
> This broke the tree for me.  Now I get:
> 
> NOTE: Out of date cache found, rebuilding...
> ERROR: Could not inherit file
> classes/perlnative.bbclass###########################################
> | ETA:  00:00:03
> ERROR: Command execution failed: Exited with 1
> 
> Am I meant to have perlnative.bbclass somewhere?  It isn't in
> meta/classes.

Same error here

On Tue, 2011-06-14 at 13:53 +0100, Phil Blundell wrote:
> On Sun, 2011-06-12 at 23:54 -0700, Saul Wold wrote:
> > -inherit autotools
> > +inherit autotools perlnative
> 
> This broke the tree for me.  Now I get:
> 
> NOTE: Out of date cache found, rebuilding...
> ERROR: Could not inherit file
> classes/perlnative.bbclass###########################################
> | ETA:  00:00:03
> ERROR: Command execution failed: Exited with 1

BTW, Scott, this is also a new addition to my list of unsatisfactory
bitbake error messages.  It would be more helpful if bitbake: (a)
printed the name of the recipe causing the problem, rather than leaving
me to grep the tree/guess, and (b) continued rather than immediately
bailing out.  Also, aesthetically, it'd be nice if it didn't print the
error on top of the status bar although I guess that is a minor issue in
the larger scheme of things.

However, on the positive side, at least there is no python
stacktrace :-)

p.

On Tue, 2011-06-14 at 14:01 +0100, Phil Blundell wrote:
> On Tue, 2011-06-14 at 13:53 +0100, Phil Blundell wrote:
> > On Sun, 2011-06-12 at 23:54 -0700, Saul Wold wrote:
> > > -inherit autotools
> > > +inherit autotools perlnative
> > 
> > This broke the tree for me.  Now I get:
> > 
> > NOTE: Out of date cache found, rebuilding...
> > ERROR: Could not inherit file
> > classes/perlnative.bbclass###########################################
> > | ETA:  00:00:03
> > ERROR: Command execution failed: Exited with 1
> 
> BTW, Scott, this is also a new addition to my list of unsatisfactory
> bitbake error messages.  It would be more helpful if bitbake: (a)
> printed the name of the recipe causing the problem, rather than leaving
> me to grep the tree/guess, and (b) continued rather than immediately
> bailing out.  Also, aesthetically, it'd be nice if it didn't print the
> error on top of the status bar although I guess that is a minor issue in
> the larger scheme of things.
> 
> However, on the positive side, at least there is no python
> stacktrace :-)

I've fixed this.

Unintentionally, a merge was made to poky but not to OE-Core for a
series of patches. I suspect somehow I did make the merge but not the
push and then lost the changes thinking it was just testing changes when
I came back to them.

So I'm sorry about the screw up there, totally my fault and unintended
and it should be fixed now.

Cheers,

Richard