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 python configuration due to the
incorrectly determined include path "{prefix}/include/python3.6". The
correct include path should be "{prefix}/include/python3.6m". This was
the root cause of my problem, which is why I added
using python : 3.6 : "{prefix}/bin/python3" :
"{prefix}/include/python3.6m" : "{prefix}/lib" ;
to the end of project-config.jam, hoping it would override the previous
configuration and use the correct paths for my installation. Which
resulted in this discussion.
On 19/2/19 3:24 pm, Steven Watanabe wrote:
> 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 configuring python twice.
> Please make sure that you only have one `using python`
> statement in your project-config.jam (or any other
> configuration file). This is a really obscure failure
> mode and I'll look into making a better message. You
> might file a ticket at https://github.com/boostorg/build/
>
> In Christ,
> Steven Watanabe
_______________________________________________
Cplusplus-sig mailing list
Cplusplus-sig@python.org
https://mail.python.org/mailman/listinfo/cplusplus-sig
