Re: lib/60418: -current rump/wg(4) build failure

"Martin Husemann via gnats" <[email protected]>
Newsgroups gmane.os.netbsd.bugs
Message-ID <[email protected]>
The following reply was made to PR lib/60418; it has been noted by GNATS.

From: Martin Husemann <[email protected]>
To: [email protected]
Cc: 
Subject: Re: lib/60418: -current rump/wg(4) build failure
Date: Mon, 6 Jul 2026 14:13:38 +0200

 On Mon, Jul 06, 2026 at 04:40:01AM +0000, Bch via gnats wrote:
 >         /usr/src/sys/rump/net/lib/libwg/wg_user.c:45:10: fatal error: ass=
 ert.h: No such file or directory
 >            45 | #include <assert.h>
 >               |          ^~~~~~~~~~
 >         compilation terminated.
 
 I can reproduce that, but only on one out of a few update builds I did toda=
 y.
 I cleaned the objdir for sys/rump/net/lib/libwg and on this build it still
 happens.
 
 The "depends" phase gets it right, wg_user.d points at the correct assert.h
 header.
 
 Here is my compiler invocation:
 
 --- wg_user.go ---
 #   compile  libwg/wg_user.go
 /home/builds/current/tools/bin/sparc64--netbsd-gcc -O2  -fno-delete-null-po=
 inter-checks  -ffreestanding -fno-strict-aliasing   -std=3Dgnu11    -Wall -=
 Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-sign-compare  =
 -Wsystem-headers   -Wno-traditional   -Wa,--fatal-warnings  -Wreturn-type -=
 Wswitch -Wshadow -Wcast-qual -Wwrite-strings -Wextra -Wno-unused-parameter =
 -Wno-sign-compare -Werror    -Wno-address-of-packed-member  -Wno-format-zer=
 o-length -Wno-pointer-sign   -fPIE     -I/home/martin/current/src/sys/rump/=
 net/lib/libwg/../../../include  --sysroot=3D/home/builds/current/dest -D_RU=
 MPKERNEL -I/home/martin/current/src/sys/rump/net/lib/libwg/../../../librump=
 /rumpkern -DCOMPAT_50 -DCOMPAT_60 -DCOMPAT_70 -DCOMPAT_80 -DCOMPAT_90 -DCOM=
 PAT_100 -DCOMPAT_110 -nostdinc -I/home/martin/current/src/sys/rump/net/lib/=
 libwg -I. -I/home/martin/current/src/sys/rump/net/lib/libwg/../../../../../=
 common/include -I/home/martin/current/src/sys/rump/net/lib/libwg/../../../i=
 nclude -I/home/martin/current/src/sys/rump/net/lib/libwg/../../../include/o=
 pt -I/home/martin/current/src/sys/rump/net/lib/libwg/../../../../arch -I/ho=
 me/martin/current/src/sys/rump/net/lib/libwg/../../../.. -DDIAGNOSTIC -DLOC=
 KDEBUG -DKTRACE  -imacros /home/martin/current/src/sys/rump/net/lib/libwg/.=
 =2E/../../include/opt/opt_rumpkernel.h  -c -DDEBUG    -g /home/martin/curre=
 nt/src/sys/rump/net/lib/libwg/wg_user.c -o wg_user.go
 
 
 and this is from wg_user.d:
 
 wg_user.o: /home/martin/current/src/sys/rump/net/lib/libwg/wg_user.c \
  /home/builds/current/dest/usr/include/sys/cdefs.h \
 [...]
  /home/builds/current/dest/usr/include/netinet/in.h \
  /home/builds/current/dest/usr/include/netinet6/in6.h \
  /home/builds/current/dest/usr/include/assert.h \
  /home/builds/current/dest/usr/include/errno.h \
  /home/builds/current/dest/usr/include/sys/errno.h \
 [..]
 
 
 On the working builds I see (modulo the exact pathnames) the same in wg_use=
 r.d
 and the working compiler invocation e.g.:
 
 =66rom the depends phase:
 
 --- wg_user.d ---
 #    create  libwg/wg_user.d
 CC=3D/work/tools/bin/armv7eb--netbsdelf-eabihf-gcc /work/tools/bin/nbmkdep =
 -f wg_user.d --    -isysroot /work/branches/hosts-current/evbearmv7hf-eb  /=
 work/src/sys/rump/net/lib/libwg/wg_user.c
 
 
 and the real build:
 --- wg_user.o ---
 #   compile  libwg/wg_user.o
 /work/tools/bin/armv7eb--netbsdelf-eabihf-gcc -o wg_user.o -O2    -Wno-addr=
 ess-of-packed-member  -Wno-format-zero-length -Wno-pointer-sign    -Werror =
 -Wall -Wextra -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototype=
 s -isysroot /work/branches/hosts-current/evbearmv7hf-eb    -c /work/src/sys=
 /rump/net/lib/libwg/wg_user.c
 
 
 but the working builds do not try to build wg_user.go.
 
 So that made me discove I still have MKDEBUGLIB=3Dyes for this build, but r=
 emoved
 it (as it is basically never needed) from all the other builds some time
 ago.
 
 
 Martin
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.