Buildworld times (was Re: svn commit: r350256 - in stable/12: . contrib/compiler-rt/lib/sanitizer_common contrib/libunwind/src contrib/llvm/lib/DebugInfo/DWARF contrib/llvm/lib/MC contrib/llvm/lib/Object contrib/llvm/lib/Ta...)

Dimitry Andric dim at FreeBSD.org
Mon Jul 29 17:17:14 UTC 2019


On 29 Jul 2019, at 03:07, Ed Maste <emaste at freebsd.org> wrote:
> 
> On Fri, 26 Jul 2019 at 22:44, Jeremy Chadwick via freebsd-stable
> <freebsd-stable at freebsd.org> wrote:
>> 
>> TL;DR for lazy folks:
>> 
>> stable/11 r350330 world + minimal clang = 1:29:34
>> stable/11 r350330 world + full clang    = 1:46:31
>> stable/11 r350252 world + minimal clang =   56:52
>> stable/11 r350252 world + full clang    = 1:14:30
> 
> Yes, because you're currently running r349226, and the world build
> thus first builds its own toolchain. Try the same experiment running
> on a r349226 or later installed world.

Indeed, that is the most likely explanation.  Unfortunately stable/11's
Makefile.inc1 does not explicitly show that it is going to bootstrap the
toolchain, like in head and stable/12, which show this right at the
start of buildworld:

--- buildworld ---
make[1]: "/usr/src/Makefile.inc1" line 349: SYSTEM_COMPILER: libclang will be built for bootstrapping a cross-compiler.
make[1]: "/usr/src/Makefile.inc1" line 354: SYSTEM_LINKER: libclang will be built for bootstrapping a cross-linker.
--- buildworld_prologue ---

Instead, you can only check for the *absence* of the following message:

"Determined that CC=xxx matches the source tree.  Not bootstrapping a cross-compiler."

-Dimitry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 223 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20190729/8aeb80b0/attachment.sig>


More information about the freebsd-stable mailing list