Date: Mon, 8 May 2017 09:04:08 -0700 From: "Simon J. Gerraty" <sjg@juniper.net> To: "O. Hartmann" <ohartmann@walstatt.org> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org>, <sjg@juniper.net> Subject: Re: filemon: weird full-time build although filemon enabled Message-ID: <25259.1494259448@kaos.jnpr.net> In-Reply-To: <20170508173709.37e94b17@thor.intern.walstatt.dynvpn.de> References: <20170506092255.083828f8@thor.intern.walstatt.dynvpn.de> <16322.1494224695@kaos.jnpr.net> <20170508173709.37e94b17@thor.intern.walstatt.dynvpn.de>
next in thread | previous in thread | raw e-mail | index | archive | help
O. Hartmann <ohartmann@walstatt.org> wrote: > It is weird! > = > Today, after yesterday's built, I face the same 90 minutes build horror = again, this time > I switched on "-dM" with the make command. > = > This happens: > = > [...] > /usr/obj/usr/src/lib/clang/libllvm/_usr_obj_usr_src_lib_clang_libllvm_Co= deGen_SelectionDAG_LegalizeDAG.o.meta: > 15: file '/usr/local/etc/libmap.d/nvidia.conf' is newer than the target.= .. > = That does seem odd why anything involved in building clang should care about that file... You can use the pid field in the syscall trace to show what process was looking at that file. > This box has the following lines in /etc/src.conf to rebuild the nvidia = kernel module > every time: > = > PORTS_MODULES+=3D x11/nvidia-driver > = > I do not know what is going on here ... :-( well that might explain why nvidia.conf is updated, but not why clang build cares.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?25259.1494259448>