Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

liboctomap-dev used by FCL is ABI-incompatible with ros-*-octomap package #2862

Closed
henningkayser opened this issue Jun 7, 2024 · 3 comments
Assignees
Labels
dependencies Issues or PRs involving dependencies ros Issues involving ROS dependency and runtime best practices stale Inactive issues and PRs are marked as stale and may be closed automatically.

Comments

@henningkayser
Copy link
Member

There is an ABI conflict between the octomap versions provided by Ubuntu and by the rosdistro package.
liboctomap-dev is currently at 1.9.7 on Ubuntu jammy and noble and the ros-[jazzy/rolling]-octomap version is at 1.10, ros-humble-octomap is at 1.9.8. Linking both version obviously results in undefined behavior and segfaults.

Until this conflict is resolved, we are enforcing the system version liboctomap-dev by depending on libfcl-dev (only rosdep target that depends on liboctomap-dev, currently), and by specifying the version in the CMakeLists.txt of all packages in the build chain. A proper fix would require one of the following options:

  • getting liboctomap-dev synced with ros-*-octomap or vice versa
  • adding a liboctomap-dev rosdep target and keeping the version filters
  • switching to fcl-hpp which provides a proper ros package and only depends on the ros package of octomap
@henningkayser henningkayser added the ros Issues involving ROS dependency and runtime best practices label Jun 7, 2024
@henningkayser henningkayser self-assigned this Jun 7, 2024
@henningkayser henningkayser added the dependencies Issues or PRs involving dependencies label Jun 7, 2024
@henningkayser
Copy link
Member Author

liboctomap-dev is being added as rosdep key: ros/rosdistro#41623

Copy link

This issue is being labeled as stale because it has been open 45 days with no activity. It will be automatically closed after another 45 days without follow-ups.

@github-actions github-actions bot added the stale Inactive issues and PRs are marked as stale and may be closed automatically. label Jul 30, 2024
Copy link

This issue was closed because it has been stalled for 45 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 13, 2024
@github-project-automation github-project-automation bot moved this to ✅ Done in MoveIt Sep 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Issues or PRs involving dependencies ros Issues involving ROS dependency and runtime best practices stale Inactive issues and PRs are marked as stale and may be closed automatically.
Projects
None yet
Development

No branches or pull requests

1 participant