Re: [C++-sig] [Boost-build] Boost 1.69 python3 module
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 Biddulph via Boost-build wrote:
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 ] ; This also results in a successful building and installation of the Boost.Python library (along with all the others). Here is the build output https://drive.google.com/open?id=1jNBu73JvFwcs8z0Om_o7bJ68x0KXCU4U
That makes no sense to me. The only thing that should be affected by this change is a few ECHO calls. Are you sure that everything else is the same? I see a new error: /nubots/toolchain/bin/python3: error while loading shared libraries: libpython3.6m.so.1.0: cannot open shared object file: No such file or directory
In Christ, Steven Watanabe _______________________________________________ Unsubscribe & other changes: https://lists.boost.org/mailman/listinfo.cgi/boost-build
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
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
participants (2)
-
Alex Biddulph -
Steven Watanabe