Date: Wed, 1 Apr 2026 11:34:39 -0700 From: bob prohaska <fbsd@www.zefox.net> To: Mark Millard <marklmi@yahoo.com> Cc: freebsd-current@freebsd.org Subject: Re: Etcupdate runtime has more than doubled....Why? Message-ID: <ac1lP2IqDJgiqHx4@www.zefox.net> In-Reply-To: <626584dc-ea9c-4a63-902c-4de4e10bba00@yahoo.com> References: <ac1SLQ4rS9tScr5-@www.zefox.net> <626584dc-ea9c-4a63-902c-4de4e10bba00@yahoo.com>
index | next in thread | previous in thread | raw e-mail
On Wed, Apr 01, 2026 at 11:00:56AM -0700, Mark Millard wrote: > > > > etcupdate has the option: > > > -B Do not build generated files in a private object tree. > Instead, reuse the generated files from a previously built > object tree that matches the source tree. This can be > useful to avoid gratuitous conflicts in sendmail(8) > configuration files when bootstrapping. It can also be > useful for building a tarball that matches a specific > world build. > > > So, if one already has the required context, its use might be relevant. > Of course, without the proper context, it should not be used. > > What was the context-status and use vs. not for -B ? There's only one /usr/obj on the system. The buildworld command used was make -j3 KERNCONF=GENERIC TARGET=arm TARGET_ARCH=armv7 buildworld and the etcupdate command following buildworld was etcupdate -p After installing world and kernel, etcupdate runs again as etcupdate Might using etcupdate -B in the second invocation be a remedy? Thanks for writing! bob prohaskahome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ac1lP2IqDJgiqHx4>