I'm running the latest snapshot pretty much each day and then compiling
my own kernel and userland to enable vmm and, for a few days now, kernel
compilation fails with these errors. I believe userland failed to build
as well but I didn't continue since I did not want mismatched kernel and
userland.

cc  -Werror -Wall -Wimplicit-function-declaration  -Wno-main
-Wno-uninitialized  -Wframe-larger-than=2047 -mcmodel=kernel
-mno-red-zone -mno-sse2 -mno-sse -mno-3dnow  -mno-mmx -msoft-float
-fno-omit-frame-pointer -fno-builtin-printf -fno-builtin-snprintf
-fno-builtin-vsnprintf -fno-builtin-log  -fno-builtin-log2
-fno-builtin-malloc -fno-pie -O2 -pipe -nostdinc -I../../../.. -I.
-I../../../../arch -DDDB -DDIAGNOSTIC -DKTRACE -DACCOUNTING -DKMEMSTATS
-DPTRACE -DPOOL_DEBUG -DCRYPTO -DSYSVMSG -DSYSVSEM -DSYSVSHM
-DUVM_SWAP_ENCRYPT -DFFS -DFFS2 -DFFS_SOFTUPDATES -DUFS_DIRHASH -DQUOTA
-DEXT2FS -DMFS -DNFSCLIENT -DNFSSERVER -DCD9660 -DUDF -DMSDOSFS -DFIFO
-DTMPFS -DFUSE -DSOCKET_SPLICE -DTCP_SACK -DTCP_ECN -DTCP_SIGNATURE
-DINET6 -DIPSEC -DPPP_BSDCOMP -DPPP_DEFLATE -DPIPEX -DMROUTING -DMPLS
-DBOOT_CONFIG -DUSER_PCICONF -DAPERTURE -DMTRR -DNTFS -DHIBERNATE
-DPCIVERBOSE -DUSBVERBOSE -DWSDISPLAY_COMPAT_USL
-DWSDISPLAY_COMPAT_RAWKBD -DWSDISPLAY_DEFAULTSCREENS="6"
-DWSDISPLAY_COMPAT_PCVT -DX86EMU -DONEWIREVERBOSE -DMULTIPROCESSOR
-DMAXUSERS=80 -D_KERNEL -MD -MP  -c ../../../../kern/vfs_syscalls.c
../../../../kern/vfs_syscalls.c: In function 'domknodat':
../../../../kern/vfs_syscalls.c:1238: error: 'PLEDGE_DPATH' undeclared
(first use in this function)
../../../../kern/vfs_syscalls.c:1238: error: (Each undeclared identifier
is reported only once
../../../../kern/vfs_syscalls.c:1238: error: for each function it
appears in.)
*** Error 1 in /usr/src/sys/arch/amd64/compile/GENERIC.MP (Makefile:940
'vfs_syscalls.o')

This is a fresh src tree from this morning. Last night, I redownloaded
an entirely new src tree just to be sure something wasn't wrong in my
tree and then updated this morning with some more commits overnight. I
don't tend to report these kind of errors unless they go on for a while
since -current is moving target right now but this error isn't going
away. Any ideas?

Bryan

Reply via email to