On Sun, 18 Feb 2024 05:11:49 +0800 Sergey Fedorov <vital....@gmail.com> wrote:
> Could someone say what is the current state of *modern* web browsers for > PowerPC? All 3 major engines are broken on powerpc or powerpc64: - www/chromium recently broke on i386, because it is now too big for 32-bit pointers. It has no chance to run on powerpc. Other than i386, I believe that only aarch64 and amd64 have ever completed a chromium build, so powerpc64 seems unlikely. - www/mozilla-firefox needs a rust compiler, which is missing on powerpc and crashes on powerpc64. After you have rust, there might be other problems. - www/webkitgtk4 is broken in the powerpc bulk build report [1]. It is now a clang error, "failed to perform tail call elimination on a call site marked musttail", but if someone fixed the error, there might be other errors. Older versions failed a static_assert on powerpc. webkitgtk4 is unreachable on powerpc64, because some other packages are broken on powerpc64. [1] https://marc.info/?l=openbsd-ports&m=170725239028843&w=2 OpenBSD/macppc uses the powerpc packages. OpenBSD/powerpc64 only runs on PowerNV models (with OPAL firmware), not on a Mac. > By the way, I assume the following code is wrong, and would prevent > *qutebrowser* from building: > https://github.com/openbsd/ports/blob/0bf6e78f8ed8dfcc1d253d505b23eeed7c28606c/www/qutebrowser/Makefile#L43-L49 The problem is elsewhere: qutebrowser needs x11/qt5/qtwebengine which is a fork of chromium; powerpc can't run chromium. In your link, the check for "${PROPERTIES:Mrust}" correctly excludes powerpc. On Sun, 18 Feb 2024 14:07:14 +0100 Florian Märkl <open...@florianmaerkl.de> wrote: > last time I tried, netsurf from ports worked fairly well. I have been using M-x eww in emacs--gtk3 on macppc, which can load only simple websites, but is better than nothing. Someone had proposed www/ladybird on ports, but I never looked at it. On Sun, 18 Feb 2024 22:41:18 +0000 Roberto Arturo Gonzalez Godinez <robglez...@proton.me> wrote: > If so, from your MacPorts maintenance, I can imagine that you have the > required hardware. If you don't, in the following weeks, I could setup a > G4 tower and give you ssh access to it so you could leave Firefox > building on it. Don't try Firefox as long as there is no rust. Linux or NetBSD might have rust on powerpc, but OpenBSD never did. OpenBSD briefly had lang/rust on powerpc64, but it broke, and some other problems on powerpc64 are blocking a rust fix. (Less than a week ago, I noticed that C++ exceptions are crashing on powerpc64. Working C++ exceptions might unbreak gdb, so gdb can debug other problems.) After rust has a package (on either powerpc or powerpc64), the next obstacle is devel/spidermonkey115, the JavaScript engine from Firefox 115. It needs patches on powerpc64 and probably on powerpc. (It was missing code to handle powerpc64's ucontext_t.) If spidermonkey115 has a package, then x11/gnome/gjs and devel/glade might get packages, which might unblock other stuff like xfce. An attempt at www/mozilla-firefox would require at least bringing forward the spidermonkey patches. www/webkitgtk4 is in the "parallel2" category, among the slowest packages to build. A fast PowerPC Mac might take days to build it. I don't know, because the build now stops early at an error. I would not build llvm (which is smaller than webkit) on a PowerPC Mac unless it had at least a 750 MHz cpu and 1G ram. I want to build llvm, because I have a possible fix for a powerpc llvm bug. My build might take around 4 days. While I am busy with llvm, I am far away from wanting to build webkit. --gkoehler
