Automated report: NetBSD-current/i386 build failure

2021-09-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 2021.09.25.21.26.04. An extract from the build.sh output follows: ./libdata/firmware/nouveau/nvidia/LICENCE.nvidia

Automated report: NetBSD-current/i386 build failure

2021-09-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 2021.09.24.13.11.39. An extract from the build.sh output follows: Files in flist but missing from DESTDIR. File

Automated report: NetBSD-current/i386 build failure

2021-09-23 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.09.24.04.11.02. An extract from the build.sh output follows: nbmake[1]: stopped in

Automated report: NetBSD-current/i386 build failure

2021-09-23 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.09.23.06.58.47. An extract from the build.sh output follows: In file included from

Automated report: NetBSD-current/i386 build failure

2021-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 2021.09.16.23.32.50. An extract from the build.sh output follows: cd

Automated report: NetBSD-current/i386 build failure

2021-09-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 2021.09.05.10.18.31. An extract from the build.sh output follows: --- i915_gem_debug.o ---

Automated report: NetBSD-current/i386 build failure

2021-09-03 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.09.03.12.20.38. An extract from the build.sh output follows: 150 | ((boothowto & (AB_QUIET|AB_SILENT)) !=

Automated report: NetBSD-current/i386 build failure

2021-09-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.09.02.11.22.30. An extract from the build.sh output follows: | char ** In file included from

Automated report: NetBSD-current/i386 build failure

2021-08-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 2021.08.29.10.18.17. An extract from the build.sh output follows: nbmake[4]: stopped in

Automated report: NetBSD-current/i386 build failure

2021-08-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 2021.08.19.21.21.04. An extract from the build.sh output follows: | ^~ In file

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

2021-08-18 Thread Andreas Gustafsson
Yesterday, the NetBSD Test Fixture wrote: > nbmake[3]: stopped in /tmp/build/2021.08.17.17.31.59-i386/src > nbmake[2]: stopped in /tmp/build/2021.08.17.17.31.59-i386/src > nbmake[1]: stopped in /tmp/build/2021.08.17.17.31.59-i386/src > nbmake: stopped in

Automated report: NetBSD-current/i386 build failure

2021-08-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 2021.08.17.17.31.59. An extract from the build.sh output follows: nbmake[5]: stopped in

Automated report: NetBSD-current/i386 build failure

2021-08-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 2021.08.15.10.33.58. An extract from the build.sh output follows: if [ x"" != x ]; then cc -c -DHAVE_CONFIG_H -O

Automated report: NetBSD-current/i386 build failure

2021-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 2021.08.12.11.57.07. An extract from the build.sh output follows: === checkflist

Automated report: NetBSD-current/i386 build failure

2021-08-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 2021.08.09.00.32.51. An extract from the build.sh output follows: --- OsdMisc.d --- #create

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

2021-08-08 Thread Dave B
On Sun, Jul 25, 2021 at 11:51:57PM +, Thomas Mueller wrote: ... > Or should I try with hg? I have devel/mercurial built and installed. > > Now to find a tutorial for Mercurial for git users: There was one, but I can > no longer find it. ... There's a related resource which isn't a tutorial

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

2021-08-06 Thread David Holland
On Thu, Jul 22, 2021 at 10:32:37AM +0200, Reinoud Zandijk wrote: > > > it looks like CVS randomly didn't commit some of my changes, > > > investigating... > > > > Yeah, not sure what happened; something caused it to, apparently, > > think a few of the files in the second changeset still

Automated report: NetBSD-current/i386 build failure

2021-08-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.08.02.20.31.15. An extract from the build.sh output follows: | ^~

Automated report: NetBSD-current/i386 build failure

2021-07-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 2021.07.30.19.55.22. An extract from the build.sh output follows: checkflist ===> distrib/sets ---

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

2021-07-25 Thread Thomas Mueller
> On Mon, Jul 19, 2021 at 01:28:06AM +, David Holland wrote: > > that is... less than helpful :-( > > it looks like CVS randomly didn't commit some of my changes, > > investigating... > Yeah, not sure what happened; something caused it to, apparently, > think a few of the files in the

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

2021-07-24 Thread Andreas Gustafsson
On Monday, David Holland wrote: > Right... I wonder what happened to bracket's error-matching script; it > usually does better than that. I have now deployed bracket 2.15 on babylon5.netbsd.org, and the latest build failure report looks much better:

Automated report: NetBSD-current/i386 build failure

2021-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 2021.07.24.11.39.19. An extract from the build.sh output follows: --- kern-LEGACY --- --- if_upgt.d --- mv

Automated report: NetBSD-current/i386 build failure

2021-07-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 2021.07.22.17.39.53. An extract from the build.sh output follows: --- dependall-bootxx_ustarfs --- nbmake[9]:

make(1) enhancements (was Re: Automated report: NetBSD-current/i386 build failure)

2021-07-22 Thread Reinoud Zandijk
On Mon, Jul 19, 2021 at 08:13:19AM +0300, Andreas Gustafsson wrote: > David Holland wrote: > > On Mon, Jul 19, 2021 at 10:32:20AM +0900, Rin Okuyama wrote: > > > Logs below are usually more helpful. > > > > Right... I wonder what happened to bracket's error-matching script; it > > usually does

Automated report: NetBSD-current/i386 build failure

2021-07-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 2021.07.21.06.45.10. An extract from the build.sh output follows: ${MAKEDIRTARGET} .

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

2021-07-18 Thread Andreas Gustafsson
David Holland wrote: > On Mon, Jul 19, 2021 at 10:32:20AM +0900, Rin Okuyama wrote: > > Logs below are usually more helpful. > > Right... I wonder what happened to bracket's error-matching script; it > usually does better than that. There are multiple causes, but a major one is that since

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

2021-07-18 Thread Rin Okuyama
On 2021/07/19 10:28, David Holland wrote: that is... less than helpful :-( it looks like CVS randomly didn't commit some of my changes, investigating... Logs below are usually more helpful. On 2021/07/19 9:42, NetBSD Test Fixture wrote: Logs can be found at:

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

2021-07-18 Thread David Holland
On Mon, Jul 19, 2021 at 12:42:49AM +, 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 2021.07.18.23.57.34. > > An

Automated report: NetBSD-current/i386 build failure

2021-07-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 2021.07.18.23.57.34. An extract from the build.sh output follows: ${MAKEDIRTARGET} .

Automated report: NetBSD-current/i386 build failure

2021-07-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 2021.07.17.18.07.22. An extract from the build.sh output follows: --- dependall-gpl3 --- nbmake[6]: stopped in

Automated report: NetBSD-current/i386 build failure

2021-07-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 2021.07.10.07.50.33. An extract from the build.sh output follows: --- dependall-external --- nbmake[6]: stopped

Automated report: NetBSD-current/i386 build failure

2021-07-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 2021.07.09.15.26.59. An extract from the build.sh output follows: nbmake[4]: stopped in

Automated report: NetBSD-current/i386 build failure

2021-07-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 2021.07.08.09.16.24. An extract from the build.sh output follows: nbmake[6]: stopped in

Automated report: NetBSD-current/i386 build failure

2021-07-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 2021.07.06.11.52.56. An extract from the build.sh output follows:

Automated report: NetBSD-current/i386 build failure

2021-06-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 2021.06.27.09.22.31. An extract from the build.sh output follows: === checkflist

Automated report: NetBSD-current/i386 build failure

2021-06-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 2021.06.17.00.38.08. An extract from the build.sh output follows: ${MAKEDIRTARGET} .

Automated report: NetBSD-current/i386 build failure

2021-06-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 2021.06.06.08.45.18. An extract from the build.sh output follows: nbmake[6]: stopped in

Automated report: NetBSD-current/i386 build failure

2021-06-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 2021.06.05.06.23.48. An extract from the build.sh output follows: === 1 extra files in DESTDIR =

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

2021-05-27 Thread Christos Zoulas
In article <24751.41935.824926.178...@guava.gson.org>, Andreas Gustafsson wrote: >The i386 build is still failing, but now with a different error: > > --- in6_pcb.o --- > /tmp/build/2021.05.27.08.58.29-i386/src/sys/netinet6/in6_pcb.c: In >function 'in6_pcblookup_port': > cc1: error: function

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

2021-05-27 Thread Christos Zoulas
In article , Christos Zoulas wrote: >In article <24751.41935.824926.178...@guava.gson.org>, >Andreas Gustafsson wrote: >>The i386 build is still failing, but now with a different error: >> >> --- in6_pcb.o --- >> /tmp/build/2021.05.27.08.58.29-i386/src/sys/netinet6/in6_pcb.c: In >>function

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

2021-05-27 Thread Christos Zoulas
In article <24751.41935.824926.178...@guava.gson.org>, Andreas Gustafsson wrote: >The i386 build is still failing, but now with a different error: > > --- in6_pcb.o --- > /tmp/build/2021.05.27.08.58.29-i386/src/sys/netinet6/in6_pcb.c: In >function 'in6_pcblookup_port': > cc1: error: function

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

2021-05-27 Thread Andreas Gustafsson
The i386 build is still failing, but now with a different error: --- in6_pcb.o --- /tmp/build/2021.05.27.08.58.29-i386/src/sys/netinet6/in6_pcb.c: In function 'in6_pcblookup_port': cc1: error: function may return address of local variable [-Werror=return-local-addr]

Automated report: NetBSD-current/i386 build failure

2021-05-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 2021.05.26.20.22.28. An extract from the build.sh output follows: ${MAKEDIRTARGET} .

Automated report: NetBSD-current/i386 build failure

2021-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 2021.05.19.06.13.08. An extract from the build.sh output follows: ${MAKEDIRTARGET} .

Automated report: NetBSD-current/i386 build failure

2021-05-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 2021.05.15.19.19.55. An extract from the build.sh output follows: nbmake[7]: stopped in

Automated report: NetBSD-current/i386 build failure

2021-05-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 2021.05.12.11.08.31. An extract from the build.sh output follows: --- dependall-external --- ---

Automated report: NetBSD-current/i386 build failure

2021-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 2021.04.30.13.55.18. An extract from the build.sh output follows: nbmake[3]: stopped in

Automated report: NetBSD-current/i386 build failure

2021-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 2021.04.29.16.46.34. An extract from the build.sh output follows: ${MAKEDIRTARGET} .

Automated report: NetBSD-current/i386 build failure

2021-04-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 2021.04.28.00.49.22. An extract from the build.sh output follows: Files in flist but missing from DESTDIR. File

Automated report: NetBSD-current/i386 build failure

2021-04-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 2021.04.25.15.18.23. An extract from the build.sh output follows: nbmake[7]: stopped in

Automated report: NetBSD-current/i386 build failure

2021-04-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 2021.04.24.23.40.16. An extract from the build.sh output follows: nbmake[4]: stopped in

Automated report: NetBSD-current/i386 build failure

2021-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 2021.04.20.21.42.32. An extract from the build.sh output follows: # install

Automated report: NetBSD-current/i386 build failure

2021-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 2021.04.18.20.15.17. An extract from the build.sh output follows: === checkflist

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

2021-04-18 Thread Christos Zoulas
Fixed... christos > On Apr 18, 2021, at 9:39 AM, Andreas Gustafsson wrote: > > The i386 build is still failing, with errors like these: > > --- dependall-tmux --- > > /tmp/build/2021.04.18.12.05.29-i386/src/external/bsd/tmux/dist/cmd-display-menu.c: > In function

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

2021-04-18 Thread Andreas Gustafsson
The i386 build is still failing, with errors like these: --- dependall-tmux --- /tmp/build/2021.04.18.12.05.29-i386/src/external/bsd/tmux/dist/cmd-display-menu.c: In function 'cmd_display_menu_get_position':

Automated report: NetBSD-current/i386 build failure

2021-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 2021.04.17.20.12.55. An extract from the build.sh output follows: --- dependall-gdb --- ---

Automated report: NetBSD-current/i386 build failure

2021-04-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 2021.04.16.22.41.12. An extract from the build.sh output follows: nbmake[7]: stopped in

Automated report: NetBSD-current/i386 build failure

2021-04-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 2021.04.16.15.10.18. An extract from the build.sh output follows: --- dependall-share --- nbmake[4]: stopped in

Automated report: NetBSD-current/i386 build failure

2021-04-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 2021.04.13.22.46.13. An extract from the build.sh output follows: nbmake[5]: stopped in

Automated report: NetBSD-current/i386 build failure

2021-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 2021.04.10.18.36.27. An extract from the build.sh output follows: --- print.lo --- *** [print.lo] Error code 1

Automated report: NetBSD-current/i386 build failure

2021-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 2021.04.08.08.10.30. An extract from the build.sh output follows: --- checkflist --- cd

Automated report: NetBSD-current/i386 build failure

2021-04-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 2021.04.07.02.43.15. An extract from the build.sh output follows: --- event.po ---

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

2021-04-06 Thread jkoshy
> 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.04.06.20.13.43. ... > *** Failed target: dependall-../external/bsd/elftoolchain ... > The following

Automated report: NetBSD-current/i386 build failure

2021-04-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 2021.04.06.20.13.43. An extract from the build.sh output follows: ln -sf libelf.so.2.0 libelf.so.tmp mv -f

Automated report: NetBSD-current/i386 build failure

2021-03-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 2021.03.31.04.38.30. An extract from the build.sh output follows: nbmake[4]: stopped in

Automated report: NetBSD-current/i386 build failure

2021-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 2021.03.08.18.03.25. An extract from the build.sh output follows:

Automated report: NetBSD-current/i386 build failure

2021-03-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 2021.03.05.17.53.51. An extract from the build.sh output follows: === 2 extra files in DESTDIR =

Automated report: NetBSD-current/i386 build failure

2021-03-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 2021.03.01.18.08.36. An extract from the build.sh output follows: --- check_DESTDIR --- --- checkflist ---

Automated report: NetBSD-current/i386 build failure

2021-02-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 2021.02.27.15.36.39. An extract from the build.sh output follows: nbmake[6]: stopped in

Automated report: NetBSD-current/i386 build failure

2021-02-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 2021.02.26.10.06.42. An extract from the build.sh output follows: --- checkflist --- cd

Automated report: NetBSD-current/i386 build failure

2021-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 2021.02.26.03.08.25. An extract from the build.sh output follows:

Automated report: NetBSD-current/i386 build failure

2021-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 2021.02.25.21.59.27. An extract from the build.sh output follows: nbmake[6]: stopped in

Automated report: NetBSD-current/i386 build failure

2021-02-23 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.23.22.14.59. An extract from the build.sh output follows: --- dependall-gpl2 --- nbmake[7]: stopped in

Automated report: NetBSD-current/i386 build failure

2021-02-23 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.23.15.00.01. An extract from the build.sh output follows: --- dependall-ibm-public --- nbmake[6]:

Automated report: NetBSD-current/i386 build failure

2021-02-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 2021.02.21.07.23.41. An extract from the build.sh output follows: *** Failed target: dependall-lint1 ***

Automated report: NetBSD-current/i386 build failure

2021-02-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 2021.02.20.22.59.37. An extract from the build.sh output follows: nbmake[4]: stopped in

Automated report: NetBSD-current/i386 build failure

2021-02-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 2021.02.19.17.09.35. An extract from the build.sh output follows: nbmake[6]: stopped in

Automated report: NetBSD-current/i386 build failure

2021-02-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 2021.02.19.13.20.43. An extract from the build.sh output follows: mv -f decl.lo.o decl.lo --- tree.lo ---

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

2021-02-15 Thread Robert Elz
Date:Sun, 14 Feb 2021 21:40:21 + (UTC) From:NetBSD Test Fixture Message-ID: <161333882137.19912.5576154194224308...@babylon5.netbsd.org> | This is an automatically generated notice of a NetBSD-current/i386 | build failure. | | The failure occurred on

Automated report: NetBSD-current/i386 build failure

2021-02-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 2021.02.14.20.58.35. An extract from the build.sh output follows: *** Failed target: dependall-../sys/rump/net/lib

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

2021-02-03 Thread Ryo ONODERA
Hi, Roy Marples writes: > On 03/02/2021 17:55, Ryo ONODERA wrote: >> Exactly. It happens in dtrace userland build. > > Fixed. Sorry about that. > > Maybe we should not define CTASSERT ourselves and just use __CTASSERT to > avoid > this in the future? Thank you. I have no idea what is the

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

2021-02-03 Thread Roy Marples
On 03/02/2021 17:55, Ryo ONODERA wrote: Exactly. It happens in dtrace userland build. Fixed. Sorry about that. Maybe we should not define CTASSERT ourselves and just use __CTASSERT to avoid this in the future? Roy

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

2021-02-03 Thread Ryo ONODERA
Hi, Martin Husemann writes: > On Wed, Feb 03, 2021 at 05:31:11PM +, Roy Marples wrote: >> I cannot replicate this? >> I'm just building a stock kernel - what extra options do I need? > > It happens in the userland build. Exactly. It happens in dtrace userland build. > Martin -- Ryo

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

2021-02-03 Thread Martin Husemann
On Wed, Feb 03, 2021 at 05:31:11PM +, Roy Marples wrote: > I cannot replicate this? > I'm just building a stock kernel - what extra options do I need? It happens in the userland build. Martin

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

2021-02-03 Thread Roy Marples
On 03/02/2021 14:42, Ryo ONODERA wrote: Hi, It seems that CTASSERT in netinet/in.h conflicts with CTASSERT in external/cddl/osnet/dist/uts/common/sys/debug.h. Ryo ONODERA writes: Hi, However I have gotten another failure: --- dt_print.pico --- In file included from

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

2021-02-03 Thread Ryo ONODERA
Hi, It seems that CTASSERT in netinet/in.h conflicts with CTASSERT in external/cddl/osnet/dist/uts/common/sys/debug.h. Ryo ONODERA writes: > Hi, > > However I have gotten another failure: > > --- dt_print.pico --- > In file included from /usr/src/external/cddl/osnet/sys/sys/debug.h:51, >

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

2021-02-03 Thread Ryo ONODERA
Hi, However I have gotten another failure: --- dt_print.pico --- In file included from /usr/src/external/cddl/osnet/sys/sys/debug.h:51, from /usr/src/external/cddl/osnet/sys/sys/uio.h:64, from /usr/world/9.99/amd64/dest/usr/include/sys/socket.h:99,

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

2021-02-03 Thread Ryo ONODERA
Hi, NetBSD Test Fixture writes: > 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.12.11.34. > > An extract from the build.sh output follows: > >

Automated report: NetBSD-current/i386 build failure

2021-02-03 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.12.11.34. An extract from the build.sh output follows: *** Failed target:

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

Automated report: NetBSD-current/i386 build failure

2021-01-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 2021.01.26.14.09.11. An extract from the build.sh output follows: # install

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

2021-01-25 Thread Martin Husemann
On Sun, Jan 24, 2021 at 12:10:46PM -0800, Jason Thorpe wrote: > > > On Jan 24, 2021, at 11:31 AM, Robert Elz wrote: > > > > /tmp/build/2021.01.24.17.44.16-i386/tools/lib/gcc/i486--netbsdelf/9.3.0/../../../../i486--netbsdelf/bin/ld: > >

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

2021-01-24 Thread Jason Thorpe
> On Jan 24, 2021, at 5:38 PM, Robert Elz wrote: > >Date:Sun, 24 Jan 2021 16:25:55 -0800 >From:Jason Thorpe >Message-ID: > > | > If would be nice if rump weren't so bloody fragile. > > It would indeed. > > | I am not able to reproduce the build failure: > >

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

2021-01-24 Thread Robert Elz
Date:Sun, 24 Jan 2021 16:25:55 -0800 From:Jason Thorpe Message-ID: | > If would be nice if rump weren't so bloody fragile. It would indeed. | I am not able to reproduce the build failure: Odd, it is still failing on b5, on all of i386 amd64 and evbarm (the

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

2021-01-24 Thread Jason Thorpe
> On Jan 24, 2021, at 12:10 PM, Jason Thorpe wrote: > > >> On Jan 24, 2021, at 11:31 AM, Robert Elz wrote: >> >> /tmp/build/2021.01.24.17.44.16-i386/tools/lib/gcc/i486--netbsdelf/9.3.0/../../../../i486--netbsdelf/bin/ld: >> /tmp/build/2021.01.24.17.44.16-i386/destdir/usr/lib/librump.so:

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

2021-01-24 Thread Robert Elz
Date:Sun, 24 Jan 2021 18:45:38 + (UTC) From:NetBSD Test Fixture Message-ID: <161151393856.1140.6101421274186394...@babylon5.netbsd.org> | An extract from the build.sh output follows: The actual error lines (with intervening unrelated stuff deleted) are: #

Automated report: NetBSD-current/i386 build failure

2021-01-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 2021.01.24.18.02.51. An extract from the build.sh output follows: nbmake[4]: stopped in

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

2021-01-24 Thread Roland Illig
On 23.01.2021 19:34, 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 2021.01.23.17.58.03. An extract from the build.sh output follows:

Automated report: NetBSD-current/i386 build failure

2021-01-23 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.01.23.17.58.03. An extract from the build.sh output follows: *** Failed target: dependall-lint1 ***

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

2021-01-21 Thread Martin Husemann
On Thu, Jan 21, 2021 at 04:33:40PM +0100, Reinoud Zandijk wrote: > I'd like to fix this ASAP but what is the correct way of dealing with this? Is > this an i386 failure or should code just not use bus_space_read_8() or > bus_space_write_8() ? Unless the spec requires it, you should just avoid

<    1   2   3   4   5   6   7   8   9   10   >