Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 9 Sep 2024 15:18:09 -0700
From:      Kevin Oberman <rkoberman@gmail.com>
To:        freebsd-questions@freebsd.org
Subject:   Re: building a 14.1 workstation
Message-ID:  <CAN6yY1tHZ4z5HP01yS6bkh=ND7t9k-pSi_U41r71A%2Bz2GFbRog@mail.gmail.com>
In-Reply-To: <20240908134405694174552@bob.proulx.com>
References:  <alpine.BSF.2.00.2409061435240.55623@bucksport.safeport.com> <20240908134405694174552@bob.proulx.com>

next in thread | previous in thread | raw e-mail | index | archive | help

[-- Attachment #1 --]
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

[-- Attachment #2 --]
<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small">On Sun, Sep 8, 2024 at 1:01 PM Bob Proulx &lt;<a href="mailto:bob@proulx.com">bob@proulx.com</a>&gt; wrote:</div></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Doug Denault wrote:<br>
&gt; Not to bury the headline I can not build a 14.1 workstation and can not<br>
&gt; believe I am the only one, but have seen nothing on this list.<br>
&gt;<br>
&gt;    1. Installing from pkg<br>
&gt;       This installs 384 packages with the following problems:<br>
&gt;          * there is no chromium<br>
&gt;          * firefox will not run, ending with an error loading a dynamic<br>
&gt;            library<br>
<br>
This is a routine problem every time a point release happens.  I see<br>
this routinely and it is routinely reported in the IRC channels.  At<br>
the time of a point release the auto-builders start building the<br>
latest commit of all ports.<br>
<br>
There might be failures due to the upgrades.  Recently x265 failed to<br>
build.  This causes a lot of dependent packages to be skipped in the<br>
build cycle.  Everything dependent upon it is then skipped.  Including<br>
firefox and chromium.<br>
<br>
The build might take several days to complete.  The result is that the<br>
pkg repositories both current and quarterly might be missing major<br>
cones of dependent packages such as recently both firefox and chromium<br>
were unavailable for several days.</blockquote><div style="font-family:tahoma,sans-serif;font-size:small" class="gmail_default"></div><div style="font-family:tahoma,sans-serif;font-size:small" class="gmail_default">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 &quot;latest&quot;, I have no idea of the status of the quarterly builders. <br></div><div style="font-family:tahoma,sans-serif;font-size:small" class="gmail_default"><br></div><div style="font-family:tahoma,sans-serif;font-size:small" class="gmail_default">Some time I want to walk through all of the build systems and see how many hare running on new metal. Unfortunately, <a href="http://pkg-status.freebsd.org">pkg-status.freebsd.org</a>; still is not talking to the new systems.<br></div></div><br clear="all"><br><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Kevin Oberman, Part time kid herder and retired Network Engineer<br>E-mail: <a href="mailto:rkoberman@gmail.com" target="_blank">rkoberman@gmail.com</a><br></div><div>PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683</div></div></div></div></div></div></div></div></div>

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1tHZ4z5HP01yS6bkh=ND7t9k-pSi_U41r71A%2Bz2GFbRog>