From owner-freebsd-current@freebsd.org Mon May 8 15:37:24 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 E72CFD62A83 for ; Mon, 8 May 2017 15:37:24 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 547E1989 for ; Mon, 8 May 2017 15:37:23 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([78.52.143.39]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0M4GRv-1dzJBG0D6R-00rl4H; Mon, 08 May 2017 17:37:17 +0200 Date: Mon, 8 May 2017 17:37:09 +0200 From: "O. Hartmann" To: "Simon J. Gerraty" Cc: "O. Hartmann" , FreeBSD CURRENT Subject: Re: filemon: weird full-time build although filemon enabled Message-ID: <20170508173709.37e94b17@thor.intern.walstatt.dynvpn.de> In-Reply-To: <16322.1494224695@kaos.jnpr.net> References: <20170506092255.083828f8@thor.intern.walstatt.dynvpn.de> <16322.1494224695@kaos.jnpr.net> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/ycOAhHP0bxIzVzy19BTU.Ew"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:XWbhoTViGbW6fxUbxrtN90gTZKVxXWSWXuMI+oQPsdq36vqn3gw vcoufn4Diecd0tH2OFKh6II3PvGygmxF3eqp/oGEYU8MS/qbckXuzuAXTAyRAIhhlNuinzU XD52CndNEaufC8Bi5G0SLs76+xSyfDuGhqY/RTDbKkPgHFi7MWcXSW6uwVgUVuaABDbT6A2 mLroM+dYbuxSt83Rl8scA== X-UI-Out-Filterresults: notjunk:1;V01:K0:Z+PUeBwozMw=:G4int0O5qzsCaTgurqxmIq Txub0aqx/3T/kJ3IcnYoyxfEqX85xcMTAZNy0fXo3rbI1ijWMs0Zmxk5rzZq9PJYRznnMbUzD 5VsoVwX6e5Ue2Vge04l+jHPgfvPBhBF8LrVrfEbf6rEl+VQvIdl9YNB/18mc4CPyPKl60h40W U9aKO1MC3pvX3tBhu2QmyuG//+tFrHrgecJdy3kHZrr7VXHByOd3G4kzz2wbGn9PX8C279u6S sHxriwLbJdu8mpvGbBpm9nHNQC+K23dHu0x9jiq0qQSSJ2IB6gXKv5hAx5nVOnoJcDrhYoBTR GloMysrop7bVBNssOHBI9sGpkX3on+wjPtu6e0K8gS97Xbl+ircB/RGgXM/d/fzjwGPPRoVL8 qHPnZH+LNzG3gYBqT4CpcYluyu/nYBClJKkBNPNgIqv86KKC2GL/VUAc8wJP9hrz80V4VTKMc w65pKNDAHfnqlK3q4Mw0qUEQbrAc9kcQ7KT2JZ+mpcIcpHWf2QVHpVbSto/dJX3mKCrr/EDlj jGYSttYjWgZ8KJhUOYGWnxhubLHTlfCbFcbnNHtZWu30urbnlm5dCO/FFqfXGnFizCvjhztuS rgcSGb05BLR3/aCRn6wM1SZnILO4iE1Ha7lNSaQGKAah+n8VsN6c2hkyGAUVQKc8GskgXT5ya bxvSf/BJBWUTrhEv/01pf/pn0BQuEF8DY2/eAIsrMBsI7xnn3YjOgmNewXsD3MZ8BarlPrOeB 6rDIdqTqChlZh80mNFDRqv3PuHrTl42djqxvJ0t7CXv8c89usinJ9JXhHyY= 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 15:37:25 -0000 --Sig_/ycOAhHP0bxIzVzy19BTU.Ew Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Sun, 7 May 2017 23:24:55 -0700 "Simon J. Gerraty" schrieb: > Hi, >=20 > > I build CURRENT on two technically similar systems on a almost daily ba= sis. > > Therefore, it was a great relief having WITH_META_MODE=3Dyes set in /et= c/src-env.conf > > for incremental builds. To make my understanding of this clear (just in= case I'm > > wrong): setting WITH_META_MODE builds only portions that does not need = to be build in > > the make context. =20 >=20 > I'm not sure I parsed that correctly, so let me just say; > With MK_META_MODE=3Dyes, bmake should be put into meta mode. >=20 > This simply means that most targets get a .meta file, that records the > expanded command line, any command output and a syscall trace. > These can be very useful for debugging. >=20 > More important; on an update build bmake can use them to make targets > out-of-date that the normal rules miss. > Any change to the expanded command line, makes the target out-of-date. > Any change to any file read or executed makes the target out-of-date. > =20 > > Well, the reason writing this email is: on one system, I run almost eve= ry reboot into > > a "full build" and this puzzles me a bit. The long-lasting and time exh= austing builds > > are =20 >=20 > You can add -dM to your build flags to have meta_oodate() - the function > that does the above, explain why it decided the target is out-of-date. > The results can be enlightening. >=20 > Note, if a target rebuilds without -dM saying why - then the normal make > rules decided it was out-of-date. >=20 > > within the LLVM/CLANG tree. They consume a lot of time. The box in > > question does have a =20 >=20 > Yes, building clang takes a while... >=20 > > Well, having said this, I need to mention that both systems use almost > > identical /etc/src.conf setting - except the order of appearance of > > the WITH_ tags. =20 >=20 > That should not matter, bsd.mkopt.mk processes them in a specified > order. >=20 > > The problem: to make my point clear: the "weak" box starts compiling al= most everytime > > now the LLVM/CLANG tree while the XEON box does not. This is spooky. =20 >=20 > Add -dM, and see if that tells you why. > Also confirm that filemon is getting loaded after each reboot. > If that comes and goes, that could cause the behavior you see. >=20 > > I think there is something missing an I'd like to ask what is the sugge= sted way to > > initially restart a full build to ensure that WITH_META_MODE gets initi= alised > > correctly. =20 >=20 > I think Bryan has set that up so that it should take care of itself > pretty well - even toggling bewteen non-meta and meta builds should > DTRT - which is why it matters if filemon was used that it is there for > next build. >=20 > > Well, I'm not a developer, so please be patient with my naive report. = =20 >=20 > No problem. Adding -dM to your build (will add a fair bit of output), > will hopefully tell you what's up. >=20 > From what you describe, I'd not be surprised if you see some > "a build command has changed" and it only takes a few to trigger a > cascade of targets out-of-date. >=20 > --sjg >=20 It is weird! Today, after yesterday's built, I face the same 90 minutes build horror aga= in, 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_CodeG= en_SelectionDAG_LegalizeDAG.o.meta: 15: file '/usr/local/etc/libmap.d/nvidia.conf' is newer than the target... This box has the following lines in /etc/src.conf to rebuild the nvidia ker= nel module every time: PORTS_MODULES+=3D x11/nvidia-driver I do not know what is going on here ... :-( --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/ycOAhHP0bxIzVzy19BTU.Ew Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWRCQpQAKCRDS528fyFhY lNzxAgCJOvdwMaXet8qCsgeHjq1/yUG4oqJDdbka6r5+RWB4qhkPVjqTP7MS+tTb KDJZJnRXetHKFTLO2J9MBsS1gzOtAgCbR7xC0479TaFwok7l+rijMvNrODDkpJKu zkO8OJPOg/HAo2Q+trR/DsAFYnZ/ttGIV6aSpEsga6RD7LkGbP2z =5yNs -----END PGP SIGNATURE----- --Sig_/ycOAhHP0bxIzVzy19BTU.Ew--