<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 23 July 2015 at 23:38, Gary Thomas <span dir="ltr"><<a href="mailto:gary@mlbassoc.com" target="_blank">gary@mlbassoc.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":1ef" class="a3s" style="overflow:hidden">Well for me, the configure script ended up chosing python3,<br>
even when I used 'pythonnative' (i.e. python2) in the recipe.<br>
I could not get it to build any other way.<br>
<br>
Since python3-native will most likely already be built, what's<br>
the harm in doing it this way?</div></blockquote></div><br>Why will it be build? I certainly don't have a python3 build here.</div><div class="gmail_extra"><br></div><div class="gmail_extra">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.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Why was the configure script choosing python3 on your host the wrong thing to do?</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>