Re: pike build msql error with 8.0 git

2018-05-23 Thread Lance Dillon
I'm finding that build works with: make CONFIGUREARGS='--with-cflags=-O'... also -O2, but -O3 fails, so I'm going to start adding options between O2 and O3 to see which one causes it to fail.. On Saturday, May 12, 2018, 11:00:02 PM EDT, Lance Dillon wrote: And through this all, it is

Re: interesting terminfo error

2018-05-23 Thread Lance Dillon
Ah, good, I'll biuld with that one and see. Thanks. On Wednesday, May 23, 2018, 4:09:09 AM EDT, Henrik Grubbström (Lysator) @ Pike (-) developers forum <10...@lyskom.lysator.liu.se> wrote: Hi Lance. >I encountered this error on a system that had it's term type set to >xterm-256color:

Re: Pike 8.0.622 beta/release candidate

2018-05-23 Thread Stephen R. van den Berg
Peter Bortas wrote: >Pike 8.0.622 beta/release candidate: As it turns out, the deadlock hunt was halfway done at 8.0.622. Since then, I committed a few more fixes. Stdio.Buffer seems clean now, but pgsql still had one race condition left, and I introduced a stupid regression error for queries ret

interesting terminfo error

2018-05-23 Thread Henrik Grubbstr�m (Lysator) @ Pike (-) developers forum
Hi Lance. >I encountered this error on a system that had it's term type set to >xterm-256color: >$ TERM=xterm-256color pike >Terminfo: unparsable terminfo file "/usr/share/terminfo/x/xterm-256color" >/usr/local/pike/8.0.498/lib/modules/Stdio.pmod/Terminfo.pmod:406: [...] > >$ file /usr/share/term