Closed GoogleCodeExporter closed 9 years ago
This has gotten even worse by now. It looks like the fix is not working
anymore. Look my confire line is this:
CC=clang ./configure --prefix=/opt/local --with-features=huge
--enable-luainterp --with-lua-prefix=/usr/local --enable-rubyinterp
--enable-pythoninterp
--with-python-config-dir=/usr/local/Cellar/python/2.7.9/Frameworks/Python.framew
ork/Versions/2.7 --enable-perlinterp --enable-cscope
--with-compiledby=francisco@oblita.com
I'm even trying to force the python-config-dir. Dude the system python IS NOT
the python available at the command line, even more, I even try to enforce that
by using --with-python-config-dir.
vim --version just gives this:
Linking: clang [...]
-L/usr/local/Cellar/python/2.7.9/Frameworks/Python.framework/Versions/2.7
-lpython2.7 [...]
Still, otool -L gives:
$otool -L `which vim`
/opt/local/bin/vim:
[...]
/System/Library/Frameworks/Python.framework/Versions/2.7/Python (compatibility version 2.7.0, current version 2.7.5)
[...]
vim building on OS X seems just broken.
Original comment by obl...@gmail.com
on 21 Mar 2015 at 5:43
I've removed --with-python-config-dir from the configure line, it's now working
again (with the build patches I mention included).
Original comment by obl...@gmail.com
on 22 Mar 2015 at 12:24
This issue can be close. The code base has been fixed.
Original comment by obl...@gmail.com
on 15 Apr 2015 at 4:58
Original comment by brammool...@gmail.com
on 15 Apr 2015 at 11:52
Original issue reported on code.google.com by
obl...@gmail.com
on 14 Jan 2015 at 2:32