> Date: Sun, 20 Aug 2023 14:11:02 +0200 > From: Martin Husemann <mar...@duskware.de> > > On Sun, Aug 20, 2023 at 12:08:01PM +0000, Taylor R Campbell wrote: > > > /r0/build/current/tools/amd64/bin/mips64el--netbsd-gcc > > > --sysroot=/r0/build/current/DEST/evbmips64-el -Wl,--warn-shared-textrel > > > -pie -shared-libgcc -o t_workqueue t_workqueue.o > > > -Wl,-rpath-link,/r0/build/current/DEST/evbmips64-el/lib -L=/lib > > > -lrumpvfs -lrumpvfs_nofifofs -lrump -lrumpuser -lpthread -lrump > > > -L/r0/build/current/obj/mips64el/tests/rump/kernspace -lkernspace > > > -latf-c > > > /r0/build/current/tools/amd64/lib/gcc/mips64el--netbsd/10.5.0/../../../../mips64el--netbsd/bin/ld: > > > t_workqueue.o: in function `atfu_workqueue_wait_pause_body': > > > /x/current/src/tests/rump/rumpkern/t_workqueue.c:96: undefined reference > > > to `rumptest_workqueue_wait_pause' > > Is this with an update build? I think I had to clean some test obj dirs after > the latest changes to workqueue (and probably forgot to note it in UPDATING)
I changed tests/rump/rumpkern/Makefile to use PROGDPLIBS so that t_workqueue should get relinked correctly even in an update build, in order to avoid needing a note in UPDATING. Curious to understand how this could happen? Surely we should be able to get this working without manual intervention.
