In article <449110636.834339.1405380729734.javamail.r...@sz0123a.westchester.pa.mail.comcast.net>, <thor0...@comcast.net> wrote: >At about 3:19PM today, I sent an email in reponse to Automated report: >NetBSD-current/i386 build failure, stating that I was unable to build >HEAD due to an issue that first appeared in libcurses around July 5th. >Over the past few days, the errors I've been receiving in building >"release" have varied, but are all caused by changes in libcurses that >are mentioned in the appended test failure on July 5th (After not >updating for two weeks, I updated my source tree on July 11th, and have >been unable to build- even clean build- since). > >I have been keeping my source up to date, but I have been unable to >successfully build the NetBSD userland for either evbarm Raspberry Pi or >a GENERIC_TINY 386. The error I have been receiving alternates between >two errors, both complaining about missing files and/or programs in the >libcurses subtree. I have appended David Holland's response test failure >which shows one version of the error, and my response showing an >alternate version of the error. > >Has anyone else had issues regarding building libcurses or can suggest >an alternative (or temporary patch) for the time being?
I see the problem, and I will commit a workaround shortly until this is fixed properly. christos