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 _______________________________________________ Cplusplus-sig mailing list Cplusplus-sig@python.org https://mail.python.org/mailman/listinfo/cplusplus-sig
