ArduPilot / ArduPilot/OctomapPlanner

error when compiling main_node

Open
#13 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
163
Forks
43
PR merge metrics
No merged PRs in 30d

Description

/usr/bin/ld: warning: liboctomap.so.1.8, needed by libArduPlanner.so, may conflict with liboctomap.so.1.6
libPlanner.so:对‘fcl::CollisionGeometry::~CollisionGeometry()’未定义的引用
libPlanner.so:对‘fcl::CollisionObject::CollisionObject(std::shared_ptr > const&)’未定义的引用
libPlanner.so:对‘unsigned long fcl::collide(fcl::CollisionObject const*, fcl::CollisionObject const*, fcl::CollisionRequest const&, fcl::CollisionResult&)’未定义的引用
libPlanner.so:对‘fcl::CollisionResult::isCollision() const’未定义的引用
libPlanner.so:对‘vtable for fcl::ShapeBase’未定义的引用
libPlanner.so:对‘fcl::OcTree::OcTree(std::shared_ptr const&)’未定义的引用
libPlanner.so:对‘fcl::Box::Box(double, double, double)’未定义的引用
libPlanner.so:对‘fcl::CollisionRequest::CollisionRequest(unsigned long, bool, unsigned long, bool, bool, fcl::GJKSolverType, double)’未定义的引用
libPlanner.so:对‘fcl::CollisionObject::setTranslation(Eigen::Matrix const&)’未定义的引用
libPlanner.so:对‘fcl::CollisionObject::~CollisionObject()’未定义的引用
libPlanner.so:对‘fcl::CollisionResult::CollisionResult()’未定义的引用
collect2: error: ld returned 1 exit status
CMakeFiles/main_node.dir/build.make:433: recipe for target 'main_node' failed
make[2]: *** [main_node] Error 1
CMakeFiles/Makefile2:77: recipe for target 'CMakeFiles/main_node.dir/all' failed
make[1]: *** [CMakeFiles/main_node.dir/all] Error 2
Makefile:83: recipe for target 'all' failed
make: *** [all] Error 2

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the main_node build and inspect CMakeFiles/main_node.dir/build.make and the target's link configuration. Trace how libPlanner.so and libArduPlanner.so are linked, including the conflicting liboctomap.so.1.8 and liboctomap.so.1.6 versions. Done means make completes successfully and main_node links without the reported FCL or OctoMap errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
cmake, cpp
Domain
build-system, robotics
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.