Date: Fri, 16 Feb 2024 00:19:27 +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-CVJvgWEqNh@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 fgorter <fgorter@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fgorter@gmail.com --- Comment #58 from fgorter <fgorter@gmail.com> --- Hey fellas, I have an observation. Had the same error as OP, namely: XPCOMGlueLoad error for file /usr/local/lib/firefox/libgkcodecs.so: /usr/local/lib/firefox/libgkcodecs.so: Undefined symbol "sin" Couldn't load XPCOM. In a few testing scenarios, I tried all the different fix combinations (this box is tracking 13.3-STABLE) as you guys have reported here, without desired result. The build proceeds successfully, but executing firefox fails. For clarity, I've left all files in www/firefox/files/ untouched, deleting/reverting all patches I made myself each time -- in an effort to remain in sync with everything officially made available in the official FreeBSD repo. Just moments ago, I built the port again after the usual git pull for updat= es, which resulted again in the same error related to libgkcodecs.so we've been having. Then, just on a hunch of "well, whatever, let's give this a shot for a laugh...", I deleted the entire local /usr/ports tree & git cloned a fresh = new copy of the entire ports tree. Built the port again, and voila, successfully built & launched FireFox. Usi= ng it right now. I have NO clue how/why this has happened. My /etc/make.conf file has remained untouched throughout. In fact, it has remained untouched for over a year now. All I've got in my make.conf file: CPUTYPE?=3Dskylake-avx512 Yes, the CPU is indeed a model listed that can take advantage of this CPUTY= PE option; which has so far never caused a problem. This fact would seem to undermine, at least partially perhaps, the suspicion cputypes has something= to do with the bug -- as the bug presented with my previous local (stale?) por= ts tree, versus the bug being resolved *after* git cloning a fresh new ports t= ree. Might this be a case that the issue is actually elsewhere in the ports tree? However when I rebuilt, no other new/old ports were pulled into the fold, t= he sole port being built & installed was www/firefox... a conundrum, indeed. --=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-CVJvgWEqNh>