From owner-freebsd-current@freebsd.org Sat May 6 07:23:12 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 D839FD6059A for ; Sat, 6 May 2017 07:23:12 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (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 59EB6DFF for ; Sat, 6 May 2017 07:23:11 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([78.52.9.80]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MGEv5-1dJEOl06jv-00FBwO for ; Sat, 06 May 2017 09:23:04 +0200 Date: Sat, 6 May 2017 09:22:55 +0200 From: "O. Hartmann" To: FreeBSD CURRENT Subject: filemon: weird full-time build although filemon enabled Message-ID: <20170506092255.083828f8@thor.intern.walstatt.dynvpn.de> 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_/9J_=qNI8RJioVhIfM/fyoHl"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:4BoPqNfUg22JdxZKdHnUiVhA+NmW1V4G7fsf31P4JS829uYSvaL wPxRfVCAfrEcVFtdxSvn8TC2ynV6c9hwj8rI6M2tiles92kz42W/CRR87Wgl1QhiB2O4pXs V0HtHFY9aWRg9lnVdcGIm02exi1dB+MJ4h4LZ8DZ8PXGhrmmTaSH4FzMCThhAdCshZmS26b pyXuIhvZYH57nba8C7bYw== X-UI-Out-Filterresults: notjunk:1;V01:K0:M3IpgT3XcVQ=:6bFjJOrblHWGiJWb16gTUx DpAQ5uZPlmvjMhTtg9QHnZNXbo4LxzjK/r6vJVhqDn8ZdbysAX/fapOwFAhaBoy78nxGSXamx /6Lj7/YTUqfbmcnm5I05Wca2be6wdZjuualN49OFLwcN8gAVLxyAJixKX3Rh5DqY+mB4vzSxV KuqPoEew/h7/1mihu/bSGxkS8eYP0MqANjte99x3CwdUH8p7ew1yYzH31DXhYc+IRRFLtqfi6 DtaAbY+uZV99G8HtFajBQ2a1kEMN4dVs+1BgU3rnUu1nIN6aj2/bmPpucF3ZB9LcdV4TuxFLC wQfOv0wrDKQbOwEiBimmpMV5M99D3KpF/DdWyMP4g5gXIH88WBFrJe98WGY/A2Xk1Rf0b8qTj M2/Op0YZnWJ5XjoVvVtka3U6oFv2WKTy+rBOxAqqDBnqNOD7OFq9LeRAqpP27d60WjIJB2Vhm 7UCrdxvBhEeF8GrsKtUK6OK65KIrk8zk38BiErLcVAywWjDDdNfaz/Nu6OruhbEWvLX7iYtPf z2SKY5L3eybZ1IKW6hPs+OrTIusgUX1ug1GVAvaulR9jRat9LY1s79zK6WW1CCZMEo3rckLF7 ExC7wbPFjTgSzmxcbXB5X/danfsDpf/4XVK8n/CafTyoIYPSJra+F3aAsxl1Ao8+IbH94drlL /3Nq1bglebBLYPSpXmDt9E6BGHzwQ66N7fG45a5+acruC4CHweCzfiDZgAHYWV1Df79gP4vsG gAK8N+OFKtoSp6QG+rfxbQOqX4SQOF0jRStGHoTD7v2CHGsWoTqy5lLWpWg= 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: Sat, 06 May 2017 07:23:13 -0000 --Sig_/9J_=qNI8RJioVhIfM/fyoHl Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I build CURRENT on two technically similar systems on a almost daily basis.= Therefore, it was a great relief having WITH_META_MODE=3Dyes set in /etc/src-env.conf for= incremental builds. To make my understanding of this clear (just in case I'm wrong): se= tting WITH_META_MODE builds only portions that does not need to be build in the m= ake context. Well, the reason writing this email is: on one system, I run almost every r= eboot into a "full build" and this puzzles me a bit. The long-lasting and time exhaustin= g 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 same motherboard, al= so a SSD, but has 16 GB RAM and a 4-core/8 threads XEON CPU - but both are "IvyBridge". T= he XEON usually needs 30 - 40 minutes to compile a full world/kernel from a clean /= usr/obj, the "weak" box takes approximately 120 minutes - it is understandable that a sh= ortage of the build time is appreciated. 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 WIT= H_ tags. In fact, they are identical except the KERNCONF (naming of the kernel) and POR= TS_MODULES=3D, the "weak" box incorporates x11/nvidia-driver and emulators/virtualbox-ose-= kmod, so these modules are build every time the system gets rebuild, but the time taken by= those is negligible. The problem: to make my point clear: the "weak" box starts compiling almost= everytime now the LLVM/CLANG tree while the XEON box does not. This is spooky. I deleted on both systems recently /usr/obj completely from its content an= d restarted a buildworld again to hope, that the problem was introduced due to some files necessary for the BSD make environment to indicate the incremental build. B= ut no success. Even more spooky is the fact, that after a build on the "weak" box and a bu= ild again, the box bevaves as expected not rebuilding everything again, but in some cases = after a reboot, a rebuild the hits again the build of LLVM/CLANG tree, while the XE= ON box does not. I think there is something missing an I'd like to ask what is the suggested= way to initially restart a full build to ensure that WITH_META_MODE gets initialis= ed correctly. Well, I'm not a developer, so please be patient with my naive report. Thanks in advance, oh --=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_/9J_=qNI8RJioVhIfM/fyoHl Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWQ15zwAKCRDS528fyFhY lNYvAgCaD2n+iXxVq/ul/WKGHeI3p/00HXfttEJ3zJujP3HEARdHjXKX8f7XeGyW Ku8M+x8Ih0RJOdeiIi0q9NLgYu4nAf957MiLjuPJJ4Z0g3DppX8AEzAK/RkXaKPT CNp/JtS1icp9ubf6AUso7RKSAJAV9klRyr3d+RHtS4eRVI5Us7ZD =SROU -----END PGP SIGNATURE----- --Sig_/9J_=qNI8RJioVhIfM/fyoHl--