On 23 July 2015 at 23:38, Gary Thomas <g...@mlbassoc.com> wrote: > Well for me, the configure script ended up chosing python3, > even when I used 'pythonnative' (i.e. python2) in the recipe. > I could not get it to build any other way. > > Since python3-native will most likely already be built, what's > the harm in doing it this way? >
Why will it be build? I certainly don't have a python3 build here. Inheriting pythonnative is also the wrong thing to do - the pythonnative classes are solely for when you need to run Python and use non-standard classes that you've already built natively. If you just want to run the host Python, let it find the host python. Why was the configure script choosing python3 on your host the wrong thing to do? Ross
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
