Cmake doesn't recognize homebrew installed python.

[NiekSchultheiss]

I had to apply some hacks to get CRPropa running on my system with a Homebrew installed Python.

It showed the correct paths to the /usr/local version of Python during cmake ..
However, when doing ccmake .. it used the wrong Python Headers:

PYTHON_EXECUTABLE   /usr/local/bin/python
PYTHON_H_FOUND      /System/Library/Frameworks/Python.framework/Headers

I had to manually set the Python headers location to the homebrew version:

/usr/local/Cellar/python/2.7.5/Frameworks/Python.framework/Headers/Python.h

Then I proceeded with make && make test, which passed 100%, then make install.
Which also went fine, but importing crpropa resulted in Python crashing.
I found wrong links to python:

otool -L /usr/local/lib/python2.7/site-packages/_crpropa.so

And had to change it to the correct one:

install_name_tool -change /System/Library/Frameworks/Python.framework/Versions/2.7/Python /usr/local/Cellar/python/2.7.5/Frameworks/Python.framework/Versions/2.7/Python /usr/local/lib/python2.7/site-packages/_crpropa.so

After which running the example worked.

[geromueller]

Hi,

could you please run

/usr/local/bin/python -c "import sys; from distutils import sysconfig;
sys.stdout.write(sysconfig.get_python_inc())"

and report the output? Maybe your homebrew python installation is faulty.

Thanks
Gero

Am Dienstag, 20. Mai 2014, 02:34:18 schrieb NiekSchultheiss:

I had to apply some hacks to get CRPropa running on my system with a
Homebrew installed Python.

It showed the correct paths to the /usr/local version of Python during
cmake .. However, when doing ccmake .. it used the wrong Python
Headers:

PYTHON_EXECUTABLE   /usr/local/bin/python
PYTHON_H_FOUND      /System/Library/Frameworks/Python.framework/Headers

I had to manually set the Python headers location to the homebrew version:

/usr/local/Cellar/python/2.7.5/Frameworks/Python.framework/Headers/Python.h

Then I proceeded with make && make test, which passed 100%, then make install. Which also went fine, but importing crpropa resulted in Python
crashing. I found wrong links to python:

otool -L /usr/local/lib/python2.7/site-packages/_crpropa.so

And had to change it to the correct one:

install_name_tool -change

/System/Library/Frameworks/Python.framework/Versions/2.7/Python
/usr/local/Cellar/python/2.7.5/Frameworks/Python.framework/Versions/2.7/Pyt
hon /usr/local/lib/python2.7/site-packages/_crpropa.so

After which running the example worked.

---

Reply to this email directly or view it on GitHub:
#6

Dipl.-Phys. Gero Müller
III. Physikalisches Institut A
RWTH Aachen University
+49 (0)241 80 23567

[NiekSchultheiss]

Running:

>>> import sys
>>> from distutils import sysconfig
>>> sysconfig.get_python_inc()
'/usr/local/Cellar/python/2.7.6_1/Frameworks/Python.framework/Versions/2.7/include/python2.7'

Thanks,
Niek

[rafaelab]

Hello!

There was a recent change in python/Python.cmake that might fix that. Can you try setting these options when running cmake:
-DPYTHON_EXECUTABLE=/path/to/homebrew/python/python
-DPYTHON_LIBRARIES=/path/to/homebrew/python/libpython.so (or .dylib)
By doing this you will be linking the libraries against your homebrew installed python instead of the standard Apple python framework.

Please let me know the outcome of this.

Rafael

[DavidWalz]

assume solved