I'm having problems building the python extensions for openbabel on essentially
virgin installation of snowleopard (thanks to a corrupted boot disk). When I
build and install openbabel-2.3.0 itself, everything is fine, and I can use
babel from the command line without any difficulty, but when I include the
python extensions, I can import pybel just fine, but as soon as I actually make
a call to the libraries, it segfaults and generates a crash report for the nice
people in Cupertino. This isn't tied to how I install it, because when I
enable testing, make tests returns with 6 failed tests, all of the python
tests. The others are all fine. I checked with google, and I saw the note
about mac builds binding to the wrong dynamic library, but in the traceback
from the segfault, there are no references to my home directory, and all
attempts to find _openbabel.so are to where it should be
(/Library/Python/2.6/site-packages ).
The code that generates the segfault is:
import pybel
mymol=pybel.readstring( "smi", "CCCC")
(the segfault actually claims to be coming from the smilesformat.so plugin, for
what it's worth)
Can anyone make any suggestions?
Also, as an FYI, the way that the cmake files notify people about whether the
GUI will be built and where libxml2 is found is parsed as an error by ccmake,
which prevents using that tool to configure the build. Is there any chance
that the notification method can be made more ccmake friendly?
Thanks,
Andy
------------------------------------------------------------------------------
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software
be a part of the solution? Download the Intel(R) Manageability Checker
today! http://p.sf.net/sfu/intel-dev2devmar
_______________________________________________
OpenBabel-scripting mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openbabel-scripting
