> I debugged an issue with the same symptoms a while ago. It happened > when I ran `make` (which builds vim) with a different compiler than > xcodebuild (which builds MacVim). Maybe 4.4 uses clang by default for > the MacVim build -- in that case, run `CC=clang ./configure; make -j6` > to build the corresponding vim binary. Make sure both vim and MacVim > are built with the same compiler.
Yes, "CC=clang ./configure; make -j6" works. But *jeez* it is annoying that special steps have to be taken. Plus, during the compliation of the Vim binary, all sorts of warnings are thrown out that weren't there before. And it's annoying because I usually want to just run the ./configuring part first. In which case, I can do "export CC=clang" and then the configuring on a separate line, but then I have to remember to get rid of $CC after building MacVim lest I accidentally botch building something else. And now my steps for building have to be different between 10.7 and up, and 10.6 and below. Arrgh! Apple! -gmn -- You received this message from the "vim_mac" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
