Thanks for not giving up on me!
I figured out the version problem -- it was installing into
/usr/local/bin/bin instead of /usr/local/bin
The requested information:
$ touch ../../src/openbabel/scripts/openbabel-python.i
$ VERBOSE=1 make_openbabel >& tmp.txt
$ cat tmp.txt
-bash: make_openbabel: command not found
$ grep -i python CMakeCache.txt > tmp2.txt
$ cat tmp2.txt
//Build Python bindings
PYTHON_BINDINGS:BOOL=ON
PYTHON_EXECUTABLE:FILEPATH=/usr/bin/python2.6
PYTHON_INCLUDE_DIR:PATH=/System/Library/Frameworks/Python.framework/Headers
PYTHON_LIBRARY:FILEPATH=/usr/lib/libpython2.6.dylib
//Details about finding PythonInterp
FIND_PACKAGE_MESSAGE_DETAILS_PythonInterp:INTERNAL=[/usr/bin/python2.6][v()]
//Details about finding PythonLibs
FIND_PACKAGE_MESSAGE_DETAILS_PythonLibs:INTERNAL=[/usr/lib/libpython2.6.dylib][/System/Library/Frameworks/Python.framework/Headers][v()]
//ADVANCED property for variable: PYTHON_EXECUTABLE
PYTHON_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_INCLUDE_DIR
PYTHON_INCLUDE_DIR-ADVANCED:INTERNAL=1
//Path to where Python.h is found (deprecated)
PYTHON_INCLUDE_PATH:INTERNAL=/System/Library/Frameworks/Python.framework/Headers
//ADVANCED property for variable: PYTHON_LIBRARY
PYTHON_LIBRARY-ADVANCED:INTERNAL=1
On Thu, Oct 13, 2011 at 7:34 AM, Noel O'Boyle <baoille...@gmail.com> wrote:
> On 12 October 2011 15:47, Chris Mayne <cgma...@gmail.com> wrote:
> > I cleared everything out and reran cmake with the following flags (i.e.
> > leaving the -DPYTHON_PATH out):
> >
> > $ cmake -DCMAKE_INSTALL_PREFIX=/usr/local/bin ../../src/openbabel
> > -DPYTHON_BINDINGS=ON -DRUN_SWIG=ON -DSWIG_EXECUTABLE=/usr/local/bin/swig
> > -DEIGEN2_INCLUDE_DIR=/usr/local/include/eigen2
> > -DEIGEN3_INCLUDE_DIR=/usr/local/include/eigen3
> >
> > the only warning was:
> >
> > CMake Warning:
> > Manually-specified variables were not used by the project:
> >
> > EIGEN2_INCLUDE_DIR
> >
> > I then issued "make" which yielded these warnings:
> >
> > ld: warning: directory
> > '/Users/cmayne/openbabel/src/openbabel/scripts/python/../../lib'
> following
> > -L not found
> > ld: warning: directory
> > '/Users/cmayne/openbabel/src/openbabel/scripts/python/../../lib64'
> following
> > -L not found
> > ld: warning: in ../lib/libopenbabel.dylib, file was built for unsupported
> > file format which is not the architecture being linked (i386)
> > ld: warning: directory
> > '/Users/cmayne/openbabel/src/openbabel/scripts/python/../../lib'
> following
> > -L not found
> > ld: warning: directory
> > '/Users/cmayne/openbabel/src/openbabel/scripts/python/../../lib64'
> following
> > -L not found
> > ld: warning: in ../lib/libopenbabel.dylib, file was built for unsupported
> > file format which is not the architecture being linked (ppc)
> > ld: warning: directory
> > '/Users/cmayne/openbabel/src/openbabel/scripts/python/../../lib'
> following
> > -L not found
> > ld: warning: directory
> > '/Users/cmayne/openbabel/src/openbabel/scripts/python/../../lib64'
> following
> > -L not found
> > [100%] Built target _openbabel
> >
> >
> > It would seem that this is where the python problems are coming up.
>
> Ok. Let's get to the bottom of this. Try "touch
> ../../src/openbabel/scripts/openbabel-python.i" and then "VERBOSE=1
> make _openbabel >& tmp.txt". This will give us the command lines that
> are causing the problem. Also, it would be good to know which Python
> are you linking against. Try "grep -i python CMakeCache.txt >
> tmp2.txt".
>
> - Noel
>
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
OpenBabel-discuss mailing list
OpenBabel-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openbabel-discuss
