On Sat, 6 Dec 2025, Van Ly wrote:
===> build.sh command: ./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=yes -V MKDEBUGKERNEL=yes -V MKDEBUGLIB=yes -V KERNEL_DIR=yes -V USE_XZ_SETS=yes -U -x -N0 -m amd64 -j4 build [...] x86_64--netbsd-install: libgcc_s_g.a: stat: No such file or directory --- /local/n/11/build/dst/amd64/usr/lib/libgcc_s_g.a ---*** Failed target: /local/n/11/build/dst/amd64/usr/lib/libgcc_s_g.a *** In directory: /usr/src/external/gpl3/gcc/lib/libgcc/libgcc_s *** Failed commands: ${_MKTARGET_INSTALL} => @# "install " /local/n/11/build/dst/amd64/usr/lib/libgcc_s_g.a ${INSTALL_FILE} -o ${LIBOWN} -g ${LIBGRP} -m ${LIBMODE} ${_INSTRANLIB} ${.ALLSRC} ${.TARGET} => /local/n/11/build/tools/x86_64/amd64/bin/x86_64--netbsd-install -U -M /local/n/11/build/dst/amd64/METALOG -D /local/n/11/build/dst/amd64 -h sha256 -N /usr/src/etc -c -r -o root -g wheel -m 444 libgcc_s_g.a /local/n/11/build/dst/amd64/usr/lib/libgcc_s_g.a *** [/local/n/11/build/dst/amd64/usr/lib/libgcc_s_g.a] Error code 1
I think this is a consequence of you setting the (non-standard) `MKDEBUGLIB=yes' combined with the default of `MKSTATICLIB=yes'. There's no need to force `MKDEBUGLIB=yes'. With the default `MKDEBUG=yes', you get *.debug files for shared libraries anyway. Stick to the way the std. build is done. Eg.: https://releng.netbsd.org/builds/netbsd-11/20251207091023Z/amd64.build Other combinations (like fully static + debug builds) may not have been tested at all--unless you want to go out on a limb... -RVP
