On 2015-07-23 16:33, Burton, Ross wrote:
On 23 July 2015 at 01:22, Gary Thomas <g...@mlbassoc.com <mailto:g...@mlbassoc.com>> wrote: This recipe needs python3. This patch arranges to use the bitbake-built version, not the host version (which may be missing or not work...) Needs is a strong word. The configure script does this: AC_CHECK_PROGS([PYTHON], [python3 python2 python]) What's actually happening as a patch to simply remove python3 from that list will also solve most problems - we obviously depend on a fully working host python 2.
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? -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------ -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
