Re: Chromium and Iridium consistently not building for 123amd64 latest

Rene Ladan wrote:
> On Mon, Apr 18, 2022 at 11:38:36PM +0000, Pau Amma wrote:
> > On 2022-04-18 22:10, Mark Millard wrote:
> > > Looking at the log shows other failures during 97% :
> > 
> > [massive snip]
> > 
> > > I suspect that the rest of the time was its very slow scanning
> > > of the huge log file to report on the type of failure. This can
> > > take 2+ hours of itself before the actual kill happens.
> > > 
> > > As I remember, something like 34 hours is about the maximum
> > > time before the process is started that leads to killing a
> > > builder. So things can be odd if it fails when it has gotten
> > > sufficiently near that time frame.
> > 
> > That doesn't really help me figure out how to help either Iridium or 
> > Chromium (I don't need both, and if I get to choose, I'll choose 
> > Iridium) get a 123amd64 package.
> > 
> Perhaps it are buid timeouts causing this, it builds 12.3 builds fine
> in poudriere on my quadcore 2015 laptop (I tested the upcoming
> Chromium 101 on 12.3-i386 quarterly yesterday).

As a chrome package hasnt been available for my 12.2-STABLE for ages,
I just finished building chrome on 
  FreeBSD lapr.js.berklix.net 12.2-STABLE FreeBSD 12.2-STABLE #0
  stable/12-n233795-1f7da3e8965-dirty: Sat Sep 18 00:23:57 CEST
  2021
  jhs@lapr.js.berklix.net:/data/release/s2/usr/src/sys/amd64/compile/LAPR.small
  amd64

Took most of a week.  I was quite suprised when nothing broke.
Now I'm nursing through a make ALLOW_UNSUPPORTED_SYSTEM=YES package-recursive
(just mentioning in case anyone needs the packages)

then I'll do a backup & a src/ update & make world cos my src/ is v. old

Cheers,
-- 
Julian Stacey  http://berklix.com/jhs/ http://StolenVotes.UK  
Kill / remove Putin: He kills innocents & causes global grain & fuel shortage.