openbabel-scripting

[openbabel-scripting] Re: "did not load properly"

[Thomas H. <thu...@t2...>]

Hello,

I'm having the same "*.so did not load properly" problem with python, ope=
nbabel and linux (suse 9.1).

Geoffrey Hutchison wrote:=20

>> Do you think we coudl statically link them? Where is the code that =20
>> loads
>> them dynamically?
>
>You don't want to statically link them. In fact, there are problems =20
>with the static builds of Open Babel because the linking is tricky.
>
>The C++ code that loads the file formats is in src/=20
>dlhandler_unix.cpp. It has no error messages like the ones you =20
>report, which is why I don't know what to debug. :-(

The error message probably comes from LoadFormatFiles in obconversion.cpp=
 (if that helps to debug;-)
      =20
for(itr=3Dfiles.begin();itr!=3Dfiles.end();itr++)
    {
        if(DLHandler::openLib(*itr))
            count++;
        else
            cerr << *itr << " did not load properly" << endl;
     }

which would scream if dlopen in dlhandler_unix.cpp fails.=20

If I let dlerror() print, I get the message:
/usr/local/lib/openbabel/chem3dformat.so: undefined symbol: _ZN9OpenBabel=
8OBFormat22TargetClassDescriptionEv
Which doesn't mean anything to me, but maybe there is someone out there s=
marter?

Having a working python binding, would be really lovely, txs.

Bye
Thomas=20

--=20
Dr. Thomas H=FCbner
T2-Consult Wein & H=FCbner,  M=FCnchen

Phone: +49 (89) 21 58 16 80
http://www.t2-consult.de

Re: [openbabel-scripting] Re: "did not load properly"

[Geoffrey H. <ge...@ge...>]

On Dec 2, 2005, at 3:21 PM, Thomas Huebner wrote:

> The error message probably comes from LoadFormatFiles in  
> obconversion.cpp (if that helps to debug;-)
> ...
>            cerr << *itr << " did not load properly" << endl;

Yes, thanks.

> which would scream if dlopen in dlhandler_unix.cpp fails.
> If I let dlerror() print, I get the message:
> /usr/local/lib/openbabel/chem3dformat.so: undefined symbol:  
> _ZN9OpenBabel8OBFormat22TargetClassDescriptionEv

Well, that was very helpful -- it's a "mangled" C++ debugging symbol.  
If you use c++filt to decode, you get:
OpenBabel::OBFormat::TargetClassDescription()

Hmm, I'll have to see what's going on there. Maybe the Linux loader  
isn't resolving that symbol in the libopenbabel library?

Thanks,
-Geoff