Date: Sat, 6 May 2017 09:22:55 +0200 From: "O. Hartmann" <ohartmann@walstatt.org> To: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: filemon: weird full-time build although filemon enabled Message-ID: <20170506092255.083828f8@thor.intern.walstatt.dynvpn.de>
next in thread | raw e-mail | index | archive | help
--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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170506092255.083828f8>