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

re_comm build error in roboearth installation (ROS Fuerte + Ubuntu 12.04)

asked 2013-01-08 10:44:03 -0500

Hi everyone,

I am trying to install RoboEarth within ROS Fuerte in Ubuntu 12.04. I looked over all answers concerning roboearth installation errors but found nothing like this. My installation fails when building the last package, namely re_comm. Can anyone help me? This is the relevant output:

[rosmake-0] Finished <<< re_ontology [PASS] [ 350.35 seconds ]                  
[rosmake-0] Starting >>> re_comm [ make ]                                       
[ rosmake ] Last 40 lines_comm: 403.8 sec ]        [ 1 Active 102/103 Complete ]
{-------------------------------------------------------------------------------
                    CommunicationVisApplet.visualizeCommunication("", "Export of model for Cop ID "+req.object_id+" failed.", null, null);
                    ^
  /home/asimo/ros/stacks/roboearth/re_comm/src/roboearth/wp1/UnizarRoboEarthInterface.java:437: cannot find symbol
  symbol  : variable CommunicationVisApplet
  location: class roboearth.wp1.UnizarRoboEarthInterface.RetrieveCopModelCallback
                    CommunicationVisApplet.visualizeCommunication("Requesting model for object '"+req.object_name+"' from RoboEarth...", "", null, "roboearth.png");
                    ^
  /home/asimo/ros/stacks/roboearth/re_comm/src/roboearth/wp1/UnizarRoboEarthInterface.java:460: cannot find symbol
  symbol  : variable CommunicationVisApplet
  location: class roboearth.wp1.UnizarRoboEarthInterface.RetrieveCopModelCallback
                        CommunicationVisApplet.visualizeCommunication("", "Object model download finished.\n\n"+targetFolderFile.getName(), null, null);
                        ^
  /home/asimo/ros/stacks/roboearth/re_comm/src/roboearth/wp1/UnizarRoboEarthInterface.java:513: cannot find symbol
  symbol  : variable CommunicationVisApplet
  location: class roboearth.wp1.UnizarRoboEarthInterface.RetrieveCopModelCallback
                            CommunicationVisApplet.visualizeCommunication("Sending model for object '"+req.object_name+"' to the vision system...\n\n"+xmlFileName, "", null, "cop.png");
                            ^
  /home/asimo/ros/stacks/roboearth/re_comm/src/roboearth/wp1/UnizarRoboEarthInterface.java:523: cannot find symbol
  symbol  : variable CommunicationVisApplet
  location: class roboearth.wp1.UnizarRoboEarthInterface.RetrieveCopModelCallback
                            CommunicationVisApplet.visualizeCommunication("", "Object model "+xmlFileName+" received.", null, null);
                            ^
  /home/asimo/ros/stacks/roboearth/re_comm/src/roboearth/wp1/UnizarRoboEarthInterface.java:536: cannot find symbol
  symbol  : variable CommunicationVisApplet
  location: class roboearth.wp1.UnizarRoboEarthInterface.RetrieveCopModelCallback
                        CommunicationVisApplet.visualizeCommunication("", "No model for "+req.object_name+" found.", null, null);
                        ^
  /home/asimo/ros/stacks/roboearth/re_comm/src/roboearth/wp1/UnizarRoboEarthInterface.java:548: cannot find symbol
  symbol  : variable CommunicationVisApplet
  location: class roboearth.wp1.UnizarRoboEarthInterface.RetrieveCopModelCallback
                CommunicationVisApplet.visualizeCommunication("", "No model for "+req.object_name+" found.", null, null);
                ^
  42 errors
  make[3]: *** [../bin/roboearth/wp5/CopRoboEarthInterface.class] Error 1
  make[3]: Leaving directory `/home/asimo/ros/stacks/roboearth/re_comm/build'
  make[2]: *** [CMakeFiles/_java_compile_1_68.dir/all] Error 2
  make[2]: Leaving directory `/home/asimo/ros/stacks/roboearth/re_comm/build'
  make[1]: *** [all] Error 2
  make[1]: Leaving directory `/home/asimo/ros/stacks/roboearth/re_comm/build'
-------------------------------------------------------------------------------}
[ rosmake ] Output from build of package re_comm written to:
[ rosmake ]    /home/asimo/.ros/rosmake/rosmake_output-20130108-200745/re_comm/build_output.log
[rosmake-0] Finished <<< re_comm [FAIL] [ 403.89 seconds ]                      
[ rosmake ] Halting due to failure in package re_comm. 
[ rosmake ] Waiting for other threads to complete.
[ rosmake ] Results:                                                            
[ rosmake ] Built 103 packages with 1 failures.                                 
[ rosmake ] Summary output to directory                                         
[ rosmake ] /home/asimo/.ros/rosmake/rosmake_output-20130108-200745

Thanks in advance!

edit retag flag offensive close merge delete

2 Answers

Sort by ยป oldest newest most voted
3

answered 2013-02-17 11:13:41 -0500

alexiip gravatar image

As mentioned in another answer, it seems like its due to some refactoring in KnowRob.

So after you checkout the latest source code into your ROS_PACKAGE_PATH as described by @mortiz.

(I have not checked if this would work without the new package... you may try replacing the import line first before attempting to pull in knew knowrob)

svn co http://code.in.tum.de/pubsvn/knowrob/tags/latest knowrob

Replace the following import line with the one below it in the files which are causing this problem:

import de.tum.in.fipm.kipm.gui.visualisation.applets.CommunicationVisApplet; //delete

import edu.tum.cs.ias.knowrob.vis.applets.CommunicationVisApplet; //add

/roboearth/re_comm/src/roboearth/wp5/CopRoboEarthInterface.java
/roboearth/re_comm/src/roboearth/wp5/REClients.java
/roboearth/re_comm/src/roboearth/wp1/UnizarRoboEarthInterface.java
edit flag offensive delete link more
1

answered 2013-01-28 23:51:24 -0500

moritz gravatar image

This is related to a refactoring in the KnowRob stack that changed some namespaces. You may need to install KnowRob from source by checking it out somewhere into your ROS_PACKAGE_PATH:

svn co http://code.in.tum.de/pubsvn/knowrob/tags/latest knowrob

Otherwise you can also just comment out those lines where 'CommunicationVisApplet' appears.

edit flag offensive delete link more

Comments

1

Pulling new code did not seem to fix it. I guess commenting out is the only way.

alexiip gravatar image alexiip  ( 2013-02-17 09:54:17 -0500 )edit

Question Tools

Stats

Asked: 2013-01-08 10:44:03 -0500

Seen: 478 times

Last updated: Feb 17 '13