Bug 69

Summary: Enabling Python extensions in libxml2-native_2.6.29.bb breaks the build (Rev. 5099)
Product: [Build System, Metadata & Runtime] Meta-yocto Reporter: Glenn Schmottlach <gschmott>
Component: meta-yoctoAssignee: Qing He <qing.he>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium CC: poky.bs.watcher, poky.watcher, sgw
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: Multiple   
URL: http://lists.o-hand.com/poky/0495.html
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---

Description Glenn Schmottlach 2008-08-28 17:13:57 UTC
See the discussion on the mailing list:

http://lists.o-hand.com/poky/0495.html

Basically, the libxml2-native recipe specifies to build the Python bindings for libxml2. When it goes to install these bindings in the site-packages directory, it's trying to use the "system" path instead of one relative to Poky. This in part due to the fact that BitBake assumes the Python-native is already installed (in the system path) and does not build a Python-native for the Poky staging area. Also, the recipe incorrectly specified the "--with-python" configuration option as a version number. The configure script is expecting a directory path.

Following the message thread for more details . . .
Comment 1 Qing He 2010-08-11 22:20:28 UTC
The situation has changed from the bug was first reported.

The flag now used is --with-python=${STAGING_DIR_NATIVE}/${prefix}, but this doesn't really work. In the configure output:
---
Found python in ......./sysroot/x86_64-linux/usr
................./libxml2-native-2.7.7_ro/libxml2-2.7.7/configure: line 13470
  .......... sysroots/x86_64-linux/usr: is a directory
Found python version
---

On non-cross build, it should be
---
Found python in /usr/bin/python
Found python version 2.6
---

So python binding is in fact not built in current libxml2
Comment 2 Qing He 2010-08-12 08:05:27 UTC
fixed in cf1e754b3fee3c7ae907e7ae30233083d7892215