Date: Sun, 21 Mar 2021 09:49:57 -0700 From: Mark Millard <marklmi@yahoo.com> To: tech-lists <tech-lists@zyxst.net> Cc: freebsd-arm@freebsd.org Subject: Re: RPI4 clock speeds and serial port Message-ID: <BEE931BC-3DDC-4DBD-B247-1B09DD598F81@yahoo.com> In-Reply-To: <YFdPNiHX%2BUCU5R%2BM@ceres.zyxst.net> References: <20210318170053.GA26688@www.zefox.net> <9FFA0A51-C0B7-4121-95CA-B98669809007@yahoo.com> <E4CF6642-CB70-4495-A865-05469953561C@yahoo.com> <YFaGFEXGUCigAJXD@ceres.zyxst.net> <C0FAA127-05CE-43E5-A7D5-B5EB975E7B4F@yahoo.com> <YFdPNiHX%2BUCU5R%2BM@ceres.zyxst.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2021-Mar-21, at 06:50, tech-lists <tech-lists@zyxst.net> wrote: > On Sat, Mar 20, 2021 at 04:55:47PM -0700, Mark Millard wrote: >=20 >> To me the wording is unclear on an important >> point: >>=20 >> Was this a rebuild after installing and booting >> the kernel and world that had been built with >> those flags? Or was this running the as yet >> not updated system and just doing the initial >> build with the -mcpu assignments? >=20 > 1. cd /usr/src && git pull --ff-only > 2. added those .clang statements to /etc/src.conf > 3. it had already built world & kernel with the other WITHOUT_xyz = statements in days previously >=20 > this was the first time i'd tried those -mcpu assignments. >=20 > I'll try building again, this time noting exactly what's done. >=20 >> CCACHE status? >=20 > enabled. I almost always use ccache as the buildtime impact is = substantial with any c/c++ program. poudriere uses it if it's available > for this reason. = https://docs.freebsd.org/en_US.ISO8859-1/books/handbook/ports-poudriere.ht= ml reports: QUOTE Defining CCACHE_DIR enables the use of devel/ccache to cache compilation = and reduce build times for frequently-compiled code. END QUOTE and: # grep -r CCACHE_DIR /usr/local/etc/poudriere.conf.sample /usr/local/etc/poudriere.conf.sample:#CCACHE_DIR=3D/var/cache/ccache /usr/local/etc/poudriere.conf.sample:# Default: yes, unless CCACHE_DIR = is set and CCACHE_DIR_NON_ROOT_SAFE is not /usr/local/etc/poudriere.conf.sample:# use a non-shared CCACHE_DIR that = is only built by PORTBUILD_USER and chowned /usr/local/etc/poudriere.conf.sample:# to that user. Then set = CCACHE_DIR_NON_ROOT_SAFE to yes. So it looks like use of ccache must be explicitly enabled in poudriere-devel . Mere installing of devel/cache and then using poudreire bulk does not seem to use ccache. (There also seems to be CCACHE_STATIC_PREFIX and CCACHE_DIR_NON_ROOT_SAFE that can be set as well.) At least for figuring out what buildworld buildkernel installs lead to taking less time vs. more time and how much less/more for later build activity, having differences in what has been cached by ccache also involved makes time comparisons untenable. Of course, going the other way, holding the system installation constant and doing various without and with ccache timings for repeatable sequences of updates can be used to get an idea of how much ccache can help. I happen to not have done such testing. >> Was this caching effectively cleaned-out/empty >> for the timing? >=20 > I don't know. All I know is that it looks after itself. I'll > disable/clear out ccache [1] if changing major freebsd versions [2], = or tracking down a problem with a program building. >=20 > I'm surprised you don't usually use it >=20 > [1] rm -rf /var/cache/ccache/* > [2] also rm -rf /usr/obj and re-make it again =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BEE931BC-3DDC-4DBD-B247-1B09DD598F81>