From owner-freebsd-current@freebsd.org Mon May 8 16:23:26 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ADD89D63269 for ; Mon, 8 May 2017 16:23:26 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E9D08AA5 for ; Mon, 8 May 2017 16:23:25 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id v48GNKoh037956 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 8 May 2017 19:23:20 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua v48GNKoh037956 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id v48GNKY2037955; Mon, 8 May 2017 19:23:20 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 8 May 2017 19:23:20 +0300 From: Konstantin Belousov To: "Simon J. Gerraty" Cc: "O. Hartmann" , FreeBSD CURRENT Subject: Re: filemon: weird full-time build although filemon enabled Message-ID: <20170508162320.GD1622@kib.kiev.ua> References: <20170506092255.083828f8@thor.intern.walstatt.dynvpn.de> <16322.1494224695@kaos.jnpr.net> <20170508173709.37e94b17@thor.intern.walstatt.dynvpn.de> <25259.1494259448@kaos.jnpr.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <25259.1494259448@kaos.jnpr.net> User-Agent: Mutt/1.8.2 (2017-04-18) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 May 2017 16:23:26 -0000 On Mon, May 08, 2017 at 09:04:08AM -0700, Simon J. Gerraty wrote: > O. Hartmann 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_CodeGen_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+= 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. If I understand the motto of meta-mode, any file change is detected for any file accessed during the build. All dynamically-linked binary includes the rtld into the process image, and rtld reads all config files in the libmap.d subdirectories. The end result is that everything must be rebuild if any config file changed. Then, after the world build, according to OP, the nvidia driver port is reinstalled, which installs the nvidia.conf anew, which triggers the behaviour on the next build.