Automated report: NetBSD-current/i386 build failure

2017-09-30 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 2017.09.30.15.25.16. An extract from the build.sh output follows: Considering target file `macro.o'. Sti

Automated report: NetBSD-current/i386 build failure

2017-09-29 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 2017.09.29.12.57.05. An extract from the build.sh output follows: --- dependall-modules --- --- audio.kmod ---

Automated report: NetBSD-current/i386 build failure

2017-09-28 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 2017.09.28.18.08.04. An extract from the build.sh output follows: --- kern-INSTALL_XEN3_DOMU --- --- vfs_vnode.o

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

2017-09-27 Thread Ryota Ozaki
On Wed, Sep 27, 2017 at 6:47 PM, NetBSD Test Fixture wrote: > 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 2017.09.27.08.14.18. > > An extract from the build.s

Automated report: NetBSD-current/i386 build failure

2017-09-27 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 2017.09.27.08.14.18. An extract from the build.sh output follows: --- ieee8023ad_lacp_sm_tx.pico --- # compile

Automated report: NetBSD-current/i386 build failure

2017-09-16 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 2017.09.17.00.01.08. An extract from the build.sh output follows: from /tmp/bracket/build/2017.09.

Automated report: NetBSD-current/i386 build failure

2017-09-15 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 2017.09.15.16.50.46. An extract from the build.sh output follows: /tmp/bracket/build/2017.09.15.16.50.46-i386/src/s

Automated report: NetBSD-current/i386 build failure

2017-08-30 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 2017.08.30.10.51.06. An extract from the build.sh output follows: --- dependall-tests --- /tmp/bracket/build/201

Automated report: NetBSD-current/i386 build failure

2017-08-24 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 2017.08.24.13.06.23. An extract from the build.sh output follows: #create gpt/set.d --- dependall-libexec -

Automated report: NetBSD-current/i386 build failure

2017-08-12 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 2017.08.12.19.48.28. An extract from the build.sh output follows: postinstall fixes failed: =

Automated report: NetBSD-current/i386 build failure

2017-08-12 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 2017.08.12.09.03.28. An extract from the build.sh output follows: from ./x86/cpu.h:490,

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

2017-08-11 Thread Andreas Gustafsson
On August 9, NetBSD Test Fixture wrote: > This is an automatically generated notice of a NetBSD-current/i386 > build failure. [...] > --- dependall-compat_ibcs2 --- > > /tmp/bracket/build/2017.08.09.18.58.51-i386/src/sys/compat/ibcs2/ibcs2_exec.c:56:35: > fatal error: machine/ibcs2_machde

Automated report: NetBSD-current/i386 build failure

2017-08-09 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 2017.08.09.18.58.51. An extract from the build.sh output follows: --- dependall-ati_pcigart --- /tmp/bracket/bui

Automated report: NetBSD-current/i386 build failure

2017-08-05 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 2017.08.05.12.38.08. An extract from the build.sh output follows: --- kern-MONOLITHIC --- /tmp/bracket/build/201

Automated report: NetBSD-current/i386 build failure

2017-08-01 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 2017.08.01.14.43.54. An extract from the build.sh output follows: Target directory: /tmp/bracket/build/2017.08.01.14

Automated report: NetBSD-current/i386 build failure

2017-07-29 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 2017.07.29.13.05.15. An extract from the build.sh output follows: postinstall-fix-obsolete_stand ===> . --- post

Automated report: NetBSD-current/i386 build failure

2017-07-24 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 2017.07.24.19.56.07. An extract from the build.sh output follows: --- qdisc_fifoq.d --- #create altqstat/qd

Automated report: NetBSD-current/i386 build failure

2017-07-11 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 2017.07.11.21.19.42. An extract from the build.sh output follows: --- transited.pico --- # compile libkrb5/tr

Automated report: NetBSD-current/i386 build failure

2017-06-26 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 2017.06.26.20.36.01. An extract from the build.sh output follows: ^ /tmp/bracket/build/2017.06.26.20.36.01-i38

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

2017-06-22 Thread Kamil Rytarowski
On 22.06.2017 17:11, NetBSD Test Fixture wrote: > 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 2017.06.22.13.42.09. > > An extract from the build.sh output fo

Automated report: NetBSD-current/i386 build failure

2017-06-22 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 2017.06.22.13.42.09. An extract from the build.sh output follows: ^ --- dependall-external --- --- dependa

Automated report: NetBSD-current/i386 build failure

2017-06-20 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 2017.06.20.07.21.50. An extract from the build.sh output follows: /tmp/bracket/build/2017.06.20.07.21.50-i386/tools/

Automated report: NetBSD-current/i386 build failure

2017-06-19 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 2017.06.19.19.58.24. An extract from the build.sh output follows: --- releasekern-XEN3PAE_DOM0 --- --- releaseke

Automated report: NetBSD-current/i386 build failure

2017-06-15 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 2017.06.16.00.10.09. An extract from the build.sh output follows: mv pack.lo.o pack.lo --- crc.lo --- mv crc

Automated report: NetBSD-current/i386 build failure

2017-06-15 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 2017.06.15.07.05.32. An extract from the build.sh output follows: ^ /tmp/bracket/build/2017.06.15.07.0

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

2017-06-13 Thread Paul Goyette
Already fixed: http://mail-index.netbsd.org/source-changes/2017/06/13/msg085302.html On Tue, 13 Jun 2017, NetBSD Test Fixture wrote: 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 sour

Automated report: NetBSD-current/i386 build failure

2017-06-13 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 2017.06.13.06.39.09. An extract from the build.sh output follows: AWK=/tmp/bracket/build/2017.06.13.06.39.09-i386/to

Automated report: NetBSD-current/i386 build failure

2017-06-12 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 2017.06.12.15.02.32. An extract from the build.sh output follows: obsolete_stand fix: postinstall fixes passed:

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

2017-06-12 Thread Paul Goyette
This should already be fixed. On Mon, 12 Jun 2017, NetBSD Test Fixture wrote: 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 2017.06.12.07.12.49. An extract from th

Automated report: NetBSD-current/i386 build failure

2017-06-12 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 2017.06.12.07.12.49. An extract from the build.sh output follows: #create XEN3_DOM0/wsmux.d CC=/tmp/bracke

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

2017-06-11 Thread Paul Goyette
This should already have been fixed... On Mon, 12 Jun 2017, NetBSD Test Fixture wrote: 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 2017.06.11.22.22.36. An extrac

Automated report: NetBSD-current/i386 build failure

2017-06-11 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 2017.06.11.22.22.36. An extract from the build.sh output follows: Target directory: /tmp/bracket/build/2017.06.11.22

Automated report: NetBSD-current/i386 build failure

2017-06-10 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 2017.06.11.03.55.56. An extract from the build.sh output follows: --- dependall-raid --- --- rf_reconutil.d ---

Automated report: NetBSD-current/i386 build failure

2017-06-09 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 2017.06.10.05.31.34. An extract from the build.sh output follows: --- fstat.o --- # compile sa/fstat.o /t

Automated report: NetBSD-current/i386 build failure

2017-06-08 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 2017.06.08.16.02.27. An extract from the build.sh output follows: --- cleandir-crypto/external --- (cd /tmp/bra

Automated report: NetBSD-current/i386 build failure

2017-06-07 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 2017.06.07.05.30.49. An extract from the build.sh output follows: --- ftp_make --- --- complete.o --- --- al

Automated report: NetBSD-current/i386 build failure

2017-05-31 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 2017.05.31.11.09.22. An extract from the build.sh output follows: ^ /tmp/bracket/build/2017.05.31.11.0

Automated report: NetBSD-current/i386 build failure

2017-05-29 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 2017.05.30.02.21.11. An extract from the build.sh output follows: postinstall-fix-obsolete_stand ===> . --- post

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

2017-05-28 Thread Andreas Gustafsson
NetBSD Test Fixture wrote: > *** [t_can.o] Error code 1 Here's the actual compiler error message, which was missing in the auto-generated report: /tmp/bracket/build/2017.05.28.05.27.13-i386/src/tests/net/can/t_can.c:689:7: error: format '%ld' expects argument of type 'long int', but argume

Automated report: NetBSD-current/i386 build failure

2017-05-27 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 2017.05.27.21.06.26. An extract from the build.sh output follows: --- dependall-tests --- --- t_regex_att.o ---

Automated report: NetBSD-current/i386 build failure

2017-05-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 2017.05.26.02.30.24. An extract from the build.sh output follows: postinstall-fix-obsolete_stand ===> . --- post

Automated report: NetBSD-current/i386 build failure

2017-05-22 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 2017.05.23.03.23.58. An extract from the build.sh output follows: --- rscreate.d --- #create LEGACY/rscreat

Automated report: NetBSD-current/i386 build failure

2017-05-19 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 2017.05.19.14.42.00. An extract from the build.sh output follows: --- kern-XEN3_DOMU --- /tmp/bracket/build/2017

Automated report: NetBSD-current/i386 build failure

2017-05-18 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 2017.05.19.00.01.34. An extract from the build.sh output follows: --- postinstall-fix-obsolete_stand --- ===

Automated report: NetBSD-current/i386 build failure

2017-05-14 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 2017.05.14.10.08.49. An extract from the build.sh output follows: --- dependkernlib --- --- addvdi3.d --- #

Automated report: NetBSD-current/i386 build failure

2017-05-13 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 2017.05.13.13.17.11. An extract from the build.sh output follows: postinstall fixes failed: =

Automated report: NetBSD-current/i386 build failure

2017-05-11 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 2017.05.11.05.55.14. An extract from the build.sh output follows: rm -f .depend CC=/tmp/bracket/build/2017.05.1

Automated report: NetBSD-current/i386 build failure

2017-05-09 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 2017.05.10.02.46.33. An extract from the build.sh output follows: ^ /t

Automated report: NetBSD-current/i386 build failure

2017-05-08 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 2017.05.09.04.25.28. An extract from the build.sh output follows: REFLOG("SP_ADDREF", (p), __func__, __LINE__);

Automated report: NetBSD-current/i386 build failure

2017-05-07 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 2017.05.07.08.26.58. An extract from the build.sh output follows: /tmp/bracket/build/2017.05.07.08.26.58-i386/destd

Automated report: NetBSD-current/i386 build failure

2017-05-06 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 2017.05.06.19.52.25. An extract from the build.sh output follows: obsolete_stand fix: postinstall fixes passed:

Automated report: NetBSD-current/i386 build failure

2017-05-01 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 2017.05.01.21.36.33. An extract from the build.sh output follows: #create ifconfig/af_atalk.d --- dependall

Automated report: NetBSD-current/i386 build failure

2017-04-30 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 2017.04.30.20.57.23. An extract from the build.sh output follows: ASL_EXTERN ACPI_COMMENT_NODEASL_INIT_GLOB

Automated report: NetBSD-current/i386 build failure

2017-04-29 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 2017.04.29.01.18.35. An extract from the build.sh output follows: --- dependall-sys --- /tmp/bracket/build/2017.

Automated report: NetBSD-current/i386 build failure

2017-04-26 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 2017.04.26.13.17.33. An extract from the build.sh output follows:

Automated report: NetBSD-current/i386 build failure

2017-04-21 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 2017.04.21.23.49.17. An extract from the build.sh output follows: unzip.c:(.text.startup+0xb14): undefined reference

Automated report: NetBSD-current/i386 build failure

2017-04-21 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 2017.04.21.19.18.05. An extract from the build.sh output follows: /tmp/bracket/build/2017.04.21.19.18.05-i386/tools

Automated report: NetBSD-current/i386 build failure

2017-04-21 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 2017.04.21.09.01.52. An extract from the build.sh output follows: --- pci_subr.pico --- /tmp/bracket/build/2017

Automated report: NetBSD-current/i386 build failure

2017-04-20 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 2017.04.20.14.39.36. An extract from the build.sh output follows: --- archive_write_set_format_warc.po --- /tmp

Automated report: NetBSD-current/i386 build failure

2017-04-18 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 2017.04.18.07.44.20. An extract from the build.sh output follows: /tmp/bracket/build/2017.04.18.07.44.20-i386/tools

Automated report: NetBSD-current/i386 build failure

2017-04-17 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 2017.04.17.20.48.36. An extract from the build.sh output follows: postinstall fixes failed: =

Automated report: NetBSD-current/i386 build failure

2017-04-17 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 2017.04.17.07.19.28. An extract from the build.sh output follows: --- postinstall-fix-obsolete_stand --- ===

Automated report: NetBSD-current/i386 build failure

2017-04-11 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 2017.04.11.18.04.08. An extract from the build.sh output follows: --- graphics.o --- # compile atc/graphics.o

Automated report: NetBSD-current/i386 build failure

2017-04-10 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 2017.04.10.16.45.57. An extract from the build.sh output follows: obsolete_stand fix: postinstall fixes passed:

Automated report: NetBSD-current/i386 build failure

2017-04-08 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 2017.04.08.18.24.09. An extract from the build.sh output follows: --- uvm_object.d --- #create librump/uvm_

Automated report: NetBSD-current/i386 build failure

2017-04-07 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 2017.04.08.00.25.50. An extract from the build.sh output follows: --- dependall-gcc --- --- cp-demangle.o ---

Automated report: NetBSD-current/i386 build failure

2017-04-05 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 2017.04.06.01.54.40. An extract from the build.sh output follows: obsolete_stand fix: postinstall fixes passed:

Automated report: NetBSD-current/i386 build failure

2017-04-04 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 2017.04.04.11.46.12. An extract from the build.sh output follows: --- dependall-usr.bin --- --- hesinfo.d ---

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

2017-04-02 Thread Andreas Gustafsson
On March 31, the NetBSD Test Fixture wrote: > > /tmp/bracket/build/2017.03.31.21.07.02-i386/src/external/bsd/dhcpcd/dist/src/bpf.c: > In function 'bpf_arp': > > /tmp/bracket/build/2017.03.31.21.07.02-i386/src/external/bsd/dhcpcd/dist/src/bpf.c:425:1: > error: stack protector not protect

Automated report: NetBSD-current/i386 build failure

2017-03-31 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 2017.03.31.21.07.02. An extract from the build.sh output follows: /tmp/bracket/build/2017.03.31.21.07.02-i386/tools/

Automated report: NetBSD-current/i386 build failure

2017-03-31 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 2017.03.31.06.49.44. An extract from the build.sh output follows: postinstall-fix-obsolete_stand ===> . --- post

Automated report: NetBSD-current/i386 build failure

2017-03-22 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 2017.03.22.18.17.42. An extract from the build.sh output follows: /tmp/bracket/build/2017.03.22.18.17.42-i386/tools

Automated report: NetBSD-current/i386 build failure

2017-03-20 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 2017.03.20.22.57.04. An extract from the build.sh output follows: ^ /tmp/bracket/build/2017

Automated report: NetBSD-current/i386 build failure

2017-03-20 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 2017.03.20.14.46.28. An extract from the build.sh output follows: /tmp/bracket/build/2017.03.20.14.46.28-i386/tools

Automated report: NetBSD-current/i386 build failure

2017-03-20 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 2017.03.20.12.06.03. An extract from the build.sh output follows: } ^ /tmp/bracket/build/2017.03.20.12.0

Automated report: NetBSD-current/i386 build failure

2017-03-19 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 2017.03.20.00.30.03. An extract from the build.sh output follows: kern_assert(__KASSERTSTR msg, "diagnostic

Automated report: NetBSD-current/i386 build failure

2017-03-14 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 2017.03.14.09.04.16. An extract from the build.sh output follows: --- murmurhash.o --- # compile kern/murmurh

Automated report: NetBSD-current/i386 build failure

2017-03-11 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 2017.03.11.12.19.30. An extract from the build.sh output follows: /tmp/bracket/build/2017.03.11.12.19.30-i386/tools/

Automated report: NetBSD-current/i386 build failure

2017-03-08 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 2017.03.08.16.09.27. An extract from the build.sh output follows: postinstall-fix-obsolete_stand ===> . --- post

Automated report: NetBSD-current/i386 build failure

2017-03-06 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 2017.03.06.10.12.00. An extract from the build.sh output follows: postinstall-fix-obsolete_stand ===> . --- post

Automated report: NetBSD-current/i386 build failure

2017-02-28 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 2017.03.01.00.41.39. An extract from the build.sh output follows: postinstall-fix-obsolete_stand ===> . --- post

Automated report: NetBSD-current/i386 build failure

2017-02-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 2017.02.25.16.48.03. An extract from the build.sh output follows: dr7.bits.condition_dr3 = 0; /* 0b00 -- break on

Automated report: NetBSD-current/i386 build failure

2017-02-22 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 2017.02.22.09.50.13. An extract from the build.sh output follows: --- dependall-arch --- --- .gdbinit --- --

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

2017-02-21 Thread Kamil Rytarowski
On 22.02.2017 03:26, NetBSD Test Fixture wrote: > 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 2017.02.22.01.07.13. > > An extract from the build.sh output fo

Automated report: NetBSD-current/i386 build failure

2017-02-21 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 2017.02.22.01.07.13. An extract from the build.sh output follows: # install /tmp/bracket/build/2017.02.22.01.07.

Automated report: NetBSD-current/i386 build failure

2017-02-18 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 2017.02.18.23.27.32. An extract from the build.sh output follows: --- ieee8023ad_lacp_sm_ptx.o --- # compile

Automated report: NetBSD-current/i386 build failure

2017-02-17 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 2017.02.17.12.16.37. An extract from the build.sh output follows: --- kern-INSTALL_XEN3_DOMU --- --- xenbus_xs.o

Automated report: NetBSD-current/i386 build failure

2017-02-16 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 2017.02.16.19.11.13. An extract from the build.sh output follows: Live child 0x7f7ff7b2a480 (init.o) PID 25591

Automated report: NetBSD-current/i386 build failure

2017-02-10 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 2017.02.11.03.07.06. An extract from the build.sh output follows: --- cleandir-liveimage --- --- cleandir-emuima

Automated report: NetBSD-current/i386 build failure

2017-02-07 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 2017.02.07.22.37.18. An extract from the build.sh output follows: --- postinstall-fix-obsolete_stand --- ===

Automated report: NetBSD-current/i386 build failure

2017-02-06 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 2017.02.06.16.08.56. An extract from the build.sh output follows: postinstall-fix-obsolete_stand ===> . --- post

Automated report: NetBSD-current/i386 build failure

2017-02-04 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 2017.02.04.10.16.09. An extract from the build.sh output follows: codepageConvert(int UNUSED_P(cp), const char *UNU

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

2017-02-03 Thread Martin Husemann
On Fri, Feb 03, 2017 at 09:40:41AM +0100, Martin Husemann wrote: > I think I fixed it for all but i386. > > Linux/i386 is wiered and uses socketcall(18, ...) for this functionality > instead of a separate accept4 syscall. I ifdef'd out the syscall implementation for __i386__ - Christos, could you

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

2017-02-03 Thread Martin Husemann
On Fri, Feb 03, 2017 at 10:23:12AM +0200, Andreas Gustafsson wrote: > NetBSD Test Fixture wrote: > > *** [kern_time_50.pico] Error code 1 > > nbmake[7]: stopped in > > /tmp/bracket/build/2017.02.02.15.37.42-i386/src/lib/librump > > The build is still failing, but now in a different place:

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

2017-02-03 Thread Andreas Gustafsson
NetBSD Test Fixture wrote: > *** [kern_time_50.pico] Error code 1 > nbmake[7]: stopped in > /tmp/bracket/build/2017.02.02.15.37.42-i386/src/lib/librump The build is still failing, but now in a different place: --- dependall-compat_linux --- /tmp/bracket/build/2017.02.03.06.06.09-i38

Automated report: NetBSD-current/i386 build failure

2017-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 2017.02.02.15.37.42. An extract from the build.sh output follows: --- memset.pico --- --- memmove.po --- #

Automated report: NetBSD-current/i386 build failure

2017-02-01 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 2017.02.01.20.06.21. An extract from the build.sh output follows: /tmp/bracket/build/2017.02.01.20.06.21-i386/src/e

Automated report: NetBSD-current/i386 build failure

2017-01-31 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 2017.01.31.21.25.58. An extract from the build.sh output follows: chain = start_at->_internal.chain;

Automated report: NetBSD-current/i386 build failure

2017-01-28 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 2017.01.28.20.46.56. An extract from the build.sh output follows: --- includes-external --- --- includes-bsd ---

Automated report: NetBSD-current/i386 build failure

2017-01-28 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 2017.01.28.17.14.21. An extract from the build.sh output follows: --- dependall-libexec --- # compile ld.elf_

<    5   6   7   8   9   10   11   12   13   14   >