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

Linking problem with ROS2 Foxy deb package #299

Closed
macale-fitech opened this issue Jul 28, 2021 · 0 comments
Closed

Linking problem with ROS2 Foxy deb package #299

macale-fitech opened this issue Jul 28, 2021 · 0 comments
Assignees

Comments

@macale-fitech
Copy link

Greetings,

I was debugging a problem of undefined linking references to BT in my ROS2 Foxy project, where I tried to use ros-foxy-behaviortree-cpp-v3 from the official ROS2 apt repository for Ubuntu 20.04 ( http://packages.ros.org/ros2/ubuntu/dists/focal/main/binary-amd64/Packages , find "Package: ros-foxy-behaviortree-cpp-v3" ). Here is a fragment of the linker output:

...
wait_for_variable.cpp:(.text+0x48c): undefined reference to `BT::CoroActionNode::setStatusRunningAndYield()'
/usr/bin/ld: wait_for_variable.cpp:(.text+0x59d): undefined reference to `BT::CoroActionNode::setStatusRunningAndYield()'
/usr/bin/ld: wait_for_variable.cpp:(.text+0x617): undefined reference to `BT::CoroActionNode::setStatusRunningAndYield()'
/usr/bin/ld: wait_for_variable.cpp:(.text+0x6c9): undefined reference to `BT::CoroActionNode::setStatusRunningAndYield()'
/usr/bin/ld: wait_for_variable.cpp:(.text+0x762): undefined reference to `BT::CoroActionNode::setStatusRunningAndYield()'
...

I have managed to overcome this issue by cloning the current master branch (278e60e). Of course, such solution is inconvenient in terms of freezing dependencies for the project. I looked further into the tags and I have found the potential source of the problem: manually building the tag 3.5.6 resulted in successful compilation. On the other hand the latest official release ( https://github.com/BehaviorTree/BehaviorTree.CPP/releases ) the tag 3.3.0 failed the build process. I speculate that the deb package in the ROS2 repository is actually older than 3.5.6 and it is probably based on the "latest release" 3.3.0 .

Regardless of my hypothesis I would like to highlighted this problem.
Thanks in advance for looking into this issue.
Maciej

@macale-fitech macale-fitech changed the title Wrong release tag for ROS2 Foxy deb package Linking problem with ROS2 Foxy deb package Jul 28, 2021
@facontidavide facontidavide self-assigned this Mar 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants