| Summary: | [2.5 M2 RC1] SDK runqemu failed with python import logging | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | yeoh ee peng <ee.peng.yeoh> |
| Component: | devtools / tool chain | Assignee: | Alexander Kanavin <alex.kanavin> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Undecided | CC: | meta.mr.watcher, meta.watcher, randy.macleod, richard.purdie, ross.burton, stephano |
| Version: | 2.5 | ||
| Target Milestone: | 2.1.4 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
yeoh ee peng
2018-02-13 03:01:57 UTC
Two theories: 1) This is running a Python binary that we ship in the SDK, and the recent manifest changes have broken what packages get installed. 2) The host is Debian/Ubuntu and only has python3-minimal installed. On my Debian box libpython3.5-minimal ships logging, but maybe other releases didn't. I can confirm that 1) is correct:
ak@kanavin-desktop:/opt/poky/2.4+snapshot$ /opt/poky/2.4+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/python3
Python 3.5.3 (default, Jan 30 2018, 15:37:04)
[GCC 7.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import logging
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ImportError: No module named 'logging'
|