Re: building a 14.1 workstation

From: Kevin Oberman <rkoberman_at_gmail.com>
Date: Mon, 09 Sep 2024 22:18:09 UTC
On Sun, Sep 8, 2024 at 1:01 PM Bob Proulx <bob@proulx.com> wrote:

> Doug Denault wrote:
> > Not to bury the headline I can not build a 14.1 workstation and can not
> > believe I am the only one, but have seen nothing on this list.
> >
> >    1. Installing from pkg
> >       This installs 384 packages with the following problems:
> >          * there is no chromium
> >          * firefox will not run, ending with an error loading a dynamic
> >            library
>
> This is a routine problem every time a point release happens.  I see
> this routinely and it is routinely reported in the IRC channels.  At
> the time of a point release the auto-builders start building the
> latest commit of all ports.
>
> There might be failures due to the upgrades.  Recently x265 failed to
> build.  This causes a lot of dependent packages to be skipped in the
> build cycle.  Everything dependent upon it is then skipped.  Including
> firefox and chromium.
>
> The build might take several days to complete.  The result is that the
> pkg repositories both current and quarterly might be missing major
> cones of dependent packages such as recently both firefox and chromium
> were unavailable for several days.

This is no longer the case for 14 for amd64 systems. The 140amd64 build
system can now do a full build of packages in about 34 hours, well under 2
days, and most smaller builds run in a few hours. They do 42 parallel
builds. This is a huge improvement and, I believe, that other build systems
will be replaced over the next months to get similar performance. Since I
have always used "latest", I have no idea of the status of the quarterly
builders.

Some time I want to walk through all of the build systems and see how many
hare running on new metal. Unfortunately, pkg-status.freebsd.org still is
not talking to the new systems.


-- 
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkoberman@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683