Re: Failure to build "current" emacs from pkgsrc on current

2018-10-25 Thread Riccardo Mottola
Hi Greg, Greg Troxel wrote: Yes, but it can hit an error and exit without finishing. So I would run it again and see if it reports that there's nothing to do. I did re-run it and it breaks out in the same place! I don't have much useful advice, other than to start using nm or objdump on t

Automated report: NetBSD-current/i386 build failure

2018-10-25 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 2018.10.26.01.33.33. An extract from the build.sh output follows: #create trek/capture.d CC=/tmp/bracket/b

daily CVS update output

2018-10-25 Thread NetBSD source update
Updating src tree: P src/distrib/sets/lists/comp/mi P src/lib/libcurses/Makefile P src/lib/libcurses/curses.3 P src/lib/libcurses/curses_addch.3 P src/lib/libcurses/curses_attributes.3 P src/lib/libcurses/curses_delch.3 P src/lib/libcurses/curses_inch.3 U src/lib/libcurses/curses_insch.3 cvs upda

Re: Automated report: NetBSD-current/i386 test failure

2018-10-25 Thread Christos Zoulas
In article <20181026003810.d7e3617f...@rebar.astron.com>, Christos Zoulas wrote: >On Oct 24, 2:14pm, mar...@netbsd.org (Martin Husemann) wrote: >-- Subject: Re: Automated report: NetBSD-current/i386 test failure > >| Ktraceing it shows the failing call is sendmsg() - which should be properly >| i

Re: Automated report: NetBSD-current/i386 test failure

2018-10-25 Thread Christos Zoulas
On Oct 24, 2:14pm, mar...@netbsd.org (Martin Husemann) wrote: -- Subject: Re: Automated report: NetBSD-current/i386 test failure | Ktraceing it shows the failing call is sendmsg() - which should be properly | intercepted by librumphijack, but talks to the host kernel and gets errno 32. The probl

Re: Failure to build "current" emacs from pkgsrc on current

2018-10-25 Thread Greg Troxel
Riccardo Mottola writes: > Greg Troxel wrote: >> Riccardo Mottola writes: >> >>> while doing a full update with today's pkgsrc con current, I get: >> by 'full update', what do you mean? > > I updated kernel, tools & distribtion to latest. > > Then I did update pkgsrc and run pkg_rolling-replac

Automated report: NetBSD-current/i386 build success

2018-10-25 Thread NetBSD Test Fixture
The NetBSD-current/i386 build is working again. The following commits were made between the last failed build and the successful build: 2018.10.25.13.20.01 uwe src/distrib/sets/lists/comp/mi,v 1.2235 Log files can be found at: http://releng.NetBSD.org/b5reports/i386/commits-2018.10.htm

Automated report: NetBSD-current/i386 build failure

2018-10-25 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 2018.10.25.10.41.00. An extract from the build.sh output follows: postinstall-fix-obsolete_stand ===> . --- post