It should be Python 2.7, but it is possible I did something wrong there. I will 
dig into it. The way you build stuff with Python is very unfamiliar to me. I 
will take a look as I think python is python3, and python2 is python 2.7.

Marcus

On Mar 4, 2011, at 12:08 PM, Noel O'Boyle wrote:

> Are you using Python 3.2? SWIG doesn't yet support this.
> 
> - Noel
> 
> On 4 March 2011 16:59, Marcus D. Hanwell <marcus.hanw...@kitware.com> wrote:
>> On Fri, Mar 4, 2011 at 11:35 AM, Noel O'Boyle <baoille...@gmail.com> wrote:
>>> On 4 March 2011 16:13, Marcus D. Hanwell <marcus.hanw...@kitware.com> wrote:
>>>> On Fri, Mar 4, 2011 at 11:11 AM, Geoffrey Hutchison
>>>> <ge...@geoffhutchison.net> wrote:
>>>>> 
>>>>> On Mar 3, 2011, at 1:56 PM, Marcus D. Hanwell wrote:
>>>>> 
>>>>>> I can probably take a pass at improving this, it will involve several
>>>>>> changes to the CMake code though. Is this a good time to do that?
>>>>> 
>>>>> Yes. I'll be traveling the next week, so I don't anticipate a 2.3.1 
>>>>> release for at least a few weeks.
>>>>> 
>>>>> If you have a chance, there's also the Mac/Python issue I mentioned (that 
>>>>> _openbabel.so doesn't get linked against the installed libopenbabel.dylib 
>>>>> but stays linked to ${CMAKE_BUILD_DIR}/libopenbabel.dylib). It's pretty 
>>>>> easy to reproduce, since "make install; otool -L 
>>>>> /Library/Python/2.6/site-packages/_openbabel.so" shows the wrong library 
>>>>> path.
>>>>> 
>>>> Is SWIG 2.0.2 known broken? That is what I have installed here and it
>>>> fails to compile even the Python bindings. I should be able to get
>>>> 2.0.1 or something on the Mac and take a look at it there. I see in
>>>> the code you are only accepting 2.0.0 and 2.0.1, but I am also using
>>>> GCC 4.5 which can cause some issues occasionally too.
>>> 
>>> Feel free to update the code to also accept 2.0.2. We've always used
>>> the latest SWIG to prepare the release. (I'd suggest removing the
>>> others but it'll make work for me to go around the buildbots and
>>> recompile SWIG.)
>>> 
>> I get quite a few compilation failures here, and don't know
>> SWIG/OpenBabel's Python bindings well enough to be able to fix it... A
>> small sample of the first few (all look quite similar):
>> 
>> building '_openbabel' extension
>> gcc -pthread -DNDEBUG -march=x86-64 -mtune=generic -O2 -pipe
>> -I/usr/include/eigen2 -fPIC
>> -I/home/marcus/ssd/src/openbabel/scripts/python/../../include
>> -I../include -I/usr/include/python2.7 -c
>> /home/marcus/ssd/src/openbabel/scripts/python/openbabel-python.cpp -o
>> build/temp.linux-x86_64-2.7/home/marcus/ssd/src/openbabel/scripts/python/openbabel-python.o
>> /home/marcus/ssd/src/openbabel/scripts/python/openbabel-python.cpp: In
>> function ‘std::vector<int>*
>> std_vector_Sl_int_Sg____getitem____SWIG_0(std::vector<int>*,
>> PyObject*)’:
>> /home/marcus/ssd/src/openbabel/scripts/python/openbabel-python.cpp:4587:60:
>> error: cannot convert ‘PyObject*’ to ‘PySliceObject*’ for argument ‘1’
>> to ‘int PySlice_GetIndices(PySliceObject*, Py_ssize_t, Py_ssize_t*,
>> Py_ssize_t*, Py_ssize_t*)’
>> /home/marcus/ssd/src/openbabel/scripts/python/openbabel-python.cpp: In
>> function ‘void std_vector_Sl_int_Sg____setitem____SWIG_0(std::vector<int>*,
>> PyObject*, const std::vector<int>&)’:
>> /home/marcus/ssd/src/openbabel/scripts/python/openbabel-python.cpp:4596:60:
>> error: cannot convert ‘PyObject*’ to ‘PySliceObject*’ for argument ‘1’
>> to ‘int PySlice_GetIndices(PySliceObject*, Py_ssize_t, Py_ssize_t*,
>> Py_ssize_t*, Py_ssize_t*)’
>> /home/marcus/ssd/src/openbabel/scripts/python/openbabel-python.cpp: In
>> function ‘void std_vector_Sl_int_Sg____delitem____SWIG_1(std::vector<int>*,
>> PyObject*)’:
>> /home/marcus/ssd/src/openbabel/scripts/python/openbabel-python.cpp:4605:60:
>> error: cannot convert ‘PyObject*’ to ‘PySliceObject*’ for argument ‘1’
>> to ‘int PySlice_GetIndices(PySliceObject*, Py_ssize_t, Py_ssize_t*,
>> Py_ssize_t*, Py_ssize_t*)’
>> /home/marcus/ssd/src/openbabel/scripts/python/openbabel-python.cpp: In
>> function ‘std::vector<unsigned int>*
>> std_vector_Sl_unsigned_SS_int_Sg____getitem____SWIG_0(std::vector<unsigned
>> int>*, PyObject*)’:
>> /home/marcus/ssd/src/openbabel/scripts/python/openbabel-python.cpp:4697:60:
>> error: cannot convert ‘PyObject*’ to ‘PySliceObject*’ for argument ‘1’
>> to ‘int PySlice_GetIndices(PySliceObject*, Py_ssize_t, Py_ssize_t*,
>> Py_ssize_t*, Py_ssize_t*)’
>> 
> 
> ------------------------------------------------------------------------------
> What You Don't Know About Data Connectivity CAN Hurt You
> This paper provides an overview of data connectivity, details
> its effect on application quality, and explores various alternative
> solutions. http://p.sf.net/sfu/progress-d2d
> _______________________________________________
> OpenBabel-Devel mailing list
> OpenBabel-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openbabel-devel
> 


------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________
OpenBabel-Devel mailing list
OpenBabel-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openbabel-devel

Reply via email to