On Mon, Jul 25, 2016 at 9:27 PM, Hisashi T Fujinaka <[email protected]> wrote: > On Mon, 25 Jul 2016, Manuel Ortega wrote: > >> On Mon, Jul 25, 2016 at 2:00 PM, Manuel Ortega <[email protected]> >> wrote: >> >> >> On Mon, Jul 25, 2016 at 1:41 PM, Hisashi T Fujinaka >> <[email protected]> wrote: >> >> Well, --huge is breaking on OSX for me again. I'm seeing if I >> can figure >> out where it broke. I wish I knew how to use bisect... >> >> >> What are your ./configure flags? I am building with huge features on OSX >> with no problems. >> >> >> By the way, --huge is the default now, so you shouldn't need to pass it at >> the command line. >> >> Bram: "./configure --help" still claims that the default level is >> "normal". > > > I'm doing: > > make clean && ./configure --with-features=huge && make test
I'm not using "make test". I set my configure setting by means of environment variables (so they will not be forgotten if make decides to run configure) then I run just "make" (or "make reconfig" if I have changed the settings or if some important libray package has been upgraded) followed by "make install" for my Huge build or by "make installruntime" for my Tiny build, which has --with-vim-name=vi to set it apart from the Huge build. Then if completion and link are OK I use mostly the Huge (gui-enabled) version as either gvim or vim. I haven't had any problems so far with 7.4.2012 since it was published. Is your problem with "compiling" Vim (then which messages do you get?), with "using" it yourself (and what are the symptoms?) or with running "make test"? If the latter, there is the possibility that the failing test (which one and how?) is the problem. Best regards, Tony. -- -- You received this message from the "vim_dev" 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 --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
