From nobody Tue May 30 08:39:42 2023 X-Original-To: freebsd-ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QVm6f6t0Mz4Y6M0; Tue, 30 May 2023 08:39:54 +0000 (UTC) (envelope-from eduardo@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QVm6f6KnPz3lrn; Tue, 30 May 2023 08:39:54 +0000 (UTC) (envelope-from eduardo@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1685435994; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=yReF5NJgkqdGLeYzBtHDC9raJSkmqkzpBYcNqwCTJHs=; b=jM3kZBhWMzrTkTwr/O8oJicYLOD72U6C4RRMyKnkCAFNnEVB4S6uQlC8yih6BgB+zgYKDw +aIpoqWgyPtpRr7EbDuMPKXPRWr3bOg8FjKibr2uYGo/FYQCILxYP71zQUfzxl0s+QTt7O zF0AdIBONMtoZzupv16vikTkpHv0tR9SgPRE4BWHCcG/MMZqSexm8Qa5qSVy6xmaZKRRb5 0DFTV3MgtYAsIKlhUXRcpKMWYgYbzSiosXKteAoNE4zn0gFmDAH9gC0YSAMiSW51R3pOVq EfuAS23MWXNwMBI6q6hK4yAp/x3yniHZvpEAOEM0mtbVT5uJa6jzHuo2Yd9xfQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1685435994; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=yReF5NJgkqdGLeYzBtHDC9raJSkmqkzpBYcNqwCTJHs=; b=Uk1Ok4QPo+NQZJj8TqDzK7aql/aAezavRC0lXxGd1J8NegV5+BM/VG5agYqH3hMbdwGyA9 NZkvcmyyJ36aiOp8QxqMZOKsm46EuSRVCPlKaj/hjVs0TKVPIFlkVL73nrlSKilPDX8Q3J m+q/sEdpopYIFomdR6AktvT5q3ocWvgVUzZVq464oD5l1az8XunTrAgAgVJvpSWhLwFGH6 aUMAB3TqdnUG7daajYOm4nO/LOsDusimTh7BpPhtCbqH+BKIajdCdhSpLNairj7fA6lWjY LR9oFVwBwlsbfAXeRUI46nlFh7hbjHvdQwt5iBjoSmU31YkRFo1Ryd85izXKSg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1685435994; a=rsa-sha256; cv=none; b=rasO9U29GFlstwj94Ff71g6P7Vf/J8ciMpBwsjEG5erUiEAbi9x2sR3pGoxsCB58baECd0 KtfQkwfeBBi89i/DmyBUiJ2y5lbk/qegnDM8w6cDiLIHSHgrz9R6edhN75EDQtrB+1wuy/ F0bgKx06zhcMoUOT/1s8cuyfnh3jaR8zxzTLhNPxI6CkhFzTeZLLNuW5xh49MV0JIAkMbO fF8yMMzQ/oGIk6xcIDxWonnituE2vH2Uf02YJL2a6Fj9+r06TlB6r/d19yimWdUSqNw4b0 17WapQ7VLOT41srxq1HLOaiSaUneyd+yCPdQbdfS0IxFHD7Z8FfvpdC6mdmepw== Received: from mail-pl1-f175.google.com (mail-pl1-f175.google.com [209.85.214.175]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) (Authenticated sender: eduardo) by smtp.freebsd.org (Postfix) with ESMTPSA id 4QVm6f5C6TzYZV; Tue, 30 May 2023 08:39:54 +0000 (UTC) (envelope-from eduardo@freebsd.org) Received: by mail-pl1-f175.google.com with SMTP id d9443c01a7336-1ae3fe67980so37255775ad.3; Tue, 30 May 2023 01:39:54 -0700 (PDT) X-Gm-Message-State: AC+VfDz6qEcYk6oEK8JtU62MFehJU+1t4SlD+zZmhBVutPBDPH0oGscm ydQWTHYjl5Vt9JsKO/LwgTq61AP2D3pcYRGG/gM= X-Google-Smtp-Source: ACHHUZ691y63GIglPiJkBYmbeXBjUtb1Jyf1CH2NCU4oRBhFc2rvty74xxzRuBGyS0MkMzj4H+mEee+ndVXmnqNawPI= X-Received: by 2002:a17:902:aa86:b0:1b0:2d08:eb51 with SMTP id d6-20020a170902aa8600b001b02d08eb51mr1671312plr.12.1685435993596; Tue, 30 May 2023 01:39:53 -0700 (PDT) List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 References: <1623315797.5.1684837400228@mailrelay> In-Reply-To: <1623315797.5.1684837400228@mailrelay> From: Nuno Teixeira Date: Tue, 30 May 2023 09:39:42 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Improving www/chromium build time on arm64 To: Ronald Klop Cc: FreeBSD Mailing List , freebsd-arm@freebsd.org Content-Type: multipart/alternative; boundary="000000000000b0a90f05fce52503" X-ThisMailContainsUnwantedMimeParts: N --000000000000b0a90f05fce52503 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello Ronald and all! Finally I build it after 57 hours @ 2000MHz !!! Configs, photos and log at: https://people.freebsd.org/~eduardo/logs/chromium/ I'm running it right now and it runs very smooth! Next step will be compiling with LTO to check compile time and do some comparisons on binary size and run performance. Should I bother with LTO? Will it add performance? Thanks all! Ronald Klop escreveu no dia ter=C3=A7a, 23/05/2023 = =C3=A0(s) 11:23: > =C3=82 > > *Van:* Nuno Teixeira > *Datum:* dinsdag, 23 mei 2023 09:48 > *Aan:* FreeBSD Mailing List , > freebsd-arm@freebsd.org > *Onderwerp:* Re: Improving www/chromium build time on arm64 > > (...) > =C3=82 > But I also found that poudriere: > [88:53:28] Failed ports: www/chromium:build/timeout > =C3=82 > So I will search how do I increase build time to avoid timeout: > --- > # This defines the max time (in seconds) that a command may run for a bui= ld > # before it is killed for taking too long. Default: 86400 > #MAX_EXECUTION_TIME=3D86400 > --- > =C3=82 > I suspect it can be the cause of build failure because build >24h. > =C3=82 > Nuno Teixeira escreveu no dia ter=C3=83=C2=A7a, 23/= 05/2023 > =C3=83 (s) 08:31: > >> Hello all, >> =C3=82 >> I'm running 13-STABLE on rpi4 8 and since firefox{-esr} is constantly ta= b >> crashing and seg faulting I decided to give chromium a try. >> chromium pkg isn't available for arm64 and I didn't found error log at >> https://pkg-status.freebsd.org/ so I decided to build it on poudriere. >> =C3=82 >> It fails to build around 70% but my biggest concern is build time: 27 >> hours for 70% compilation! >> =C3=82 >> Just for comparison: >> llvm15: 12h >> rust: 9h >> firefox: 6h >> =C3=82 >> rip4 v1.5 8GB @ 2000Hz ~62 Celsius >> zfs >> poudriere: >> USE_TMPFS=3Dno >> PARALLEL_JOBS=3D1 >> ALLOW_MAKE_JOBS=3Dyes >> =C3=82 >> Any hints on how to speed build? ccache? >> Does cflags "-O -pipe" not present in compilation is related to build >> time? >> =C3=82 >> Full log: >> >> https://people.freebsd.org/~eduardo/logs/chromium/chromium-113.0.5672.12= 6.log >> =C3=82 >> Thanks! >> =C3=82 >> --- >> >> In file included from ../../base/check.h:11: >> ../../base/compiler_specific.h:8:10: fatal error: 'build/build_config.h' >> file not found >> #include "build/build_config.h" >> ^~~~~~~~~~~~~~~~~~~~~~ >> 1 error generated. >> ninja: build stopped: subcommand failed. >> =3D=3D=3D> Compilation failed unexpectedly. >> Try to set MAKE_JOBS_UNSAFE=3Dyes and rebuild before reporting the failu= re >> to >> the maintainer. >> *** Error code 1 >> >> Stop. >> make: stopped in /usr/ports/www/chromium >> build of www/chromium | chromium-113.0.5672.126 ended at Tue May 23 >> 02:22:56 WEST 2023 >> build time: 27:15:37 >> !!! build failure encountered !!! >> --- >> -- >> Nuno Teixeira >> FreeBSD Committer (ports) >> > > =C3=82 > -- > Nuno Teixeira > FreeBSD Committer (ports) > > > > Hi, > > My poudriere.conf for building ports on rpi4 contains these two changes: > > # This defines the max time (in seconds) that a command may run for a bui= ld > # before it is killed for taking too long. Default: 86400 > #MAX_EXECUTION_TIME=3D86400 > MAX_EXECUTION_TIME=3D172800 > > # This defines the time (in seconds) before a command is considered to > # be in a runaway state for having no output on stdout. Default: 7200 > #NOHANG_TIME=3D7200 > NOHANG_TIME=3D172800 > > > I'm maintaining some mongodb ports which also take a long long time to > build on rpi4. > But I don't remember which of these settings has the preferred impact on > your situation. > > Oh... now I'm reading your log better. It contains this: > "=3D>> Killing timed out build after 86400 seconds" > > And some time later: > "=3D>> Cleaning up wrkdir > =3D=3D=3D> Cleaning for chromium-113.0.5672.126" > > So the errors about missing files happen because poudriere is removing > files while some processes of the build are still running. > > I'm curious how far it gets after you increase MAX_EXECUTION_TIME. > > Regards, > Ronald. > =C3=82 > --=20 Nuno Teixeira FreeBSD Committer (ports) --000000000000b0a90f05fce52503 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello Ronald and all!

Finall= y I build it after 57 hours @ 2000MHz !!!

I'm running it right now and it runs very smooth!

Next step will be compiling with LTO to check compile time= and do some comparisons on binary size and run performance.

=
Should I bother with LTO? Will it add performance?

Thanks all!


Ronald Klop <ronald-lists@klop.ws> escreveu no d= ia ter=C3=A7a, 23/05/2023 =C3=A0(s) 11:23:
=C3=82=C2=A0

Van: Nuno Teixeira <eduardo@freebsd.org>
Datum: dinsdag, 23 mei 2023 09:48
Aan: FreeBSD Mailing List <freebsd-ports@freebsd.org>, freebsd-arm@freebsd= .org
Onderwerp: Re: Improving www/chromium build time on arm64<= /p>

(...)
=C3=82=C2=A0
But I also found that poudriere:
[88:53:28] Failed ports: www/chromium:build/timeout
=C3=82=C2=A0
So I will search how do I increase build time to avoid timeout:
---
# This defines the max time (in seconds) that a command may run for a = build
# before it is killed for taking too long. Default: 86400
#MAX_EXECUTION_TIME=3D86400
---
=C3=82=C2=A0
I suspect it can be the cause of build failure because build >24h.<= /div>
=C3=82=C2=A0
Nuno Teixeira <eduardo@freebsd.org> escreveu no dia ter= =C3=83=C2=A7a, 23/05/2023 =C3=83=C2=A0(s) 08:31:
Hello all,
=C3=82=C2=A0
I'm running 13-STABLE on rpi4 8 and since firefox{-esr} is constan= tly tab crashing and seg faulting I decided to give chromium a try.
chromium pkg isn't available for arm64 and I didn't found erro= r log at=C2=A0https://pkg-status.freebsd.org/ so I decided to build it on poudriere.=
=C3=82=C2=A0
It fails to build around 70% but my biggest concern is build time: 27 = hours for 70% compilation!
=C3=82=C2=A0
Just for comparison:
llvm15: 12h
rust: 9h
firefox: 6h
=C3=82=C2=A0
rip4 v1.5 8GB @ 2000Hz ~62 Celsius
zfs
poudriere:
USE_TMPFS=3Dno
PARALLEL_JOBS=3D1
ALLOW_MAKE_JOBS=3Dyes
=C3=82=C2=A0
Any hints on how to speed build? ccache?
Does cflags "-O -pipe" not present in compilation is related= to build time?=C2=A0
=C3=82=C2=A0
Full log:
=C3=82=C2=A0
Thanks!
=C3=82=C2=A0
---
<SNIP>
In file included from ../../base/check.h:11:
../../base/compiler_specific.h:8:10: fatal error: 'build/build_config.h= ' file not found
#include "build/build_config.h"
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0^~~~~~~~~~~~~~~~~~~~~~
1 error generated.
ninja: build stopped: subcommand failed.
=3D=3D=3D> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=3Dyes and rebuild before reporting the failure = to
the maintainer.
*** Error code 1

Stop.
make: stopped in /usr/ports/www/chromium
build of www/chromium | chromium-113.0.5672.126 ended at Tue May 23 02:22:5= 6 WEST 2023
build time: 27:15:37
!!! build failure encountered !!!
---
--
Nuno Teixeira
FreeBSD Committer (ports)
=C2=A0
=C3=82=C2=A0
--
Nuno Teixeira
FreeBSD Committer (ports)


Hi,

My poudriere.conf for building ports on rpi4 contains these two changes:
# This defines the max time (in seconds) that a command may run for a build=
# before it is killed for taking too long. Default: 86400
#MAX_EXECUTION_TIME=3D86400
MAX_EXECUTION_TIME=3D172800

# This defines the time (in seconds) before a command is considered to
# be in a runaway state for having no output on stdout. Default: 7200
#NOHANG_TIME=3D7200
NOHANG_TIME=3D172800


I'm maintaining some mongodb ports which also take a long long time to = build on rpi4.
But I don't remember which of these settings has the preferred impact o= n your situation.

Oh... now I'm reading your log better. It contains this:
"=3D>> Killing timed out build after 86400 seconds"

And some time later:
"=3D>> Cleaning up wrkdir
=3D=3D=3D> Cleaning for chromium-113.0.5672.126"

So the errors about missing files happen because poudriere is removing file= s while some processes of the build are still running.

I'm curious how far it gets after you increase MAX_EXECUTION_TIME.

Regards,
Ronald.
=C3=82=C2=A0


--
Nuno Teixeira<= br>FreeBSD Committer (ports)
--000000000000b0a90f05fce52503--