Skip to contentSkip to conversation

qemu: Inherit pythonnative

PATCH In review Khem Raj 2 participants 2 messages Feb 10, 2017

lore
Share & tools
lore

Khem Raj

author
#0 lore raw

PATCH 1/1 qemu: Inherit pythonnative

On buildhosts where default python has switched to using python3 qemu-native fails configure like this

| ERROR: Cannot use 'python', Python 2.6 or later is required.
|        Note that Python 3 or later is not yet supported.
|        Use --python=/path/to/python to specify a supported Python.
|

inheriting pythonnative makes sure that a usable python2 is always available.

---
 meta/recipes-devtools/qemu/qemu.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta/recipes-devtools/qemu/qemu.inc +1 -1
index ef5d75c450..50f53f0de1 100644
@@ -6,7 +6,7 @@ RDEPENDS_${PN}_class-target += "bash"
 RDEPENDS_${PN}-ptest = "bash make"
 
 require qemu-targets.inc
-inherit autotools pkgconfig ptest
+inherit autotools pkgconfig ptest pythonnative
 BBCLASSEXTEND = "native nativesdk"
 
 # QEMU_TARGETS is overridable variable
Signature · 1 line
2.11.1
#1 lore raw
Quoted 7 lines · Khem Raj

On buildhosts where default python has switched to using python3 qemu-native fails configure like this

| ERROR: Cannot use 'python', Python 2.6 or later is required.
|        Note that Python 3 or later is not yet supported.
|        Use --python=/path/to/python to specify a supported Python.

Build hosts where /usr/bin/python is Python3 are Doing It Wrong, and Python upstream says don't do that.

Many other recipes depend on /usr/bin/python existing, so I'm not sure we want to start building our own Python so early in the build just yet, especially as we're trying to move away from Py2. Can we not just list python2 as a host dependency (to be honest, I thought it already was).

Ross