| Summary: | python build tries to import target modules and fails | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Awais <awais_belal> |
| Component: | devtools / tool chain | Assignee: | Alejandro Hernandez <alejandro.hernandez> |
| Status: | VERIFIED FIXED | QA Contact: | Cristina Agurida <cristina-danielax.agurida> |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | bogdanx.a.voiculescu, meta.mr.watcher, meta.watcher |
| Version: | unspecified | ||
| Target Milestone: | 2.0.1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Awais
2015-11-10 08:50:25 UTC
Just to add that this can be confirmed through dev-shell once the build fails. bitbake -c devshell python edit the (srcdir)/setup.py script to first import sys and the print sys.path which is the path python is going to use for imports. The path does not contain references to sysroot (native) python modules location and then the interpreter tries to import from target's build dir. I can confirm this isn't working, I do find it interesting this is necessary, since when executing python-native from a devshell and printing sys.path, one can see that it DOES include CROSSPYTHONPATH, but when it is executed via the makefile to install sharedmods, it doesn't, causing the failure, so I am just wondering if there might be a better fix, in the meantime, the patch seems to work. Fixed here: http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=a1fa8d9ac53625737aab29b4e5e1687fc01bdfc2 Verified on master: 36b43b233c841b3c09fc17e04686b4b758780963 |