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

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

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

Boost - Build mailing list




-------- Forwarded Message --------
Subject: Re: [C++-sig] [Boost-build] Boost 1.69 python3 module
Date: Thu, 7 Feb 2019 22:55:22 +0000
From: Alex Biddulph [hidden email]
Reply-To: [hidden email], Development of Python/C++ integration [hidden email]
To: [hidden email] [hidden email]


> 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

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


On 7/2/19 10:21 am, Alexander Biddulph wrote:

OK, I scrubbed the build folder and ran again. Here is a link to the output with -d2 --debug-configuration --with-python --debug-building on the command line (in that order)
https://drive.google.com/open?id=1hINO1jHr5ikkVQ4o3EDexGGhhtpy2RTe


On 7/2/19 4:26 am, stefan wrote:

Alexander,

I'm replying by re-adding some addresses, just so you don't miss Steven's reply below. Can you please try that and report back what you get ?

On 2019-02-06 12:13 p.m., Steven Watanabe via Boost-build wrote:
AMDG

On 2/6/19 7:22 AM, stefan via Boost-build wrote:
On 2019-02-04 8:54 p.m., Alexander Biddulph wrote:
Hi,

Finally managed to get around to rebuilding this with "-d2" added to
the command line. Here is a link to the build output
https://drive.google.com/open?id=1tlwj3-uGd6wsZ5qJcrD4Ms4RbaVMbDmC

As before, everything seems to be built and installed, except for the
python library.
As before, Boost.Build seems to find the python installation and says
it is going to build the python library, but just doesn't seem to get
around to doing it and there don't appear to be any errors that the
build system encountered.

I don't see anything obvious either. Steve, can you help with this ?

Try `--with-python --debug-building`  (--debug-building
generates way too much output if you build everything)
I suspect that you'll see "<build>no in common properties"
My best guess is that the problem is in python.require-py.
Maybe run under the debugger and set a breakpoint there.

In Christ,
Steven Watanabe
_______________________________________________
Unsubscribe & other changes: https://lists.boost.org/mailman/listinfo.cgi/boost-build

Stefan
--

      ...ich hab' noch einen Koffer in Berlin...
    

_______________________________________________
Cplusplus-sig mailing list
[hidden email]
https://mail.python.org/mailman/listinfo/cplusplus-sig

_______________________________________________
Unsubscribe & other changes: https://lists.boost.org/mailman/listinfo.cgi/boost-build

Attached Message Part (222 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

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

Boost - Build mailing list
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
_______________________________________________
Unsubscribe & other changes: https://lists.boost.org/mailman/listinfo.cgi/boost-build
Reply | Threaded
Open this post in threaded view
|

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

Boost - Build mailing list

Steven,

I'm not sure the author of the original mail is subscribed to the Boost-build list, so I'm cross-posting your reply.

On 2019-02-08 1:56 a.m., Steven Watanabe via Boost-build wrote:
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
_______________________________________________
Unsubscribe & other changes: https://lists.boost.org/mailman/listinfo.cgi/boost-build
--
Stefan
-- 

      ...ich hab' noch einen Koffer in Berlin...

_______________________________________________
Unsubscribe & other changes: https://lists.boost.org/mailman/listinfo.cgi/boost-build