ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
What is in catkin_LIBRARIES
? If it includes any package which you've installed from the buildfarm provided binaries for Noetic, that's going to bring in the platform's default Boost.
SEGFAULT
s are typically a result of mixing different Boost versions, and you seem to have observed those.
I believe the only robust way to avoid this is to build Noetic from source against the same Boost version you're bringing in from the SLTC_SDK_LIB_DIR
.
If you don't actually absolutely need to run this all natively under Noetic, I would suggest to use some sort of container technology to run just this one node in a Docker container which packs just this node and its dependencies (which would include ROS Indigo, which I assume is where the Boost 1.53 comes from).
2 | No.2 Revision |
What is in catkin_LIBRARIES
? If it includes any package which you've installed from the buildfarm provided binaries for Noetic, that's going to bring in the platform's default Boost.
Seeing as you're using ROS, and this is a C++ program, I would assume at least roscpp
is there.
SEGFAULT
s are typically a result of mixing different Boost versions, and you seem to have observed those.
I believe the only robust way to avoid this is to build Noetic from source against the same Boost version you're bringing in from the SLTC_SDK_LIB_DIR
.
If you don't actually absolutely need to run this all natively under Noetic, I would suggest to use some sort of container technology to run just this one node in a Docker container which packs just this node and its dependencies (which would include ROS Indigo, which I assume is where the Boost 1.53 comes from).
3 | No.3 Revision |
What is in catkin_LIBRARIES
? If it includes any package which you've installed from the buildfarm provided binaries for Noetic, that's going to bring in the platform's default Boost.
Seeing as you're using ROS, and this is a C++ program, I would assume at least roscpp
is there.
SEGFAULT
s are typically a result of mixing different Boost versions, and you seem to have observed those.
I believe the only robust way to avoid this is to build Noetic from source against the same Boost version you're bringing in from the SLTC_SDK_LIB_DIR
.. But seeing there are quite some differences between 1.53
and the Noetic native 1.71
, that will most likely be problematic, if not impossible.
If you don't actually absolutely need to run this all natively under Noetic, I would suggest to use some sort of container technology to run just this one node in an isolated environment (fi: a Docker container which packs container). That environment would pack just this node and its dependencies (which would include probably includes ROS Indigo, Indigo (?), which I assume is where the Boost 1.53 comes from).
4 | No.4 Revision |
What is in catkin_LIBRARIES
? If it includes any package which you've installed from the buildfarm provided binaries for Noetic, that's going to bring in the platform's default Boost.
Seeing as you're using ROS, and this is a C++ program, I would assume at least roscpp
is there.
I am wondering why this is the case, how could I solve it?
SEGFAULT
s are typically a result of mixing different Boost versions, and you seem to have observed those.
I believe the only robust way to avoid this is to build Noetic from source against the same Boost version you're bringing in from the SLTC_SDK_LIB_DIR
. But seeing there are quite some differences between 1.53
and the Noetic native 1.71
, that will most likely be problematic, if not impossible.
If you don't actually absolutely need to run this all natively under Noetic, I would suggest to use some sort of container technology to run just this one node in an isolated environment (fi: a Docker container). That environment would pack just this node and its dependencies (which probably includes ROS Indigo (?), which I assume is where the Boost 1.53 comes from).
5 | No.5 Revision |
What is in catkin_LIBRARIES
? If it includes any package which you've installed from the buildfarm provided binaries for Noetic, that's going to bring in the platform's default Boost.
Seeing as you're using ROS, and this is a C++ program, I would assume at least roscpp
is there.
I am wondering why this is the case, how could I solve it?
SEGFAULT
s are typically a result of mixing different Boost versions, and you seem to have observed those.those (it's not limited to Boost of course: (transitively) linking different versions of the same library often doesn't work).
I believe the only robust way to avoid this is to build Noetic from source against the same Boost version you're bringing in from the SLTC_SDK_LIB_DIR
. But seeing there are quite some differences between 1.53
and the Noetic native 1.71
, that will most likely be problematic, if not impossible.
If you don't actually absolutely need to run this all natively under Noetic, I would suggest to use some sort of container technology to run just this one node in an isolated environment (fi: a Docker container). That environment would pack just this node and its dependencies (which probably includes ROS Indigo (?), which I assume is where the Boost 1.53 comes from).