Martin Husemann <[email protected]> writes:
> On Sat, Dec 06, 2025 at 01:54:24PM +0000, Van Ly wrote: >> The most recent cvs pullup hasn't included the update. https://mail-index.netbsd.org/current-users/2025/10/11/msg046903.html see final hunk in cvs rdiff -u -r1.487 -r1.488 src/distrib/sets/lists/debug/mi +./usr/tests/lib/libpthread/weak/libh_pthread_weak_g.a comp-c-debuglib atf,debuglib,compattestfile > Now I'm confused, this is supposed to be fixed in netbsd-11, do you > mean the fix did not work for you? If the daily release build infrastructure for 11 beta runs to completion, I may have an issue with my local environment. The fix I'm looking for is to complete `build.sh .. release' and I wasn't able to because the file `libh_pthread_weak_g.a' would respawn after `build.sh .. build'. Do you have any other non-standard > build.sh options besides DEBUGLIB=yes ? These are the environment variables [1] before calling [2]. I've set `no' to the MKDEBUG, MKDEBUGKERNEL, MKDEBUGLIB options. See how it goes. [1] fretsaw# printenv ENV=/root/.shrc BLOCKSIZE=1k PWD=/root LANG=C.UTF-8 HOME=/root LC_ALL=C.UTF-8 PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/pkg/sbin:/usr/pkg/bin:/usr/games:/usr/X11R7/bin:/usr/local/sbin:/usr/local/bin HOST=fretsaw TERM=xterm USER=root TZ=Australia/Sydney [email protected]:/cvsroot LOGNAME=root SU_FROM=v SHELL=/bin/sh CVS_RSH=ssh [2] cd /usr/src script -a -c "./build.sh \ -D /local/n/11/build/dst/amd64 \ -O /local/n/11/build/obj/amd64 \ -T /local/n/11/build/tools/x86_64/amd64 \ -X /usr/xsrc \ -R /local/n/11/build/rel \ -V RELEASEMACHINEDIR=amd64 \ -V MKDEBUG=no \ -V MKDEBUGKERNEL=no \ -V MKDEBUGLIB=no \ -V KERNEL_DIR=yes \ -V USE_XZ_SETS=yes \ -U -x -N0 -m amd64 -j4 release" /tmp/build_release_log -- vl
