Closed mmurooka closed 1 year ago
Hi @mmurooka
This could be due to one of two things:
ninja force-mc_rtc-python3-bindings
in mc_rtc build folder?unknown location(0): fatal error: in "RUN": std::runtime_error: boundedSpeed is already handled by another loading function
is that you have components loading old versions of mc_rtc at runtime along the current version (e.g some plugins still linked to 1.x)The later is a little unlikely these days because mc_rtc install rules systematically removes the previous installation (to avoid this specific issue among others).
I'm working towards a PR to improve incremental builds of Python bindings in https://github.com/gergondet/mc_rtc/tree/topic/ImproveCythonIncrementalBuilds which should hopefully circumvent the first issue for good (there's a long standing hack in the build_and_install script to trigger the force binding target on test failures)
Thanks for the explanation.
ABI issue with the Python bindings, that is because incremental builds of the bindings are not super reliable now, can you try to run ninja force-mc_rtc-python3-bindings in mc_rtc build folder?
After doing this, the tests passed.
After updating everything with mc-rtc-superbuild, I got the following error.