46
Applications and Porting / [DEV] An attempt to package chromium for ppc64le in the official Fedora DNF repo
« on: September 10, 2023, 09:07:01 am »
UPDATE 31 July 2024: Fedora has adopted the patchset that Debian and other distros are using (https://gitlab.solidsilicon.io/public-development/open-source/chromium/openpower-patches). Great thanks to Than Ngo of RedHat, Timothy Pearson (Debian package maintainer)
EDIT: Than Ngo of Red Hat has cherry-picked all ppc64le patches into the main trunk. Now we officially have chromium for Fedora 40 or newer!
URL https://src.fedoraproject.org/rpms/chromium/pull-request/37 *STILL WORK IN PROGRESS*
The last time I was successful at getting Chromium up and running in Fedora is 3 years ago. That was version 88. Now Chromium has reached version 117.
This weekend I've spent a bit of time to adapt Timothy Pearson's patchset from Debian deb package for the official chromium Fedora RPM. So far I could get the whole application compiled and running HOWEVER the browser get into SIGSEGV or SIGTRAP with web pages that has JavaScript. So I speculate this might be related to the V8 engine.
The error outputs in the console is not so much helpful:
I also attempt to gdb and could not find any useful backtrace (NOTE: I manually commented out all `strip` symbols in the build spec file).
The full log out when trying to open a webpage https://gist.github.com/runlevel5/3c85515c521ebcfb6ca65e4697b6b1d1
Any idea how to get more logs out of V8 in Chromium?
EDIT: Than Ngo of Red Hat has cherry-picked all ppc64le patches into the main trunk. Now we officially have chromium for Fedora 40 or newer!
URL https://src.fedoraproject.org/rpms/chromium/pull-request/37 *STILL WORK IN PROGRESS*
The last time I was successful at getting Chromium up and running in Fedora is 3 years ago. That was version 88. Now Chromium has reached version 117.
This weekend I've spent a bit of time to adapt Timothy Pearson's patchset from Debian deb package for the official chromium Fedora RPM. So far I could get the whole application compiled and running HOWEVER the browser get into SIGSEGV or SIGTRAP with web pages that has JavaScript. So I speculate this might be related to the V8 engine.
The error outputs in the console is not so much helpful:
Code: [Select]
[1961086:1961086:0910/235841.808221:ERROR:CONSOLE(1)] "Uncaught SyntaxError: Invalid regular expression: /([^\s]+?)\(([\s\S]*)\)/: Maximum call stack size exceeded", source: chrome://resources/polymer/v3_0/polymer/polymer_bundled.min.js (1)
[0910/235911.891648:ERROR:check.cc(298)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
[0911/000357.201831:ERROR:check.cc(298)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
I also attempt to gdb and could not find any useful backtrace (NOTE: I manually commented out all `strip` symbols in the build spec file).
The full log out when trying to open a webpage https://gist.github.com/runlevel5/3c85515c521ebcfb6ca65e4697b6b1d1
Any idea how to get more logs out of V8 in Chromium?
