ClosestStorm / macvim

Automatically exported from code.google.com/p/macvim
0 stars 0 forks source link

MacVim searching for Python headers in the wrong location #458

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Try to compile MacVim with homebrew python
2. Alternatively, try to compile MacVim with System Python

What is the expected output? What do you see instead?
MacVim should compile properly. It does not, failing with:

clang -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_MACVIM -Wall 
-Wno-unknown-pragmas -pipe  -DMACOS_X_UNIX -no-cpp-precomp  -g -O2 
-U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1     
-I/System/Library/Frameworks/Tcl.framework/Headers  -D_REENTRANT=1  
-D_THREAD_SAFE=1  -D_DARWIN_C_SOURCE=1   -o objects/if_tcl.o if_tcl.c
if_python.c:48:11: fatal error: 'Python/Python.h' file not found
# include <Python/Python.h>
          ^
brew: superenv removed: -Wall -Wno-unknown-pragmas -g -O2
1 error generated.
make[1]: *** [objects/if_python.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make: *** [first] Error 2

This is Re: https://github.com/mxcl/homebrew/issues/20392

A workaround is to link the headers to a folder inside the headers folder:

$ ln -sf 
/usr/local/Cellar/python/2.7.5/Frameworks/Python.framework/Versions/2.7/include/
python2.7/*.h 
/usr/local/Cellar/python/2.7.5/Frameworks/Python.framework/Versions/2.7/include/
python2.7/Python/

This allows MacVim to compile and run properly, linked against the brewed 
Python.

I have not tested this workaround for System Python.

Original issue reported on code.google.com by ppvanze...@gmail.com on 29 Jun 2013 at 1:25

GoogleCodeExporter commented 9 years ago
This workaround solved the problem for me. Thanks

Original comment by iraquita...@gmail.com on 3 Aug 2013 at 5:26