> 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
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
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,
Hi Alexander,
On 2019-01-28 9:02 p.m., Alexander Biddulph wrote:
Hopefully this is the right list for this.
It is, though the issue may be more related to the Boost build system
(b2 / Boost.Build), so I'm cross-posting to try to get their attention, too.
I have been struggling to get
Hopefully this is the right list for this.
I have been struggling to get Boost 1.69 to build Boost.Python against Python
3.6.3.
I have specified the location of the python binary, include, and library (due
to a non-standard install location) in the project-config.jam file in the Boost
source
