From owner-freebsd-current@freebsd.org Mon May 8 18:25:57 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 8C32FD636A0 for ; Mon, 8 May 2017 18:25:57 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (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 0CBD61B2B for ; Mon, 8 May 2017 18:25:56 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([78.52.143.39]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MXIov-1dVBvC2syb-00WGv0; Mon, 08 May 2017 20:25:47 +0200 Date: Mon, 8 May 2017 20:25:40 +0200 From: "O. Hartmann" To: "Ngie Cooper (yaneurabeya)" Cc: "O. Hartmann" , FreeBSD CURRENT Subject: Re: filemon: weird full-time build although filemon enabled Message-ID: <20170508202540.470321ac@thor.intern.walstatt.dynvpn.de> In-Reply-To: <557CD2F0-4E32-41EE-A0A9-DF5D8C189E83@gmail.com> References: <20170506092255.083828f8@thor.intern.walstatt.dynvpn.de> <557CD2F0-4E32-41EE-A0A9-DF5D8C189E83@gmail.com> 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_/1LSrqTgbT5Mm=BYg/+COrSu"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:5MGxLkLBXbv902wAUMx7geVoCLfAeFot6IGkBzbUMRy2xDNS4PA kpJfIZwsPH4t74zUfd7bijDxHOifd7ZxGKiHn38X+kul4Rg/FTvN5L2UhIM9yeMi1Rhk4UL ZG5XtPQEFdNxh2Kwcos7PtrRNi0t+Gtq91qkNsL6m6rX3rIxgQRPWfMXbwf1nYxNPVdt2Y5 yWSvyTzvrxlW9wT1vBcSw== X-UI-Out-Filterresults: notjunk:1;V01:K0:26TU0hFV29s=:EjKQBd2qYQBmU+3seM2EB2 pOa5lAjPDEd71KgZeSM03v3Z6d+XPP/AZLpg+XRH0KX8l3j82LbljNbHBFZXdMNHXoZd7u63M C16tyEWKARExTjAwyyYLi8+n/77iVd2sfCXFdLAy2GiOoZS9dxIaECBUngzf+EbVkirc49rdU VwqllJM5xEEZ0ta1MFFc8oNbdtAJcyUwXuIIdTZAtQq55WsoyJ99SrdklMfeljtjXrSGHiMqa MEk23EPfDsvqEXNP/iZar8pVSEP+2WBnIgmP1l3yXkfdVaNVlqA3I7CsKTGSH3kFW63+ZIwoJ t6Q0jv0kPIXu4oJq9KJg5+k/HS9TF9VrokL5EH8IVenRua7f8kl8QC2r/MWsXjMpCLrO6k2I4 0DKBdq1357pm3hgHFvrze2A6CNVrsO/hTrDR4rIr0VZE8iTG9nDTwrosDtsnNX22UPW/x5JK+ pcEwkKNQ4RcKZJ+xeAdfo9tXs7hCDQYo0s5fCB2xseXtqONt+IgolDSE/EY1PF9JrMJuvZxd/ T9wbzqch4aI279KdHtZXdfoJCxb7x4NRWUJSZiaNsyNi6kRI3GwdZZI2iLCAeEOG3NjeK7SSw k3SpsPklQzYCWdQVlOONu9pUhLDpn/jytFYTFfrCHX+OboAyx/dYpVbWZTSxfOBFxpqW5isrH vdb9T9aQarREYGKBDQMZNcOC2WHSWo+FzaZUgemmfMNkPPok+J7psRuhEphdIUoHrzFVMc+w1 iXE7i7UUO4pILZYV5ggp2B8vty6nekf08iGg2Lo34WLP+XJlhJO/n0W7W/s= 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 18:25:57 -0000 --Sig_/1LSrqTgbT5Mm=BYg/+COrSu Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Mon, 8 May 2017 11:23:01 -0700 "Ngie Cooper (yaneurabeya)" schrieb: > > On May 6, 2017, at 00:22, O. Hartmann wrote: > >=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 > > 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 within the LLVM/CLANG tree. They consume a lot of time. The box in = question does > > have a weak CPU, only two physical cores, four threads, 8GB of RAM and = builds > > the /usr/obj residing on a SSD. The reference machine does have the sam= e motherboard, > > also a SSD, but has 16 GB RAM and a 4-core/8 threads XEON CPU - but bot= h are > > "IvyBridge". The XEON usually needs 30 - 40 minutes to compile a full w= orld/kernel > > from a clean /usr/obj, the "weak" box takes approximately 120 minutes -= it is > > understandable that a shortage of the build time is appreciated. > >=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. In > > fact, they are identical except the KERNCONF (naming of the kernel) and > > PORTS_MODULES=3D, the "weak" box incorporates x11/nvidia-driver and > > emulators/virtualbox-ose-kmod, so these modules are build every time th= e system gets > > rebuild, but the time taken by those is negligible. > >=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 > > I deleted on both systems recently /usr/obj completely from its conten= t and > > restarted a buildworld again to hope, that the problem was introduced d= ue to some > > files necessary for the BSD make environment to indicate the incrementa= l build. But > > no success. Even more spooky is the fact, that after a build on the "we= ak" box and a > > build again, the box bevaves as expected not rebuilding everything agai= n, but in some > > cases after a reboot, a rebuild the hits again the build of LLVM/CLANG = tree, while > > the XEON box does not. > >=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 > > Well, I'm not a developer, so please be patient with my naive report. > >=20 > > Thanks in advance, =20 >=20 > Dumb question: which kernel are you using on which machine (GENERIC, > GENERIC-NODEBUG, a custom kernel with or without debug hooks, e.g., INVAR= IANTS, > enabled)? Also, how are you building the system (locally using UFS or ZFS= , remotely, > e.g., over NFS, etc)? Thanks, -Ngie - Custom kernel - as far as I know, no debug hooks, no INVARIANTS (i tried to eliminate all= of them) - Build is performed on a Samsung SSD 850 PRO with UFS2, locally --=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_/1LSrqTgbT5Mm=BYg/+COrSu Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWRC4JAAKCRDS528fyFhY lOoOAf0fDa2HjHvxsiQGPI/qf/pIqqM6yUC9oTOQuuJxd69NuZ4sc49qSa5n+lKI r1+HXi59UM3KxwQHneCpSHEtLcePAf9Jx9Z+1kkHSIWPHQcEzFtczdTqQ9MXOiqH 2WZMrcskK5TbGGNiX0OlRQn4AX3Dfx3wMHZtfVVitVRngIEzA8yi =ktkP -----END PGP SIGNATURE----- --Sig_/1LSrqTgbT5Mm=BYg/+COrSu--