This is a self-hosted amd64; the failure was during the (re)build of the kernel module for x11/nvidia-driver-340 as the final bit of "make buildkernel": ... >>> stage 3.1: building everything ... ===> nvidia-driver-340-340.102 depends on file: /usr/local/libdata/pkgconfig/xext.pc - found ===> Configuring for nvidia-driver-340-340.102 ===> Building for nvidia-driver-340-340.102 ===> src (all) make[6]: "/usr/src/share/mk/bsd.obj.mk" line 89: Malformed conditional (defined(SRCTOP) && (${CANONICALOBJDIR} == /${RELDIR} || ${.OBJDIR} == /${RELDIR})) make[6]: Fatal errors encountered -- cannot continue make[6]: stopped in /common/S4/obj/usr/src/amd64.amd64/sys/CANARY/common/ports/x11/nvidia-driver-340/work/NVIDIA-FreeBSD-x86_64-340.102/src *** Error code 1 Stop. make[5]: stopped in /common/S4/obj/usr/src/amd64.amd64/sys/CANARY/common/ports/x11/nvidia-driver-340/work/NVIDIA-FreeBSD-x86_64-340.102 ===> Compilation failed unexpectedly. .... As noted, the previous successful build in head/amd64 was r325383: FreeBSD g1-252.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #2 r325383M/325385:1200052: Sat Nov 4 06:54:48 PDT 2017 root_at_g1-252.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY amd64 I have 'PORTS_MODULES=x11/nvidia-driver-340' in src.conf -- as I'm rebuilding the kernel fairly often (daily), it seemed to make sense to ensure that the nvidia kmod stays synchronized. Any suggestions for evasive maneuvers? Thanks! Peace, david -- David H. Wolfskill david_at_catwhisker.org Unsubstantiated claims of "Fake News" are evidence that the claimant lies again. See http://www.catwhisker.org/~david/publickey.gpg for my public key.
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:13 UTC