Bug 248232 - www/firefox versions 78.0.2 and 79.0: turning OPTIMIZED_CFLAGS off breaks compile
Summary: www/firefox versions 78.0.2 and 79.0: turning OPTIMIZED_CFLAGS off breaks com...
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-gecko (Nobody)
URL:
Keywords:
: 249491 (view as bug list)
Depends on:
Blocks:
 
Reported: 2020-07-24 01:05 UTC by George Mitchell
Modified: 2022-08-08 22:54 UTC (History)
2 users (show)

See Also:
jbeich: maintainer-feedback+


Attachments
Tail end of build log with OPTIMIZED_CFLAGS off (10.35 KB, text/plain)
2020-07-24 01:05 UTC, George Mitchell
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description George Mitchell 2020-07-24 01:05:20 UTC
Created attachment 216733 [details]
Tail end of build log with OPTIMIZED_CFLAGS off

Turning OPTIMIZED_CFLAGS option off causes compile to break as shown in attached build log, seeming to indicate that libepoll-shim was not linked into the build.  Perhaps optimization removes all the calls to the library.
Comment 1 Jan Beich freebsd_committer freebsd_triage 2020-07-24 03:50:26 UTC
Regressed by https://bugzilla.mozilla.org/show_bug.cgi?id=1619882 which added dependency on epoll and made VAAPI videos transparent. Both MOZ_ENABLE_WAYLAND and MOZ_X11_EGL use DMAbuf for VAAPI. During Firefox 75-77 VAAPI did work fine on Wayland (see bug 244793) but X11 support was added in Firefox 80.
Comment 2 George Mitchell 2020-07-24 17:50:45 UTC
I'm glad to know I wasn't imagining things!  I honestly don't know why I ever turned OPTIMIZED_CFLAGS off, but I guess I'll leave it on in the future.
Comment 3 Jan Beich freebsd_committer freebsd_triage 2020-09-21 00:40:22 UTC
*** Bug 249491 has been marked as a duplicate of this bug. ***
Comment 4 Jan Beich freebsd_committer freebsd_triage 2021-01-05 15:36:17 UTC
After ports r560401 it should build fine on FreeBSD >= 13.
Comment 5 George Mitchell 2021-07-01 17:49:20 UTC
As far as I know, this bug is ready to be closed ...
Comment 6 Daniel Engberg freebsd_committer freebsd_triage 2022-08-08 22:54:54 UTC
Closing it by request of submitter