Greg, thanks for your hint about the numpy version, it solved my problems! I'll summarize what I did in case anyone needs it later:
> Make sure that version looks right and that it's the one you're > actually using. You can check which one is being used like this: > python -c 'import numpy;print numpy.__file__' So cmake was actually using the default numpy but python wasn't. I added the path to numpy/__init__.pyc to my PYTHONPATH... however, cmake ignored this and was still using the default path (at least according to > grep -i numpy $RDBASE/build/CMakeCache.txt). To force it, I added the following to my cmake command: -D PYTHON_NUMPY_INCLUDE_PATH=/my/path/to/numpy/__init__.pyc This worked, but the python bits in ctest failed or gave segfaults. From some google searches, I got the impression that I need to supply the location of numpy/arrayobject.h (rather than numpy/__init__.pyc) , which can be found from a python interactive session like this: >>> import numpy >>> print numpy.get_include() Thus, I added to my cmake command: -D PYTHON_NUMPY_INCLUDE_PATH=/my/path/to/arrayobject.h That did it for me, finally! Now it's playtime :))) > out of curiousity: which version of redhat are you using? Red Hat Enterprise Linux Server release 6.1 (Santiago) -- Felix twitter: @MoSander ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Rdkit-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rdkit-discuss
