![]() (This corrects a problem where can’t be located during compilation.) Then I had to create a custom symlink to get past a build problem: $ cd /System/Library/Frameworks/amework/Versions/2.7/include/python2.7 Around the line that reads: ENV.prepend 'LDFLAGS'. If you are reading this a few weeks or longer after Mavericks has been released to the public then its likely these problems will have been solved already within Homebrew.įirst I had to manually patch /usr/local/Library/Formula/macvim.rb. Fortunately I got it working and I can be productive once again.Įverything here applies to the Homebrew ( brew) installed version of MacVim using the OSX system installation of Python. ![]() ![]() Ultimately the best I could end up with was a successful build (this took some herculean effort to attain) that would crash rather anticlimactically: $ mvimįatal Python error: PyThreadState_Get: no current thread I tried using the precompiled Python 2.7.5 installer (which I had to manually uninstall, ick), building MacVim from source with crazy LDFLAGS and CFLAGS settings, and a few other things. I experienced a ton of difficulties getting MacVim compiled with a bunch of false leads and research. It felt like a clean install of MacVim was in order anyway. After upgrading to Mavericks I was having problems since my brew’d Python was replaced with the OSX system python. I also use a couple of plugins that require Python – YouCompleteMe and powerline. I require MacVim on OSX to work productively.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |