Bug 866

Summary: perl-native conflicts with host perl within autotools
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Paul Eggleton <bluelightning>
Component: devtools / tool chainAssignee: Nitin Kamble <nitin.a.kamble>
Status: RESOLVED FIXED QA Contact:
Severity: major    
Priority: Medium CC: meta.mr.watcher, meta.watcher, richard.purdie, sgw
Version: unspecified   
Target Milestone: 1.1   
Hardware: x86   
OS: x86_64   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---

Description Paul Eggleton 2011-03-14 04:37:07 UTC
I'm getting what looks to be a reproducible problem between gnu-config-native, autotools and perl-native. It seems that if perl-native has been built when autoconf-native/automake-native get built then they attach themselves to perl-native; unfortunately this results in gnu-configize failing during autoreconf (during configure of of libtool-native in the example I have found) due to a version mismatch between host perl on my system (5.12.3) and the perl-native libraries in the sysroot (5.12.2).  

If you then clean perl-native and try again it just complains of perl being missing from the sysroot, with no attempt to rebuild perl-native either. This is I think at least part of the issue I was seeing in bug #768.

Steps to reproduce:

1. bitbake -c cleanall perl-native libtool-native gnu-config-native autoconf-native automake-native
2. bitbake perl-native
3. bitbake automake-native
4. bitbake libtool-native

If you perform the above but skip step 2, then all is well.
Comment 1 Saul Wold 2011-03-14 15:16:34 UTC
This will require invasive changes and is too late for 1.0.
Add to release notes.
Comment 2 Paul Eggleton 2011-03-15 03:30:25 UTC
There are a couple of patches in OE that will likely solve this and it's not too invasive:

http://lists.linuxtogo.org/pipermail/openembedded-core/2011-March/000462.html