On Wed, Apr 27, 2016 at 1:34 PM, Burton, Ross <ross.bur...@intel.com> wrote: > On 27 April 2016 at 16:15, Mark Asselstine <mark.asselst...@windriver.com> > wrote: > >> > I'm not sure using pythonnative is the right fix here. Executing python >> > using the host python should just work, so why does importing ntpath fail >> > using your host python? >> >> Correct. Host python should and does work but configure is executing >> sysroot python and using host libraries. >> > > How is it finding and executing the sysroot python without inheriting > pythonnative?
I originally hit this issue when building Wind River Linux and I usually take steps to ensure these changes are applicable to non-Wind River Linux builds before sending anything out. It appears my checks have failed me. Looking again at a Yocto build I see that host python is being picked up and thus the issue does not exist. Thanks Ross for the review. Mark > > Ross > -- > _______________________________________________ > Openembedded-devel mailing list > Openembedded-devel@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- _______________________________________________ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel