symbol lookup error when migrate from groovy to hydro

Hello, I have a problem running my plugins when I migrate from groovy to Hydro. I compiled everything from source using hydro The problem happens when I echo one of my laser sensors to display the message, and getting the following error: gzserver: symbol lookup error: /home/francesco/catkinws/src/sensors/lib/libopticalswitchcontroller.so: undefined symbol: _ZN3ros7console5printEPNS010FilterBaseEPN7log4cxx6LoggerENS06levels5LevelEPKciS9S9_z any ideas or suggestions please?

Best, Zahraa

Asked by Zahra on 2014-02-18 06:42:35 UTC

Comments

Please post what versions of gazebo, ros-hydro-rosconsole and ros-hydro-gazebo-ros have you installed.

Asked by Jose Luis Rivero on 2014-02-18 18:07:23 UTC

ros-hydro-gazebo-ros-pkgs 2.3.4-0 precise-20140208-0311-+0000, gazebo 1.9.41~precise ros hydro ros consolo 2.3.4

Asked by Zahra on 2014-02-19 12:51:58 UTC

Recently hydro update the rosconsole package breaking the ABI, it could be that you need to recompile your plugin. Does recompiling solve the problem?

Asked by Jose Luis Rivero on 2014-02-19 19:20:47 UTC

I updated ros-hydro-rosconsole (version 1.9.54 ). I re-compiled the plugins without any errors, but still has the same error when running it.

Asked by Zahra on 2014-02-20 09:46:17 UTC

Is the code available and easy to build? I can give it a look

Asked by Jose Luis Rivero on 2014-02-20 10:41:54 UTC

Answers

It looks like your plugin is not compiled correctly. Is it possible that your plugin is compiled against groovy, and you're running hydro?

Asked by nkoenig on 2014-02-19 14:40:07 UTC

Comments

C:\fakepath\pir_controller.cpp(/upfiles/139296625728578.cpp)

Hello, I attached the cpp file and the message.h file. Thanks in advance!

Asked by Zahra on 2014-02-21 02:06:45 UTC

Comments

C:\fakepath\pir_controller.cpp

here is the cpp file.

Asked by Zahra on 2014-02-21 02:11:03 UTC

Comments

There was another plugins in the same workspace that was compiled against groovy, which override the hydro compiled plugin and removing all the plugins of groovy, have solved the problem.

Asked by Zahra on 2014-02-27 03:40:18 UTC