Current-Users archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Automated report: NetBSD-current/i386 build failure
Date: Thu, 2 Apr 2020 14:09:14 +0000 (UTC)
From: NetBSD Test Fixture <bracket%NetBSD.org@localhost>
Message-ID: <158583655484.15292.8162724620486601477%babylon5.NetBSD.org@localhost>
| An extract from the build.sh output follows:
|
| # create libgdb/maint.d
| --- dependall-gcc ---
| /tmp/bracket/build/2020.04.02.11.52.41-i386/src/external/gpl3/gcc/dist/gcc/machmode.h: In function 'poly_uint16 mode_to_nunits(machine_mode)':
| --- dependall-gdb ---
| CC=/tmp/bracket/build/2020.04.02.11.52.41-i386/tools/bin/i486--netbsdelf-c++ /tmp/bracket/build/2020.04.02.11.52.41-i386/tools/bin/nbmkdep -f maint.d.tmp -- -std=gnu++11 --sysroot=/tmp/bracket/build/2020.04.02.11.52.41-i386/destdir -D_KERNTYPES -I/tmp/bracket/build/2020.04.02.11.52.41-i386/src/external/gpl3/gdb/lib/libgdb -I/tmp/bracket/build/2020.04.02.11.52.41-i386/src/external/gpl3/gdb/lib/libgdb/arch/i386 -I/tmp/bracket/build/2020.04.02.11.52.41-i386/src/external/gpl3/gdb/lib/libgdb/../../dist/gdb -I/tmp/bracket/build/2020.04.02.11.52.41-i386/src/external/gpl3/gdb/lib/libgdb/../../dist/gdb/config -I/tmp/bracket/build/2020.04.02.11.52.41-i386/src/external/gpl3/gdb/lib/libgdb/../../dist/gdb/common -I/tmp/bracket/build/2020.04.02.11.52.41-i386/src/external/gpl3/gdb/lib/libgdb/../../dist/gdb/gnulib/import -I/tmp/bracket/build/2020.04.02.11.52.41-i386/src/external/gpl3/gdb/lib/libgdb/../../dist/include/opcode -I/tmp/bracket/build/2020.04.02.11.52.41-i386/src/exte!
rnal/gpl3/
gdb
| /lib/libgdb/../../dist/libdecn--- dependall-gcc ---
| /tmp/bracket/build/2020.04.02.11.52.41-i386/src/external/gpl3/gcc/dist/gcc/machmode.h:593:30: error: 'mode_nunits_inline' was not declared in this scope
| ? mode_nunits_inline (mode) : mode_nunits[mode]);
| ^
| *** [min-insn-modes.lo] Error code 1
| nbmake[9]: stopped in /tmp/bracket/build/2020.04.02.11.52.41-i386/src/external/gpl3/gcc/usr.bin/backend
This looks to be something in the build infrastructure - most likely
parallel builds getting out of sync. It is inconceivable that any of
the commits between the previous successful build and this one could
have caused this particular problem.
Further, it is just as inconceivable that the following commits could
have fixed it, yet the subsequent build went past this point (seemingly,
with stuff happening in parallel it is always hard to be certain).
That build also failed - because of a different problem, which I believe
Roy has already fixed (that failure won't get reported here, but
assuming it was fixed, the "success" message should come soon).
kre
Home |
Main Index |
Thread Index |
Old Index