Re: [Boost-build] Fwd: Re: [C++-sig] Boost 1.69 python3 module

Subject: Re: [Boost-build] Fwd: Re: [C++-sig] Boost 1.69 python3 module
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2019-02-08 06:56:50

AMDG

On 2/7/19 6:04 PM, Alex Biddulph via Boost-build wrote:
> <snip>
> 
>> It looks like python was built in that run.
>> I also noticed:
>>   project-config.jam:33: syntax error at EOF
>> which didn't appear in the previous log.
>> In addition, the new log shows configuration
>> of python 2.7 instead of python 3.6.
> 
> It did indeed appear to build the python library in that case (although I missed a semicolon so it built python27 instead of python36).
> 
> I corrected my error (also scrubbing the build folder again), and this time it correctly built and installed the python36 library.
> Here is the link to the output for this build
> https://drive.google.com/open?id=1UHzlwMfAlXlOEghqIFH41jnBlfPNAH51
> 

Well, at least you now have a workaround.

> So I went back to building everything (I left the --debug-building option on) and once again, it built everything but the python36 library. Here is the link to the build output for this build
> https://drive.google.com/open?id=14m9Jrwz8imrEi90HGkkmglVKEI3v6FHH
> 

That's really strange.  I have no idea why that would happen.
There's definitely some kind of hidden global state somewhere.
That mostly confirms my suspicion that the offending rule is
python.require-py.  Maybe if you add /debug/ into the call to
main-target.select-alternatives, it will reveal something:

    local py-ext-alternative = [ $(py-ext-target).select-alternatives
$(property-set) debug ] ;

In Christ,
Steven Watanabe