0

I am getting this at runtime:

./LibTestApp: symbol lookup error: libaxis2_mod_addr.so: undefined symbol: axis2_handler_create

on command user1@ubuntu:nm path/libaxis2_mod_addr.so | grep axis2_handler_create the output is:U axis2_handler_createwhere U confirms that it's undefined.

on command user1@ubuntu:ldd path/libaxis2_mod_addr.so i get:

linux-gate.so.1 => (0xb7787000)
libaxis2_axiom.so.0 => /opt/wso2/wsf_cpp/lib/libaxis2_axiom.so.0 (0xb7749000)
libaxutil.so.0 => /opt/wso2/wsf_cpp/lib/libaxutil.so.0 (0xb771e000)
libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xb7553000)
libaxis2_parser.so.0 => /opt/wso2/wsf_cpp/lib/libaxis2_parser.so.0 (0xb754a000)
libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xb752f000)
libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xb752a000)
/lib/ld-linux.so.2 (0xb7788000)
libguththila.so.0 => /opt/wso2/wsf_cpp/lib/libguththila.so.0 (0xb7519000)

No one of this linked libraries contains axis2_handler_create and no one is linked with libaxis2_engine witch contains disired symbol(axis2_handler_create).

Is this a bug from WSF generate on building the framework described by missing the link to needed library? Or am i missing something? Any ideas how can i solve my problem?

EDIT:

Forgot to mention, code that load this library have been generated by wsdl2cpp tool based on Onvif WSDL files from here. In my case it's just devicemgmt.wsdl and media.wsdl.

Straticiuc Vicu
  • 102
  • 3
  • 12

0 Answers0