Automated report: NetBSD-current/i386 build failure

2021-02-02 Thread NetBSD Test Fixture
This is an automatically generated notice of a NetBSD-current/i386 build failure. The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host, using sources from CVS date 2021.02.03.05.51.40. An extract from the build.sh output follows: nbmake[5]: stopped in

Re: Help with libcurses and lynx under NetBSD-9 and -current?

2021-02-02 Thread Brian Buhrow
hello Roy and Brett. As usual in these cases, there was a bit of noise in the beginning of this process while I figured out what was wrong and what I was doing wrong. Here is my current understanding of the situation: 1. By default, terminfo reads the TERMCAP environment variable and

Re: Help with libcurses and lynx under NetBSD-9 and -current?

2021-02-02 Thread Roy Marples
On 02/02/2021 09:44, Brett Lymn wrote: Why don't you post your $TERMCAP and infocmp output here? Umm I don't have a problem with using terminfo. I am more interested in working out why lynx is misbehaving in window. I suspect that is something I did wrong when I fixed another PR to do with

Re: Help with libcurses and lynx under NetBSD-9 and -current?

2021-02-02 Thread Brett Lymn
On Mon, Feb 01, 2021 at 02:28:08PM +, Roy Marples wrote: > On 01/02/2021 09:53, Brett Lymn wrote: > > The TERMCAP variable has some severe liitations, the worst being it can > > only be 256bytes in size which was more than adequate for a vt100 > > definition but a modern colour xterm