Ok, I played around a bit more.
It was indeed configuring python twice. Likely because the bootstrap.sh
script adds this bit to project-config.jam
# Python configuration
import python ;
if ! [ python.configured ]
{
using python : 3.6 : /nubots/toolchain ;
}
which results in a non-working p
AMDG
On 2/18/19 9:09 PM, Alex Biddulph wrote:
> Not sure what happened there, I must have dirtied my build environment.
>
> I cleaned everything up and ran it again. Here is the output.
> https://drive.google.com/open?id=1u_8KHpjuAC2Cm0jGrVOdGvaqxFtslhNm
>
The problem is that you are configurin
Not sure what happened there, I must have dirtied my build environment.
I cleaned everything up and ran it again. Here is the output.
https://drive.google.com/open?id=1u_8KHpjuAC2Cm0jGrVOdGvaqxFtslhNm
On 16/2/19 5:39 am, Steven Watanabe via Boost-build wrote:
> AMDG
>
> On 2/12/19 3:31 PM, Alex B
> 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 c
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 rep
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
