ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question
0

Conflicting libtinyxml libraries - Kinetic

asked 2017-07-31 12:49:16 -0500

Dave Coleman gravatar image

After a recent update I now am getting lots of warnings from catkin/cmake:

CMake Warning at /home/dave/ros/current/ws_moveit/src/moveit/moveit_setup_assistant/CMakeLists.txt:132 (add_executable):
  Cannot generate a safe linker search path for target
  moveit_setup_assistant_updater because files in some directories may
  conflict with libraries in implicit directories:

    link library [libtinyxml.so] in /usr/lib/x86_64-linux-gnu may be hidden by files in:
      /opt/ros/kinetic/lib

  Some of these libraries may not be found correctly.

It seems Kinetic is now shipping with

/opt/ros/kinetic/lib/libtinyxml.so

But ROS debians still depend on the system version:

/usr/lib/x86_64-linux-gnu/libtinyxml.a
/usr/lib/x86_64-linux-gnu/libtinyxml.so
/usr/lib/x86_64-linux-gnu/libtinyxml2.so.2.2.0
/usr/lib/x86_64-linux-gnu/libtinyxml.so.2.6.2
/usr/lib/x86_64-linux-gnu/libtinyxml2.so.2
/usr/share/doc/libtinyxml2.6.2v5
/usr/share/doc/libtinyxml-dev
/usr/share/doc/libtinyxml2-2v5

How did duplicate happen? How can I remove the hundreds of warnings? It also seems to broken my build of ros-kinetic-srdfdom.

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
0

answered 2017-07-31 12:56:58 -0500

Dave Coleman gravatar image

updated 2017-07-31 15:08:07 -0500

edit flag offensive delete link more

Comments

This isn't really an answer is it? I mean I guess it's the cause, but the solution there is to support both versions so it compiles. It doesn't address your linking warnings I think.

William gravatar image William  ( 2017-07-31 14:01:02 -0500 )edit

I'm trying to track down which package is installing the tinyxml lib to /opt/ros now. I'd say we need to raise the issue on the issue tracker of the that package.

William gravatar image William  ( 2017-07-31 14:02:21 -0500 )edit

nvm, I misread the issue. It is the one responsible, so once it is updated to work with the system one, it will no longer install its own. So this is the answer. Sorry for the noise.

William gravatar image William  ( 2017-07-31 14:08:21 -0500 )edit

Thanks for your help William!

Dave Coleman gravatar image Dave Coleman  ( 2017-07-31 15:08:25 -0500 )edit

Question Tools

1 follower

Stats

Asked: 2017-07-31 12:49:16 -0500

Seen: 611 times

Last updated: Jul 31 '17