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.11.08.02.08.35.
An extract from the build.sh output follows:
--- librumpdev_netsmb_pic.a ---
/tmp/bracket/b
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.29.15.37.06.
An extract from the build.sh output follows:
/tmp/bracket/build/2018.10.29.15.37.06-i386/tools/
On Oct 27, 12:59pm, g...@gson.org (Andreas Gustafsson) wrote:
-- Subject: Re: Automated report: NetBSD-current/i386 build failure
| The i386 build is still failing in gzip:
|
| /tmp/bracket/build/2018.10.27.07.24.58-i386/src/usr.bin/gzip/unlz.c:580:21:
error: format '%td' expects a
The i386 build is still failing in gzip:
/tmp/bracket/build/2018.10.27.07.24.58-i386/src/usr.bin/gzip/unlz.c:580:21:
error: format '%td' expects argument of type 'ptrdiff_t', but argument 3 has
type '__off_t {aka long long int}' [-Werror=format=]
--
Andreas Gustafsson, g...@gson.org
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.22.10.15.
An extract from the build.sh output follows:
/tmp/bracket/build/2018.10.26.22.10.15-i386/tools/
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
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
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.24.07.42.12.
An extract from the build.sh output follows:
--- dependall-libugenhc ---
/tmp/bracket/build
The NetBSD Test Fixture wrote:
> --- kern-INSTALL ---
> *** [netbsd] Error code 1
> nbmake[2]: stopped in
> /tmp/bracket/build/2018.10.16.00.32.07-i386/obj/sys/arch/i386/compile/INSTALL
More helpful error messages from earlier in the build log:
--- kern-INSTALL ---
acpi_cpu_cstate.o:
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.16.00.32.07.
An extract from the build.sh output follows:
--- kern_hook.o ---
--- kern-LEGACY ---
--
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.15.10.01.32.
An extract from the build.sh output follows:
/tmp/bracket/build/2018.10.15.10.01.32-i386/tools/
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.11.15.41.07.
An extract from the build.sh output follows:
--- obj ---
#objdir
/tmp/bracket/build/2
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.10.01.29.25.
An extract from the build.sh output follows:
--- eng_all.d ---
CC=/tmp/bracket/build/2018.
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.05.22.16.50.
An extract from the build.sh output follows:
--- dependall-crypto/external ---
#create
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.09.28.23.40.45.
An extract from the build.sh output follows:
--- cleandir-libexec ---
--- __doclean ---
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.09.25.05.57.46.
An extract from the build.sh output follows:
--- __doclean ---
--- cleandir-external ---
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.09.24.22.36.03.
An extract from the build.sh output follows:
CC=/tmp/bracket/build/2018.09.24.22.36.03-i386/to
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.09.23.21.44.01.
An extract from the build.sh output follows:
--- dependall-libdm ---
--- dm_target_linear.d
Robert Elz writes:
> Date:Sun, 23 Sep 2018 13:25:23 +0530
> From:"Cherry G.Mathew"
> Message-ID: <87efdkfy1g@zyx.in>
>
> | Should be fixed now.
>
> Not yet,...
>
Thanks for the alert. I have tested the build now it should be fixed.
I would look forward to
Date:Sun, 23 Sep 2018 13:25:23 +0530
From:"Cherry G.Mathew"
Message-ID: <87efdkfy1g@zyx.in>
| Should be fixed now.
Not yet,...
/tmp/bracket/build/2018.09.23.07.54.42-i386/src/sys/arch/x86/x86/idt.c:92:1:
error: conflicting types for 'set_idtgate'
set_idtgat
Andreas Gustafsson writes:
> Cherry,
>
> The NetBSD Test Fixture wrote:
>> --- assym.h ---
>> *** [assym.h] Error code 1
>> nbmake[2]: stopped in
>> /tmp/bracket/build/2018.09.23.02.51.06-i386/obj/sys/arch/i386/compile/INSTALL_XEN3PAE_DOMU
>
> Here's a more relevant part of the build
Cherry,
The NetBSD Test Fixture wrote:
> --- assym.h ---
> *** [assym.h] Error code 1
> nbmake[2]: stopped in
> /tmp/bracket/build/2018.09.23.02.51.06-i386/obj/sys/arch/i386/compile/INSTALL_XEN3PAE_DOMU
Here's a more relevant part of the build log:
--- assym.h ---
In file included f
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.09.23.02.51.06.
An extract from the build.sh output follows:
cleandiring the kern library objects
--- __alw
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.09.19.23.22.17.
An extract from the build.sh output follows:
^~~
/tmp/bracket/build/2018.09.19.23.22.17-i
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.09.16.23.20.18.
An extract from the build.sh output follows:
#create esdb/ISO646-JP-OCR-B.esdb
/tmp/br
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.09.13.01.55.16.
An extract from the build.sh output follows:
if (HENTER(h, &ev, decode_result)) == -1) {
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.09.12.15.58.08.
An extract from the build.sh output follows:
postinstall-fix-obsolete_stand ===> .
--- post
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.09.07.17.30.58.
An extract from the build.sh output follows:
postinstall-fix-obsolete_stand ===> .
--- post
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.09.06.08.20.12.
An extract from the build.sh output follows:
--- cleandir-tools ---
(cd /tmp/bracket/build/
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.09.04.06.05.39.
An extract from the build.sh output follows:
/tmp/bracket/build/2018.09.04.06.05.39-i386/tools/
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.09.03.14.44.31.
An extract from the build.sh output follows:
--- sf-pcap.d ---
#create lib/sf-pcap.d
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.08.28.03.48.38.
An extract from the build.sh output follows:
Target directory: /tmp/bracket/build/2018.08.28.03
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.08.27.01.36.13.
An extract from the build.sh output follows:
--- linux_file.o ---
# compile compat_linux
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.08.26.07.53.25.
An extract from the build.sh output follows:
--- dependall-pam_rhosts ---
/tmp/bracket/buil
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.08.25.08.12.28.
An extract from the build.sh output follows:
CC=/tmp/bracket/build/2018.08.25.08.12.28-i386/to
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.08.22.09.38.21.
An extract from the build.sh output follows:
kasan_free(const void *addr __unused, size_t sz_w
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.08.20.15.04.52.
An extract from the build.sh output follows:
--- kern_clock.d ---
CC=/tmp/bracket/build/20
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.08.20.08.53.48.
An extract from the build.sh output follows:
/tmp/bracket/build/2018.08.20.08.53.48-i386/tools
The NetBSD Test Fixture wrote:
> --- dependall-libexec ---
> /tmp/bracket/build/2018.08.18.09.00.28-i386/destdir/usr/lib/libssl.so:
> undefined reference to `conf_ssl_get'
> /tmp/bracket/build/2018.08.18.09.00.28-i386/destdir/lib/libcrypto.so:
> undefined reference to `conf_add_ssl_mo
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.08.18.09.00.28.
An extract from the build.sh output follows:
--- dependall-libexec ---
/tmp/bracket/build/2
Date:Fri, 17 Aug 2018 00:07:59 +0300
From:Andreas Gustafsson
Message-ID: <23413.59311.93455.342...@guava.gson.org>
| The NetBSD Test Fixture wrote:
| > --- policy.o ---
| > /tmp/bracket/build/2018.08.16.18.28.10-i386/tools/bin/nbctfconvert -g
-L VERSION
The NetBSD Test Fixture wrote:
> --- policy.o ---
> /tmp/bracket/build/2018.08.16.18.28.10-i386/tools/bin/nbctfconvert -g -L
> VERSION policy.o
> A failure has been detected in another branch of the parallel make
Here are some more useful error messages from earlier in the log:
--- d
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.08.16.18.28.10.
An extract from the build.sh output follows:
Still updating file `symtab.o'.
Consid
Date:Thu, 16 Aug 2018 12:10:00 +0200
From:Kamil Rytarowski
Message-ID:
| A compiler is allowed and nowadays requested to prevent compilation of a
| detected Undefined Behavior mistake.
In this particular case we are requesting that it not do so.By all means
On 16.08.2018 09:27, Robert Elz wrote:
> Date:Thu, 16 Aug 2018 10:09:38 +0300
> From:Andreas Gustafsson
> Message-ID: <23413.9010.387115.892...@guava.gson.org>
>
> | Christos Zoulas wrote:
> | > This is intended
> |
> | The code in case has "undefined beha
Date:Thu, 16 Aug 2018 10:09:38 +0300
From:Andreas Gustafsson
Message-ID: <23413.9010.387115.892...@guava.gson.org>
| Christos Zoulas wrote:
| > This is intended
|
| The code in case has "undefined behavior" per the C11 standard,
| section 6.5.6.8:
Yes,
Christos Zoulas wrote:
> >--- man_validate.o ---
> >/tmp/bracket/build/2018.08.15.14.31.22-i386/src/external/bsd/mdocml/lib/libmandoc/../../dist/man_validate.c:
> > In function 'man_node_validate':
> >/tmp/bracket/build/2018.08.15.14.31.22-i386/src/external/bsd/mdocml/lib/libmandoc/../../dist/man_v
Date:Thu, 16 Aug 2018 10:20:02 +0700
From:Robert Elz
Message-ID: <10853.1534389...@jinx.noi.kre.to>
| this time I will wait for my test build to complete,
That has now happened, sources from 05:10 UTC (or later)
today should now build - I hope.
I really need a com
In article <23412.21273.515317.883...@guava.gson.org>,
Andreas Gustafsson wrote:
>Christos,
>
>The build is still failing on the testbed after your commit of
>src/tools/mandoc/Makefile 1.14, with two separate errors:
>
>--- mandoc_aux.o ---
>/tmp/bracket/build/2018.08.15.14.31.22-i386/src/externa
Date:Thu, 16 Aug 2018 08:10:09 +0700
From:Robert Elz
Message-ID: <25425.1534381...@jinx.noi.kre.to>
| so with any luck, we are past the mandoc issues now.
No luck, there is at least one more... this time I will wait for my
test build to complete, rather than just
Date:Wed, 15 Aug 2018 19:21:45 +0300
From:Andreas Gustafsson
Message-ID: <23412.21273.515317.883...@guava.gson.org>
| The build is still failing on the testbed after your commit of
| src/tools/mandoc/Makefile 1.14, with two separate errors:
nakayama@ fixed one of
Christos,
The build is still failing on the testbed after your commit of
src/tools/mandoc/Makefile 1.14, with two separate errors:
--- mandoc_aux.o ---
/tmp/bracket/build/2018.08.15.14.31.22-i386/src/external/bsd/mdocml/lib/libmandoc/../../dist/mandoc_aux.c:
In function 'mandoc_recallocarray':
/
Christos Zoulas wrote:
> What is the build host?
It fails on babylon5.netbsd.org which is amd64/7.1_STABLE:
http://releng.netbsd.org/b5reports/i386/2018/2018.08.14.14.56.33/build.log.tail
--
Andreas Gustafsson, g...@gson.org
In article <23410.57852.120067.934...@guava.gson.org>,
Andreas Gustafsson wrote:
>Christos,
>
>The NetBSD Test Fixture wrote:
>>
>/tmp/bracket/build/2018.08.14.08.54.11-i386/src/tools/mandoc/../../external/bsd/mdocml/bin/mandoc/../../dist/configure:
> 513: Syntax error: "fi"
>unexpected
>
>I
In article <23410.57852.120067.934...@guava.gson.org>,
Andreas Gustafsson wrote:
>Christos,
>
>The NetBSD Test Fixture wrote:
>>
>/tmp/bracket/build/2018.08.14.08.54.11-i386/src/tools/mandoc/../../external/bsd/mdocml/bin/mandoc/../../dist/configure:
> 513: Syntax error: "fi"
>unexpected
>
>I
Christos,
The NetBSD Test Fixture wrote:
>
> /tmp/bracket/build/2018.08.14.08.54.11-i386/src/tools/mandoc/../../external/bsd/mdocml/bin/mandoc/../../dist/configure:
> 513: Syntax error: "fi" unexpected
I removed the stray "fi", but the build still fails at a later point:
--- mandoc ---
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.08.14.08.54.11.
An extract from the build.sh output follows:
selected UTF8_LOCALE=en_US.UTF-8
tested wchar-
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.08.12.14.32.39.
An extract from the build.sh output follows:
--- dependall-mpl ---
/tmp/bracket/build/2018.
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.08.06.04.50.11.
An extract from the build.sh output follows:
obsolete_stand fix:
postinstall fixes passed:
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.08.02.08.40.48.
An extract from the build.sh output follows:
#create libc/ypprot_err.d
--- nslexer.d -
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.08.01.12.36.56.
An extract from the build.sh output follows:
--- evp_pbe.po ---
/tmp/bracket/build/2018.08.
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.07.27.12.02.26.
An extract from the build.sh output follows:
--- cleandir-lib ---
--- cleandir-share ---
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.07.21.07.46.56.
An extract from the build.sh output follows:
--- crunched_skel.c ---
--- dependall-bin ---
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.07.15.06.16.12.
An extract from the build.sh output follows:
--- kern-XEN3_DOMU ---
/tmp/bracket/build/2018
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.07.13.09.58.49.
An extract from the build.sh output follows:
--- cleandir-pmc ---
--- cleandir-sys ---
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.07.12.21.42.53.
An extract from the build.sh output follows:
*where += (Elf_Addr)relocbase;
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.07.11.06.25.05.
An extract from the build.sh output follows:
--- dependall-touch ---
CC=/tmp/bracket/build
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.07.10.18.43.20.
An extract from the build.sh output follows:
--- if_msk.o ---
/tmp/bracket/build/2018.07.10
Date:Sun, 8 Jul 2018 19:28:34 + (UTC)
From:NetBSD Test Fixture
Message-ID: <153107811457.517.12437998665914189...@babylon5.netbsd.org>
| This is an automatically generated notice of a NetBSD-current/i386
| build failure.
|
| The failure occurred on babylo
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.07.08.17.58.39.
An extract from the build.sh output follows:
--- unicode.d ---
--- dependall-arch ---
-
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.06.30.16.05.44.
An extract from the build.sh output follows:
xen_resumeclocks_xc(void *a, void *b)
^~
Date:Sat, 30 Jun 2018 03:28:35 + (UTC)
From:NetBSD Test Fixture
Message-ID: <153032931594.8658.14072358424850823...@babylon5.netbsd.org>
| This is an automatically generated notice of a NetBSD-current/i386
| build failure.
| --- dependall-sys ---
|
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.06.30.01.08.39.
An extract from the build.sh output follows:
--- dependall-usr.bin ---
--- bpf.d ---
#
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.06.26.22.16.45.
An extract from the build.sh output follows:
Target directory: /tmp/bracket/build/2018.06.26.22
> On Jun 16, 2018, at 4:39 PM, Jason Thorpe wrote:
>
> Will look into this shortly.
This should be fixed now.
>
> -- thorpej
> Sent from my iPhone.
>
>> On Jun 16, 2018, at 4:16 PM, NetBSD Test Fixture wrote:
>>
>> This is an automatically generated notice of a NetBSD-current/i386
>> bui
Will look into this shortly.
-- thorpej
Sent from my iPhone.
> On Jun 16, 2018, at 4:16 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 f
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.06.16.21.28.07.
An extract from the build.sh output follows:
# compile kern/mcount.o
/tmp/bracket/build/
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.06.05.09.28.56.
An extract from the build.sh output follows:
--- rf_psstatus.o ---
/tmp/bracket/build/2018.
The i386 build is still failing as of source date 2018.06.04.02.42.23,
with the following error:
--- dependall-sys ---
In file included from
/tmp/bracket/build/2018.06.04.02.42.23-i386/src/external/cddl/osnet/dist/uts/common/sys/dtrace_impl.h:52:0,
from
/tmp/bracket/build/
On Jun 4, 6:07am, m...@eterna.com.au (matthew green) wrote:
-- Subject: re: Automated report: NetBSD-current/i386 build failure
| FWIW, yes, i did do this, both before committing and after i
| heard a report it wasn't working for chuq.
|
| i still was unable to reproduce it, and while chr
Andreas Gustafsson writes:
> matthew green wrote:
> > FWIW, i tested my change on about 5 platforms, but all
> > netbsd host. i can't reproduce the above, unfortunately.
>
> The testbed runs on a NetBSD host. Have you tried doing a
> "build.sh release" from scratch?
>
> In the meantime, the bui
> > --- dependall-kdump ---
> > In file included from
> > /tmp/bracket/build/2018.06.03.05.55.08-i386/src/sys/net/if.h:99:0,
> > from kdump-ioctl.c:23:
> > /tmp/bracket/build/2018.06.03.05.55.08-i386/src/sys/altq/if_altq.h:48:2:
> > error: unknown type name 'kmutex_t'
> > kmute
FWIW, amd64 is also affected:
http://www.gson.org/netbsd/bugs/build/amd64-baremetal/2018/2018.06.03.13.23.58/build.log.tail
To find the relevant error message in the above, search for kmutex_t.
--
Andreas Gustafsson, g...@gson.org
matthew green wrote:
> FWIW, i tested my change on about 5 platforms, but all
> netbsd host. i can't reproduce the above, unfortunately.
The testbed runs on a NetBSD host. Have you tried doing a
"build.sh release" from scratch?
In the meantime, the build has been broken in a fifth way, this tim
Andreas Gustafsson writes:
> The build is still failing as of source date 2018.06.03.05.55.08,
> now with the following error messages:
>
> --- dependall-kdump ---
> In file included from
> /tmp/bracket/build/2018.06.03.05.55.08-i386/src/sys/net/if.h:99:0,
> from kdump-ioctl.c:23
The build is still failing as of source date 2018.06.03.05.55.08,
now with the following error messages:
--- dependall-kdump ---
In file included from
/tmp/bracket/build/2018.06.03.05.55.08-i386/src/sys/net/if.h:99:0,
from kdump-ioctl.c:23:
/tmp/bracket/build/2018.06.03.05.55.08-
This morning, the NetBSD Test Fixture wrote:
> /tmp/bracket/build/2018.06.02.03.02.30-i386/tools/bin/i486--netbsdelf-ld:
> use the --help option for usage information
> *** [libcompat.o] Error code 1
The build is still failing as of source date 2018.06.02.15.47.22,
now with the following
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.06.02.03.02.30.
An extract from the build.sh output follows:
#create INSTALL/init_sysctl.d
CC=/tmp/br
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.06.01.16.13.08.
An extract from the build.sh output follows:
--- hwsleep.o ---
# compile LEGACY/hwsleep.
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.05.29.11.18.50.
An extract from the build.sh output follows:
--- dependall-makefs ---
/tmp/bracket/build/20
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.05.28.21.05.16.
An extract from the build.sh output follows:
mv -f libunbound.so.6.2.tmp libunbound.so.6.2
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.05.24.20.04.46.
An extract from the build.sh output follows:
--- postinstall-fix-obsolete_stand ---
===
Hi kamil,
The NetBSD Test Fixture wrote:
> --- dependall-tests ---
> *** [t_ptrace_wait.o] Error code 1
> nbmake[9]: stopped in
> /tmp/bracket/build/2018.05.23.13.51.27-i386/src/tests/lib/libc/sys
> 1 error
>
> The following commits were made between the last successful build and
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.05.23.13.51.27.
An extract from the build.sh output follows:
rm -f .gdbinit
--- dependall-unzip ---
---
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.05.23.02.08.40.
An extract from the build.sh output follows:
postinstall-fix-obsolete_stand ===> .
--- post
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.05.22.08.15.26.
An extract from the build.sh output follows:
mv -f kern_sysctl.d.tmp kern_sysctl.d
--- kern
> On May 20, 2018, at 7:50 AM, 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 2018.05.20.14.08.33.
Sorry guys, I forgot to “c
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.05.20.14.08.33.
An extract from the build.sh output follows:
--- cleandir-libexec ---
--- __docleandir ---
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.05.19.01.53.24.
An extract from the build.sh output follows:
c++ -I.
-I/tmp/bracket/build/2018.05.19.01.53.24-
Date:Wed, 16 May 2018 12:11:52 + (UTC)
From:NetBSD Test Fixture
Message-ID: <152647271276.4669.15116410426276739...@babylon5.netbsd.org>
| This is an automatically generated notice of a NetBSD-current/i386
| build failure.
|
| The failure occurred on babyl
701 - 800 of 1468 matches
Mail list logo
