Date: Wed, 14 Feb 2024 15:46:18 +0000 From: bugzilla-noreply@freebsd.org To: gecko@FreeBSD.org Subject: [Bug 277021] www/firefox: error on start after updating to 123.0 (rc1, rc2) Message-ID: <bug-277021-21738-kizErMpCiW@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-277021-21738@https.bugs.freebsd.org/bugzilla/> References: <bug-277021-21738@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D277021 --- Comment #28 from Guido Falsi <madpilot@FreeBSD.org> --- Having a look at firefox sources I found something interesting in `third_party/libwebrtc/moz-patch-stack/0106.patch`: ------ From: Chun-Min Chang <chun.m.chang@gmail.com> Date: Tue, 5 Dec 2023 20:08:00 +0000 Subject: Bug 1864008 - Move libvpx to libgkcodecs, part 2 r=3Dwebrtc-reviewers,padenot,mjf This patch addes trampoline headers for libvpx. To follow the libwebrtc merge procedure, the vpx headers are silently replaced with "trampoline" headers, which do nothing but include real VPX headers. This makes the libwebrtc-merge process easier without worrying headers' paths. On the other hand, the `rtc_build_libvpx` is set to `true` in webrtc.gni, so moz.build file for third_party/libvpx can be generated by the gn_processor in the next patch. Differential Revision: https://phabricator.services.mozilla.com/D195495 Mercurial Revision: https://hg.mozilla.org/mozilla-central/rev/d43978d3d8356e176fac2ad18f328871= f36698ce ------ This has a recent date, and looks related. Makes me think libgkcodecs.so is= a recent additions and upstream simply omitted the -lm there. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-277021-21738-kizErMpCiW>