On Thu, Jul 14, 2016 at 11:09 AM, Rene Rivera <grafikrobot@gmail.com> wrote:

On Tue, Jul 12, 2016 at 1:54 PM, Dmitry Moskalchuk <dm@crystax.net> wrote:

This looks as a more-or-less recent change in Boost regression scripts, since I've added "using python" to our user-config.jam some time ago (I don't remember exactly but it was not later than half of year ago), but tests started failing just about a week ago (well, maybe several weeks ago). Does this conclusion looks right for you?

Yes, that looks like the correct conclusion. The library check tests I added run a Python script using the built-in python test rules.

If I'm right, we have to do something with that. This is not strictly Android-related issue, it is another cross-build testing problem of Boost.

I'll have to think about how to deal with this :-)

OK, I have a solution. It should now work that you can specify a target-os condition when configuring the python interpreter. The init for python.jam always had optional conditions for the interpreter, but unfortunately it was not usable for target-os because of the way it added the global toolset requirements. I've fixed that now. And I've also changed the Boost status/Jamfile to only use the host-os python interpreter accordingly. In your case all you need to do is add <target-os>??? when doing the "using python ..". That's assuming you build with "target-os=???". You might have to add a plain "using python ;" to configure the host-os python interpreter also, which is what the library check tests will use.

-- Rene Rivera
-- Grafik - Don't Assume Anything
-- Robot Dreams - http://robot-dreams.net
-- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail