Bug 219110

Summary: www/firefox-i18n and www/firefox-esr-i18n: mark BROKEN on aarch64 due to "firefox --version" crashing
Product: Ports & Packages Reporter: Mark Linimon <linimon>
Component: Individual Port(s)Assignee: freebsd-arm (Nobody) <freebsd-arm>
Status: Closed Overcome By Events    
Severity: Affects Some People CC: linimon
Priority: --- Flags: jbeich: maintainer-feedback+
Version: Latest   
Hardware: arm64   
OS: Any   
Bug Depends on:    
Bug Blocks: 201763    
Description Flags
patch to various gecko@ ports
patch to various gecko@ ports jbeich: maintainer-approval+

Description Mark Linimon freebsd_committer freebsd_triage 2017-05-06 21:39:33 UTC
I am going through the tier-2 build logs and marking various things BROKEN.  I do not have the time to fix these at the moment.  There is no reason to try to build them over and over again during package builds.

Patches welcome.
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2017-05-06 21:40:49 UTC
Created attachment 182350 [details]
patch to various gecko@ ports
Comment 2 Jan Beich freebsd_committer 2017-05-06 21:58:57 UTC
Comment on attachment 182350 [details]
patch to various gecko@ ports

> BROKEN_aarch64=		fails to compile:  error: no member named cacheFlush

Vague (which file?) and out of date.

Comment 3 Mark Linimon freebsd_committer freebsd_triage 2017-05-07 16:42:13 UTC
Created attachment 182368 [details]
patch to various gecko@ ports
Comment 4 Jan Beich freebsd_committer 2017-05-21 00:19:42 UTC
Looks fine but maybe arm@ folks want to check *why* Firefox crashes on aarch64? Let's wait 1-2 weeks more.

Also upstream plans to transition aarch64 from Tier3 to Tier1 in Firefox 55.
Comment 5 Jan Beich freebsd_committer 2017-07-10 14:36:21 UTC
Firefox 55 will also support --headless flag that may (probably not) help work around the crash.
Comment 6 Jan Beich freebsd_committer 2017-10-21 02:11:44 UTC
-i18n finally built fine on aarch64. I'm not sure if it's specific to -CURRENT or 56.* as 11.0 build was blocked by a dependency (see bug 223009). However, marking BROKEN_FreeBSD_11_aarch64 would be too soon until we have results for 11.1 builds which should start sometime after 2017-10-26 (11.0 EOL).