Thanks Brian you are a star :)
> Send Playerstage-users mailing list submissions to
> To subscribe or unsubscribe via the World Wide Web, visit
> or, via email, send a message with subject or body 'help' to
> You can reach the person managing the list at
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Playerstage-users digest..."
> Today's Topics:
> 1. Re: player plugin __dso_handle error (Brian Gerkey)
> 2. Re: player-2.0pre6 --with-gazebo DNC (Brian Gerkey)
> Message: 1
> Date: Tue, 17 Jan 2006 09:44:24 -0800
> From: Brian Gerkey <brian@...>
> To: playerstage-users@...
> Subject: Re: [Playerstage-users] player plugin __dso_handle error
> Reply-To: playerstage-users@...
> Joseph Baxter wrote:
>>Parsing configuration file "miabot.cfg"
>>trying to load /home/jlb/player_b/./miabot.so...failed
>>(/home/jlb/player_b/./miabot.so: undefined symbol: __dso_handle)
>>trying to load miabot.so...failed (miabot.so: cannot open shared object
>>file: No such file or directory)
>>error : error loading plugin: (null)
>>error : failed to load plugin: miabot.so
>>I get the above error when trying to load a plugin I have written, I use
>>the following commands to compile/link:
>>$ g++ -Wall -g3 -c miabot.cc miabot_commands.cc miabot_params.cc
>>$ g++ -shared -nostartfiles -o miabot.so miabot.o miabot_commands.o
> That unresolved symbol is internal to the C (or maybe C++) runtime; the
> error is a symptom of an incorrect or incomplete link. A common cause
> is using ld instead of g++ for linking, but you're already using g++,
> which is the right way to do it.
> I would try removing the -nostartfiles option to g++. I know it's in
> the example Makefile for Player plugins, but it shouldn't be necessary
> since we moved from '_init()' to 'player_driver_init()' for plugin
Automated Scheduling, Optimisation and Planning Group
School of Computer Science and Information Technology
University of Nottingham
Tel: (0115) 95 14247
This message has been checked for viruses but the contents of an attachment
may still contain software viruses, which could damage your computer system:
you are advised to perform your own checks. Email communications with the
University of Nottingham may be monitored as permitted by UK legislation.