catkin_make only working with -j1 option, giving compile error otherwise?

asked 2013-07-31 11:58:09 -0500

24361 ●173 ●299 ●444 https://www.energy-rob...

updated 2014-01-28 17:17:30 -0500

ngrennan
1 ●1 ●1

We are working with a pretty large catkin project that compiled just fine for months. Without code changes, we started seeing compile errors after some groovy updates and building from scratch, looking like:

[  2%] Building CXX object flor_common/flor_interactive_marker_server_custom/CMakeFiles/flor_interactive_marker_server_custom.dir/src/interactive_marker_server_custom.cpp.o
In file included from /home/kohlbrecher/flor_repo/catkin_ws/src/flor_common/flor_interactive_marker_server_custom/src/interactive_marker_server_custom.cpp:68:0:
/home/kohlbrecher/flor_repo/catkin_ws/src/flor_common/flor_interactive_marker_server_custom/include/flor_interactive_marker_server_custom/interactive_marker_server_custom.h:80:45: fatal error: flor_ocs_msgs/OCSTemplateUpdate.h: No such file or directory
compilation terminated.
make[2]: *** [flor_common/flor_interactive_marker_server_custom/CMakeFiles/flor_interactive_marker_server_custom.dir/src/interactive_marker_server_custom.cpp.o] Error 1
make[1]: *** [flor_common/flor_interactive_marker_server_custom/CMakeFiles/flor_interactive_marker_server_custom.dir/all] Error 2
make: *** [all] Error 2
make: INTERNAL: Exiting with 3 jobserver tokens available; should be 2!
Invoking "make" failed

Noticing that the actual error messages changed when executing "catkin_make" multiple times, I figured there might be some issue with parallel jobs and different timings leading to different errors. Sure enough, when running "catkin_make -j1", the project compiles. Any ideas if there's something on our side making this error appear, or if this is a catkin bug?

edit retag flag offensive close merge delete

add a comment

Comments

Dirk, does this mean that beside the declaration in package.xml and in find_package(catkin ...) a dependency to ${catkin_EXPORTED_TARGETS} or flor_ocs_msgs_generate_messages_cpp has to be declared for every single target in each dependent package that uses the generated headers?!?

Johannes Meyer ( 2013-08-24 12:18:29 -0500 )edit

Yes, you need a target-level dependency between the target which uses the generated message headers and the target which generates the message headers.