Problem linking with uuid.

[tiberiusferreira]

Originally posted at http://answers.ros.org/question/194158/bondcpp-fails-on-osx/?answer=194299#post-id-194299

I tried the solution from the tutorial. But doesn't work.
Result:

Built target roscpp_generate_messages_cpp
Linking CXX shared library /Users/tiberio/ros_catkin_ws/devel_isolated/bondcpp/lib/libbondcpp.dylib
ld: library not found for -luuid
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [/Users/tiberio/ros_catkin_ws/devel_isolated/bondcpp/lib/libbondcpp.dylib] Error 1
make[1]: *** [CMakeFiles/bondcpp.dir/all] Error 2
make: *** [all] Error 2
<== Failed to process package 'bondcpp':
  Command '/Users/tiberio/ros_catkin_ws/install_isolated/env.sh make -j8 -l8' returned non-zero exit status 2

Reproduce this error by running:
==> cd /Users/tiberio/ros_catkin_ws/build_isolated/bondcpp && /Users/tiberio/ros_catkin_ws/install_isolated/env.sh make -j8 -l8

Command failed, exiting.

I also did a run with VERBOSE=1, but the output is enormous, I'm not sure if I should post here. Anyway, it is in the original question link.

Apparently bondcpp or who ever is originally finding uuid is either not passing along the library directory or not converting the relative library (-L/usr/local/Cellar/uuid/1.6.2/lib -luuid) into an absolute library (maybe /usr/local/Cellar/uuid/1.6.2/lib/libuuid.dylib).

[wjwwood]

@esteve can you have a look at this once you get up and running again?

[tfoote]

This line looks less than portable: https://github.com/ros/bond_core/blob/master/bondcpp/CMakeLists.txt#L13

[tiberiusferreira]

Nope. I would really love a solution. =(

[wjwwood]

@aldofpr, @esteve will get to it as soon as he can, you're not the only person with deadlines and external circumstances.

As I understand it this only affects OS X, you can always dual boot your mac with Ubuntu or run a virtual machine in the mean time until this problem has been resolved.

Another option is to take the pointers given by others in the thread and try to solve the issue yourself; we're all engineers here, it only takes time and effort to solve problems like these.

[tfoote]

@aldofpr FYI If you havne't seen them our etiquette guidelines at http://wiki.ros.org/Support

[wjwwood]

@aldofpr I don't think you were rude, I just wanted you to know @esteve is going to look into as soon as he has time, just not right now, and in the mean time you can do the other things I suggested.

[esteve]

@tiberiusferreira I just pushed a pull request (#7) that uses find_package to find the UUID library and should be cross-platform, could test it?

[tiberiusferreira]

Awesome! I'll do a clean install and test it, because I did a clean yosemite install. Hope everything works.

[tiberiusferreira]

I want to report that ros did successfully compile under OS X Yosemite 10.10 with a clean install. No problems AT ALL! Fantastic ! I only had to install outside from the tutorial the XQuartz. I did not test everything yet, but roscore does work. Awesome work! Thanks a lot! Should I close the issue now?
PS: @aldofpr Did you manage to make it work too? I advice you to update to Yosemite if not. Everything seems smoother there.

[esteve]

Thanks for testing the patch. I can close it when I merge the pull request.
On Oct 23, 2014 4:22 AM, "tiberiusferreira" notifications@github.com
wrote:

I want to report that ros did successfully compile under OS X Yosemite
10.10 with a clean install. No problems AT ALL! Fantastic ! I only had to
install outside from the tutorial the XQuartz. I did not test everything
yet, but roscore does work. Awesome work! Thanks a lot! Should I close the
issue now?

—
Reply to this email directly or view it on GitHub
#6 (comment).

[esteve]

@tiberiusferreira I'm going to move this code to ros/cmake_modules since this issue also affects ros/nodelet with Yosemite

[esteve]

@tiberiusferreira A FindUUID.cmake module got merged into ros/cmake_modules, could you test #8 You'll need a recent copy of ros/cmake_modules in your workspace (at least ros/cmake_modules@b45081a)

[esteve]

This issue was addressed in 43df790