Hisashi Fujinaka wrote:

> On Mon, 25 Jul 2016, Tony Mechelynck wrote:
> 
> > On Mon, Jul 25, 2016 at 9:27 PM, Hisashi T Fujinaka <ht...@twofifty.com> 
> > wrote:
> >> On Mon, 25 Jul 2016, Manuel Ortega wrote:
> >>
> >>> On Mon, Jul 25, 2016 at 2:00 PM, Manuel Ortega <mannyvim...@gmail.com>
> >>> wrote:
> >>>
> >>>
> >>>       On Mon, Jul 25, 2016 at 1:41 PM, Hisashi T Fujinaka
> >>> <ht...@twofifty.com> 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.
> 
> Sorry, but lately most of my comments have been about bad tests. I
> assumed most people read all the email here but that was a bad
> assumption.
> 
> Bram broke my builds a while ago (like in the 203x range) in netbseans
> and the tests yield:
> 
> >From test_netbeans.vim:
> Found errors in Test_nb_basic():
> function 
> RunTheTest[9]..Test_nb_basic[2]..<SNR>4_run_server[1]..RunServer[21]..Nb_basic
>  line 11: Expected 2 but got 130
> function 
> RunTheTest[9]..Test_nb_basic[2]..<SNR>4_run_server[1]..RunServer[21]..Nb_basic
>  line 12: Expected 20 but got 2
> function 
> RunTheTest[9]..Test_nb_basic[2]..<SNR>4_run_server[1]..RunServer[21]..Nb_basic
>  line 23: Expected '0:disconnect=1' but got '0:disconnect=0'
> 
> Test results:
> 
> 
> >From test_netbeans.vim:
> Found errors in Test_nb_basic():
> function 
> RunTheTest[9]..Test_nb_basic[2]..<SNR>4_run_server[1]..RunServer[21]..Nb_basic
>  line 11: Expected 2 but got 130
> function 
> RunTheTest[9]..Test_nb_basic[2]..<SNR>4_run_server[1]..RunServer[21]..Nb_basic
>  line 12: Expected 20 but got 2
> function 
> RunTheTest[9]..Test_nb_basic[2]..<SNR>4_run_server[1]..RunServer[21]..Nb_basic
>  line 23: Expected '0:disconnect=1' but got '0:disconnect=0'
> TEST FAILURE
> 
> I asked Bram about this (and about whether netbeans was even supposed to
> be used in OSX) and all he said was "works for me". Does anyone else
> even have Java installed?

Dominique discovered that it also breaks when running under Valgrind.
I suspect a race condition.

-- 
A hamburger walks into a bar, and the bartender says: "I'm sorry,
but we don't serve food here."

 /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\  an exciting new programming language -- http://www.Zimbu.org        ///
 \\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Raspunde prin e-mail lui