On Tue, Mar 15, 2016 at 11:29 PM, <alexander.kana...@linux.intel.com> wrote: >>> This is because python3-config does not contain the version within >>> itself, >>> it reports the version of the python interpreter that it is run with. So >>> NOTABUG. >> >> If its supposed to report the version of python pack its coming with >> and not the interpreter its run with >> then how do you decide its not a behavior change ? > > Apologies for being terse. I should've explained that when building > recipes that make use of this script, it will be run with the native > python (instead of host python) because native python will come first in > the PATH, and so the version reported will be correct, because native > python will match target python. This is set up in pythonnative.bbclass > for python 2, and in python3native.bbclass for python 3. Sorry but I don't get it: The script reports the version of host's python which might be different from what we are building native and cross. When something is trying to link against python libs and is using this script this crashes for host's with python < 3.5. This is a bug. It should be either corrected or using of pkg-config should be enforced if possible.
By the way: What was wrong with the shell script exactly? We have used it for long time and it reported the correct version. Andreas -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
