On Sun, 2024-10-06 at 09:09 +0100, Roy Marples wrote:
> Actually the file wasn't there!
> And that was the clue - a simple hg clone of xsrc checkedout xorg and
> not trunk.
> Is there a way to fixate a default branch on clone on anonhg so this
> doens't happen to others?
>
Mostly, but only mostly
On Sun, 06 Oct 2024 00:24:22 +0100 Robert Swindells wrote ---
>
> Roy Marples r...@marples.name> wrote:
> > --- includes-libepoxy ---
> > nbmake[7]: don't know how to make gl_generated.h. Stop
> > nbmake[7]: stopped making "includes" in
> > /home/roy/src/src/external/mit/xorg/lib/l
Roy Marples wrote:
> --- includes-libepoxy ---
> nbmake[7]: don't know how to make gl_generated.h. Stop
> nbmake[7]: stopped making "includes" in
> /home/roy/src/src/external/mit/xorg/lib/libepoxy
> nbmake[6]: stopped making "includes" in
> /home/roy/src/src/external/mit/xorg/lib
>
> Looking t
--- includes-libepoxy ---
nbmake[7]: don't know how to make gl_generated.h. Stop
nbmake[7]: stopped making "includes" in
/home/roy/src/src/external/mit/xorg/lib/libepoxy
nbmake[6]: stopped making "includes" in /home/roy/src/src/external/mit/xorg/lib
Looking through the sources, gl_generated and f
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.10.03.16.59.15.
An extract from the build.sh output follows
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.10.01.17.15.59.
An extract from the build.sh output follows:
--- drmkms_linux.kmod ---
# link
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.09.28.19.36.20.
An extract from the build.sh output follows:
2228 | SCARG(&clone_args, parent_ti
On Thu, Sep 26, 2024 at 05:01:45PM +0200, Thomas Klausner wrote:
> Thanks. The fix still means that ~two days of NetBSD-current/amd64
> can not be used to build a new NetBSD-current: If one has the broken
> version, then one needs to downgrade to a version before the switch to
> the new jemalloc.
On Thu, Sep 26, 2024 at 02:24:21PM -, Christos Zoulas wrote:
> In article ,
> Thomas Klausner wrote:
> >On Thu, Sep 26, 2024 at 10:29:03AM +0200, Thomas Klausner wrote:
> >> Hi!
> >>
> >> With latest source, I see
> >>
> >> --- Process.lo ---
> >> In file included from
> >/usr/src/tools/llv
In article ,
Thomas Klausner wrote:
>On Thu, Sep 26, 2024 at 10:29:03AM +0200, Thomas Klausner wrote:
>> Hi!
>>
>> With latest source, I see
>>
>> --- Process.lo ---
>> In file included from
>/usr/src/tools/llvm-lib/libLLVMSupport/../../llvm/../../external/apache2/llvm/lib/../dist/llvm/lib/Supp
On Thu, Sep 26, 2024 at 10:29:03AM +0200, Thomas Klausner wrote:
> Hi!
>
> With latest source, I see
>
> --- Process.lo ---
> In file included from
> /usr/src/tools/llvm-lib/libLLVMSupport/../../llvm/../../external/apache2/llvm/lib/../dist/llvm/lib/Support/Process.cpp:108:
> /usr/src/tools/llvm-
Hi!
With latest source, I see
--- Process.lo ---
In file included from
/usr/src/tools/llvm-lib/libLLVMSupport/../../llvm/../../external/apache2/llvm/lib/../dist/llvm/lib/Support/Process.cpp:108:
/usr/src/tools/llvm-lib/libLLVMSupport/../../llvm/../../external/apache2/llvm/lib/../dist/llvm/lib/Su
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.09.23.15.08.36.
An extract from the build.sh output follows:
| ^~~~
In
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.09.22.19.04.43.
An extract from the build.sh output follows:
${OBJCOPY} ${OBJCOPYLIBFLAGS} ${.TARGET
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.09.16.17.25.34.
An extract from the build.sh output follows:
/tmp/build/2024.09.16.17.25.34-i386/tools/bin
I just had the following happen during a build with '-j 12', in the
"make includes" phase. This looks like a parallel build race failure
where the same rules were run in parallel when they shouldn't have done
so. (I'm pretty sure I've seen similar races in other parts of the tree
before too, but
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.09.08.15.26.46.
An extract from the build.sh output follows:
cd /tmp/build/2024.09.08.15.26.46-i386/src
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.09.02.14.58.13.
An extract from the build.sh output follows:
3533
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.09.02.05.14.45.
An extract from the build.sh output follows:
./usr/bin/shmif_pcapin
./usr/share/man/html1
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.08.27.21.52.39.
An extract from the build.sh output follows:
nbmake[1]: stopped making "release"
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.08.19.07.28.22.
An extract from the build.sh output follows:
--- dependall-usr.bin ---
/tmp/build
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.08.02.17.13.02.
An extract from the build.sh output follows
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.08.01.13.41.15.
An extract from the build.sh output follows
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.07.25.00.07.33.
An extract from the build.sh output follows:
${MAKEDIRTARGET} .
${SUBDIR_GROUP
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.07.24.20.29.43.
An extract from the build.sh output follows:
from
/tmp/build
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.07.15.13.51.10.
An extract from the build.sh output follows:
--- dependall-share ---
--- fr_FR.ISO8859-15
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.07.10.19.37.41.
An extract from the build.sh output follows:
CC=/tmp/build/2024.07.10.19.37.41-i386/tools/bin
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.07.08.22.36.29.
An extract from the build.sh output follows:
nbmake[3]: stopped making "cleandir"
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.06.30.07.36.32.
An extract from the build.sh output follows:
longest path: 838 (code:178
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.06.29.14.09.35.
An extract from the build.sh output follows:
/tmp/build/2024.06.29.14.09.35-i386/tools/bin
Should be fixed now.
Thanks,
rin
On 2024/06/29 17:20, Rin Okuyama wrote:
Oops, sorry, I was just going to fix this.
On 2024/06/29 17:15, NetBSD Test Fixture wrote:
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org
Oops, sorry, I was just going to fix this.
On 2024/06/29 17:15, NetBSD Test Fixture wrote:
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.06.29.07.52.16.
An
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.06.29.07.52.16.
An extract from the build.sh output follows:
/tmp/build/2024.06.29.07.52.16-i386/tools/bin
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.06.22.20.17.25.
An extract from the build.sh output follows:
cd /tmp/build/2024.06.22.20.17.25-i386/src
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.06.19.09.02.48.
An extract from the build.sh output follows:
--- kern-MONOLITHIC ---
--- intel_wakeref.o
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.06.18.17.31.17.
An extract from the build.sh output follows:
*** In directory:
/tmp/build/2024.06.18.17.31.17
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.06.17.20.25.20.
An extract from the build.sh output follows:
nbmake[6]: stopped in
/tmp/build
On Mon, 17 Jun 2024 at 19:42, matthew green wrote:
>
> Chavdar Ivanov writes:
> > # compile INSTALL_XEN3_DOMU/aes_ni.o
> [ ... ]
> > [-Werror=stringop-overread]
>
> this indicates you're still seeing the thing that should be fixed with
> bsd.own.mk 1.1379?
Yes, I already rebuilt amd64, now reb
Chavdar Ivanov writes:
> # compile INSTALL_XEN3_DOMU/aes_ni.o
[ ... ]
> [-Werror=stringop-overread]
this indicates you're still seeing the thing that should be fixed with
bsd.own.mk 1.1379?
.mrg.
On Sun, 16 Jun 2024 at 20:23, matthew green wrote:
>
> OK, this should be fixed now at bsd.own.mk 1.1378.
>
> the problem was that for the xen kernel builds, MACHINE=xen,
> and the bsd.own.mk snippet was checking for "i386" and "amd64",
> and not "xen". i was able to trigger the failure in a tree
OK, this should be fixed now at bsd.own.mk 1.1378.
the problem was that for the xen kernel builds, MACHINE=xen,
and the bsd.own.mk snippet was checking for "i386" and "amd64",
and not "xen". i was able to trigger the failure in a tree
using an empty mk.conf, still not sure why i didn't see it in
both reported issues (bracket, pgoyette) are with a xen kernel,
and i see it may end up with non-std-x86 values of MACHINE and/or
MACHINE_ARCH in some cases, but why i'm not seeing it is confusing
me quite a bit here.
src/sys> grep ^machine arch/i386/conf/std.xen
machine xen i386 x86
this *
NetBSD Test Fixture writes:
> --- aes_via.o ---
> In file included from
> /tmp/build/2024.06.15.20.36.38-i386/src/sys/sys/systm.h:648,
> from
> /tmp/build/2024.06.15.20.36.38-i386/src/sys/crypto/aes/arch/x86/aes_via.c:35:
>
> /tmp/build/2024.06.15.20.36.38-i386/s
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.06.15.20.36.38.
An extract from the build.sh output follows:
/tmp/build/2024.06.15.20.36.38-i386/tools/bin
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.06.15.12.38.16.
An extract from the build.sh output follows:
== 2 missing files in DESTDIR
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.06.11.14.32.18.
An extract from the build.sh output follows:
#format man4.mvme68k/zsc.html4
if test
On Tue, Jun 11, 2024 at 10:07:11AM +, NetBSD Test Fixture wrote:
> This is an automatically generated notice of a NetBSD-current/i386
> build failure.
>
> The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
> using sources from CVS date 2024.06.11.09.26.58.
>
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.06.11.09.26.58.
An extract from the build.sh output follows:
#create lib/load_http.d
CC=/tmp/build
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.06.09.19.36.07.
An extract from the build.sh output follows:
--- archive_check_magic.pico
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.06.01.09.45.36.
An extract from the build.sh output follows:
--- dependall ---
--- gzip.lo
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.05.24.11.33.04.
An extract from the build.sh output follows:
1271 | dhcpcd_handlehwaddr(struct interface *ifp
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.05.19.20.09.40.
An extract from the build.sh output follows:
nbmake[3]: stopped in /tmp/build
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.05.19.13.28.28.
An extract from the build.sh output follows:
132 | ret = ttm_bo_uvm_fault_idle(bo, ufi
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.05.14.15.17.57.
An extract from the build.sh output follows:
find: ./i386: No such file or directory
find
On Sun, 12 May 2024 at 09:14, Chavdar Ivanov wrote:
>
> Hi,
>
> I am getting:
>
> #create libEGL/loader.d
> CC=/dumps/sysbuild/evbarm64/tools/bin/aarch64--netbsd-gcc
> /dumps/sysbuild/evbarm64/tools/bin/nbmkdep -f loader.d.tmp --
> -std=gnu99 -Werror --sysroot=/dumps/sysbuild/evbarm64/
Hi,
Just noticing that wip/lldb and manually configured llvm that includes
lldb fail to complete under aarch64 -current. It builds OK under
amd64. Earlier versions used to work under both, so there is some
regression with respect to NetBSD support. I build it as I regularly
rebuild and test zig, w
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.05.12.17.26.51.
An extract from the build.sh output follows:
--- rf_reconstruct.d ---
#create raid
Hi,
I am getting:
#create libEGL/loader.d
CC=/dumps/sysbuild/evbarm64/tools/bin/aarch64--netbsd-gcc
/dumps/sysbuild/evbarm64/tools/bin/nbmkdep -f loader.d.tmp --
-std=gnu99 -Werror --sysroot=/dumps/sysbuild/evbarm64/de
stdir -I/usr/xsrc/external/mit/MesaLib/dist/include
-I/usr/xsrc/ext
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.05.08.16.08.08.
An extract from the build.sh output follows:
=> /tmp/build/2024.05.08.16.08.08-i386/to
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.05.02.00.01.48.
An extract from the build.sh output follows:
161 | { FE_DOWNWARD, 0x2.18p+52L
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.04.28.01.21.27.
An extract from the build.sh output follows:
./usr/tests/lib/libstdc++/t_sync_with_stdio
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.04.24.14.02.39.
An extract from the build.sh output follows:
( cd dhcpcd; printf '.PATH: ${dhcpcd_S
On Sun, 21 Apr 2024 at 06:42, Izumi Tsutsui wrote:
>
> > cat work.mbr.truncated work.efi imgroot.fs work.gpt > work.img
> > /dumps/sysbuild/amd64/tools/bin/nbgpt work.img biosboot -i 2
> > -c
> > /dumps/sysbuild/amd64/obj/home/sysbuild/src/distrib/amd64/liveimage/emuimage/work/usr/mdec/gptmbr
> cat work.mbr.truncated work.efi imgroot.fs work.gpt > work.img
> /dumps/sysbuild/amd64/tools/bin/nbgpt work.img biosboot -i 2
> -c
> /dumps/sysbuild/amd64/obj/home/sysbuild/src/distrib/amd64/liveimage/emuimage/work/usr/mdec/gptmbr.bin
> nbgpt: work.img: No primary GPT header; run create or r
I made some changes to the live image which is probably triggering this
behaviour, but it's working on releng's builds - I expect that there's a
stale object that the live-image target isn't re-creating despite it
needing changes.
You could take the easy-for-human approach and do a clean build, bu
Hi,
I am presently getting:
mv work.rootfs imgroot.fs
create EFI system partition...
/dumps/sysbuild/amd64/tools/bin/x86_64--netbsd-install -c -m 0644
work/usr/mdec/bootx64.efi work.efidir/EFI/boot/`basename
work/usr/mdec/bootx64.efi`
/dumps/sysbuild/amd64/tools/bin/x86_64--netbsd-install -c
On Sat, 20 Apr 2024 at 17:49, Chavdar Ivanov wrote:
>
> Hi,
>
> I am presently getting:
>
>
> mv work.rootfs imgroot.fs
> create EFI system partition...
> /dumps/sysbuild/amd64/tools/bin/x86_64--netbsd-install -c -m 0644
> work/usr/mdec/bootx64.efi work.efidir/EFI/boot/`basename
> work/usr/md
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.04.13.17.22.33.
An extract from the build.sh output follows:
/tmp/build/2024.04.13.17.22.33-i386/tools/lib
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.04.09.15.17.25.
An extract from the build.sh output follows
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.04.07.15.02.08.
An extract from the build.sh output follows:
# execute checkflist
cd /tmp/build
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.04.05.11.20.34.
An extract from the build.sh output follows:
/tmp/build/2024.04.05.11.20.34-i386/tools/bin
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.04.05.01.16.01.
An extract from the build.sh output follows:
/tmp/build/2024.04.05.01.16.01-i386/tools/bin
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.04.03.01.52.28.
An extract from the build.sh output follows:
351 | #define ENTERI() ENTERIT(long double
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.03.20.17.11.44.
An extract from the build.sh output follows:
# link fujhk/fujhk.kmod
/tmp/build
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.03.15.20.09.31.
An extract from the build.sh output follows:
--- rump_syscalls.o ---
In file included from
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.03.03.17.43.32.
An extract from the build.sh output follows:
/tmp/build/2024.03.03.17.43.32-i386/tools/bin
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.02.24.15.16.53.
An extract from the build.sh output follows:
--- dependall-gdb ---
--- backtrace.o
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.02.21.21.55.16.
An extract from the build.sh output follows:
nbmake[4]: stopped in /tmp/build
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.02.19.12.41.27.
An extract from the build.sh output follows:
|char *
| %d
In
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.02.17.18.06.35.
An extract from the build.sh output follows:
/tmp/build/2024.02.17.18.06.35-i386/tools/bin
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.01.29.05.02.06.
An extract from the build.sh output follows:
--- kern-LEGACY ---
nbmake[1]: stopped in
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.01.25.00.30.57.
An extract from the build.sh output follows:
cd /tmp/build/2024.01.25.00.30.57-i386/src
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.01.23.19.44.28.
An extract from the build.sh output follows:
# execute checkflist
cd /tmp/build
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.01.21.18.53.19.
An extract from the build.sh output follows:
| ^~
--- catrig.po
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.01.20.14.55.11.
An extract from the build.sh output follows:
--- compat_opendir.d ---
#create libc
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.01.19.18.45.01.
An extract from the build.sh output follows:
67 | ru50->ru_maxrss = ru->ru_
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2024.01.02.19.28.25.
An extract from the build.sh output follows:
343 | static const rb_tree_ops_t sample_ops
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2023.12.18.15.52.37.
An extract from the build.sh output follows:
CC=/tmp/build/2023.12.18.15.52.37-i386/tools/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 2023.11.23.21.30.03.
An extract from the build.sh output follows:
./usr/share/man/html7/stack.html
./usr/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 2023.10.27.05.45.00.
An extract from the build.sh output follows:
--- errata.o ---
/tmp/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 2023.10.25.20.23.26.
An extract from the build.sh output follows:
--- /tmp/build/2023.10.25.20.23.26-i386/destdir
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 2023.10.20.10.09.44.
An extract from the build.sh output follows:
93 | #define DESC_BOUNDARY (1ULL <&
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 2023.10.17.12.07.42.
An extract from the build.sh output follows:
63 | offsetof(dom0_vga_console_info_t
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 2023.10.15.10.46.51.
An extract from the build.sh output follows:
CC=/tmp/build/2023.10.15.10.46.51-i386/tools/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 2023.10.13.20.57.30.
An extract from the build.sh output follows:
/tmp/build/2023.10.13.20.57.30-i386/src/distrib
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 2023.09.25.17.09.27.
An extract from the build.sh output follows:
mv -f ipmi.d.tmp ipmi.d
--- kern-XEN3PAE_DOMU
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 2023.09.25.07.12.25.
An extract from the build.sh output follows:
--- interwave.o ---
/tmp/build
Thanks .mgr for guidence here.
Looks like I didn't correctly get latest updates on src. To test:
I renamed current failed src and obj, to src.old and obj.old.
I rsync'd latest (11-Sep) and did a tools, kernel, and release build; it
succeeded and all good as you said.
I took latest src with copy of
> nbmtree: .: missing directory in specification
> nbmtree: failed at line 1 of the specification
there must be something wrong in your build tree or src tree.
i updated and built this from a clean tree fine.
this should have been fixed with this pullup:
revision 1.175.2.1
date: 2023-09-04 10:33
I'm trying to build a newly sync'd RockPro64 kernel and userland:
./build.sh -U -u -j6 -O ../obj -m evbarm -a aarch64 kernel=ROCKPRO64
distribution
I can successfully build tools and the kernel (copied GENERIC64 to
ROCKPRO64). Here's the error when I try a distribution build:
obj ===> distrib/evba
1 - 100 of 1440 matches
Mail list logo
