Bug 263833

Summary: www/chromium: no longer packaged for FreeBSD:12:amd64 – build/timeout
Product: Ports & Packages Reporter: Lena <Lena>
Component: Individual Port(s)Assignee: freebsd-chromium (Nobody) <chromium>
Status: Open ---    
Severity: Affects Many People CC: dave, grahamperrin, pkgmgr
Priority: --- Flags: bugzilla: maintainer-feedback? (chromium)
Version: Latest   
Hardware: amd64   
OS: Any   
URL: https://www.freshports.org/www/chromium/

Description Lena 2022-05-07 08:49:08 UTC 
12.3-amd64. I have package chromium-99.0.4844.82 installed on April 1.
Since then no new chromium package for packages-lasest.
Though quarterly has 101.0.4951.54 - I tried to find the reason but failed.

Last mailing list message I see - "exp bulid/timeout":
https://lists.freebsd.org/archives/freebsd-chromium/2022-May/000683.html

As a consequence I'm afraid to upgrade www/firefox and its dependency devel/icu
because devel/icu upgrade may break installed chromium-99 I think.
Comment 1 Graham Perrin freebsd_committer freebsd_triage 2022-11-20 01:25:26 UTC 
Adapted from the fallout link at FreshPorts: 

<https://portsfallout.com/fallout?port=www%2Fchromium%24&env=123amd64>

The tail of the latest build/timeout for 123amd64-default (logs are colossal, this was 146.1 MiB): 

…
[ 99% 52271/52272] rm -f obj/headless/libheadless_shell_lib.a && "ar" -T -r -c -s -D obj/headless/libheadless_shell_lib.a @"obj/headless/libheadless_shell_lib.a.rsp"
[100% 52272/52272] python3 "../../build/toolchain/gcc_link_wrapper.py" --output="./chrome" -- c++ -Wl,--version-script=../../build/linux/chrome.map -fuse-ld=lld -Wl,--build-id=sha1 -fPIC -Wl,-z,noexecstack -Wl,-z,relro -Wl,-z,now -Wl,--icf=all -Wl,--color-diagnostics -m64 -no-canonical-prefixes -Wl,-O2 -Wl,--gc-sections -rdynamic -pie -Wl,--disable-new-dtags -L/usr/local/lib  -fstack-protector-strong -L/usr/local/lib  -o "./chrome" -Wl,--start-group @"./chrome.rsp"  -Wl,--end-group  -lpthread -lgmodule-2.0 -lglib-2.0 -lgobject-2.0 -lgthread-2.0 -lintl -licui18n -licuuc -licudata -lnss3 -lsmime3 -lnssutil3 -lplds4 -lplc4 -lnspr4 -ldl -latk-1.0 -latk-bridge-2.0 -lcups -lgio-2.0 -ldrm -lfontconfig -ldbus-1 -lkvm -lexecinfo -lutil -levent -lpng16 -lz -lwebpdemux -lwebpmux -lwebp -lharfbuzz-subset -lharfbuzz -ljpeg -lexpat -lxcb -lxkbcommon -lm -lopus -lopenh264 -lX11 -lXcomposite -lXdamage -lXext -lXfixes -lXrender -lXrandr -lXtst -lgbm -lwayland-client -lwayland-server -lpangocairo-1.0 -lpango-1.0 -lcairo -lsndio -lwayland-egl -lXi -lGL -lpci -lsnappy -latspi -lxml2 -lFLAC -lusb -liconv -lxslt -lxshmfence
=>> Cleaning up wrkdir
===>  Cleaning for chromium-106.0.5249.119
build of www/chromium | chromium-106.0.5249.119 ended at Sun Oct 16 14:42:46 UTC 2022
build time: 36:46:26
!!! build failure encountered !!!
% 


That was with: 

MAKE_JOBS_NUMBER=2
Comment 2 Graham Perrin freebsd_committer freebsd_triage 2022-11-20 01:29:42 UTC 
Logged: 

> =======================<phase: check-sanity   >============================
> 
> To build Chromium, you should have around 2GB of memory
> and around 14 GB of free disk space.

Is that _truly_ a sane amount of memory for a build of www/chromium?
Comment 3 Dave Hayes 2022-11-28 04:07:12 UTC 
I've successfully compiled chromium on 12.3 amd 64 since 105.0.5195.102
(Q32022). 

Now, however, I doubt that insufficient memory is the issue. In the makefile:

.if ${OSREL} == "12.3"
IGNORE=         does not compile, libc++ too old
.endif

This was recently (as of 11/27/22) committed. I'm curious as to:

a) What version of libc++ is -not- too old?
b) What happened? 

I suppose I should remove this and try and build it myself to really see. :)
Comment 4 Graham Perrin freebsd_committer freebsd_triage 2023-01-02 11:12:40 UTC 
<https://portsfallout.com/fallout?port=www%2Fchromium%24&env=123amd64> nothing since 2022-10-16 (another build/timeout). 

<https://www.freshports.org/www/chromium/#packages> no package for FreeBSD:12:amd64.

<https://portsfallout.com/fallout?env=124> nothing yet, I guess that there's not (yet) a separate build service for 12.4.