compat_netbsd32 linker error messages on NetBSD/amd64 6 beta

[Jan Danielsson <jan.m.danielsson%gmail.com@localhost>]

Hello,

  I keep getting:

kobj_checksyms, 867: [compat_netbsd32]: linker error: symbol
`compat_12_sys_stat' not found
kobj_checksyms, 867: [compat_netbsd32]: linker error: symbol
`netbsd32___ntp_gettime50' not found
kobj_checksyms, 867: [compat_netbsd32]: linker error: symbol
`compat_12_sys_lstat' not found
kobj_checksyms, 867: [compat_netbsd32]: linker error: symbol
`compat_30_sys_socket' not found
kobj_checksyms, 867: [compat_netbsd32]: linker error: symbol
`compat_12_sys_reboot' not found
kobj_checksyms, 867: [compat_netbsd32]: linker error: symbol
`compat_14_sys_msgctl' not found
kobj_checksyms, 867: [compat_netbsd32]: linker error: symbol
`compat_12_sys_fstat' not found
kobj_checksyms, 867: [compat_netbsd32]: linker error: symbol
`compat_30_sys_getfh' not found
kobj_checksyms, 867: [compat_netbsd32]: linker error: symbol
`compat_12_sys_getdirentries' not found
kobj_checksyms, 867: [compat_netbsd32]: linker error: symbol
`netbsd32_ntp_adjtime' not found
kobj_checksyms, 867: [compat_netbsd32]: linker error: symbol
`compat_30_sys_fhopen' not found
kobj_checksyms, 867: [compat_netbsd32]: linker error: symbol
`compat_30_sys_fhstatvfs1' not found
kobj_checksyms, 867: [compat_netbsd32]: linker error: symbol
`compat_14_sys_shmctl' not found
kobj_checksyms, 867: [compat_netbsd32]: linker error: symbol
`compat_09_sys_uname' not found
kobj_checksyms, 867: [compat_netbsd32]: linker error: symbol
`native_sigset13_to_sigset' not found
kobj_checksyms, 867: [compat_netbsd32]: linker error: symbol
`native_sigset_to_sigset13' not found
WARNING: module error: unable to affix module `compat_netbsd32'

   I have disabled compat_netbsd32 (and a bunch of other compat-options)
in the kernel config since I wasn't planning on running any old binaries
on my system, so I sort-of understand where the messages are coming
from. But since I haven't explicitly built any 32-bit binaries, I'm
still somewhat surprised I'm getting those messages.

   Is disabling compat_netbsd32 merely a theoretical construct?

-- 
Kind regards,
Jan Danielsson