Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Web browser options for PPC64?
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Gentoo on PPC
View previous topic :: View next topic  
Author Message
socamx
n00b
n00b


Joined: 30 Jan 2021
Posts: 1

PostPosted: Sat Jan 30, 2021 4:04 pm    Post subject: Web browser options for PPC64? Reply with quote

It doesn't seem possible to emerge any modern web browser on ppc64. I have an original dual 2 ghz Power Mac G5 running xfce4 and every single web browser I try to install that is remotely modern is either a precompiled, x86 only binary, or itself and most of its dependencies are masked off.

I was hoping to get Firefox or Epiphany going but neither seem to be possible.

The only one I have gotten installed and going is Dillo, and it's a relic of the early 2000s that barely supports CSS, let alone any even remotely modern standards.

Is PPC64 just out of luck for modern browsers?
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 54097
Location: 56N 3W

PostPosted: Sat Jan 30, 2021 5:37 pm    Post subject: Reply with quote

socamx,

Welcome to Gentoo.

PPC64 is no well tested. Feel free to keyword things you would like to try.
Firefox will be a challenge. It needs rust and llvm.

Rust is known to build on powerpc64-unknown-linux-gnu. That's you.
llvm builds too. There is a .deb of llvm-10.

That does not mean that they will just work for you.

To see what needs to be built to get firefox, cheat.
Code:
ACCEPT_ARCH="amd64" emerge firefox -pv
will spit out a list of all the packages that would be built on amd64. That's the things you need.
You way want to save that output to a file.

The packages on that list that are keyworded ppc64 or ~ppc64 are known to build. The other packages are not tested.
The wheel comes off a little because your arch becomes a USE flay that is used to trigger ARCH dependent options in the build and the package build systems.
That means you cannot use
Code:
ACCEPT_ARCH="amd64" emerge firefox
and have it just work.
Some of the options that get passed to build systems will cause failures.
You are back to keywording.

The good news is
Code:
$ grep ppc  /usr/portage/dev-lang/rust/*
grep: /usr/portage/dev-lang/rust/files: Is a directory
/usr/portage/dev-lang/rust/rust-1.46.0.ebuild:   KEYWORDS="amd64 arm arm64 ppc64 x86"
/usr/portage/dev-lang/rust/rust-1.47.0-r2.ebuild:   KEYWORDS="amd64 ~arm ~arm64 ppc64 x86"
/usr/portage/dev-lang/rust/rust-1.47.0-r2.ebuild:   # on ppc64 we unpack both BE and LE archive, so double that.
/usr/portage/dev-lang/rust/rust-1.47.0-r2.ebuild:   M=$(( $(usex system-bootstrap 0 $(usex ppc64 2048 1024) ) + ${M} ))
/usr/portage/dev-lang/rust/rust-1.48.0.ebuild:   KEYWORDS="~amd64 ~arm ~arm64 ~ppc64 ~x86"

so rust and by inference, all its dependences ace tested on ppc64 on gentoo.

llvm is in the same state.grep ppc /usr/portage/sys-devel/llvm/*
Code:
grep: /usr/portage/sys-devel/llvm/files: Is a directory
/usr/portage/sys-devel/llvm/llvm-10.0.1.ebuild:KEYWORDS="amd64 arm arm64 ppc64 x86 ~amd64-linux ~ppc-macos ~x64-macos"
/usr/portage/sys-devel/llvm/llvm-11.0.0.ebuild:KEYWORDS="amd64 arm arm64 ppc64 ~riscv x86 ~amd64-linux ~ppc-macos ~x64-macos"
/usr/portage/sys-devel/llvm/llvm-11.0.1.ebuild:KEYWORDS="~amd64 ~arm ~arm64 ~ppc64 ~riscv ~x86 ~amd64-linux ~ppc-macos ~x64-macos"
/usr/portage/sys-devel/llvm/llvm-9.0.1.ebuild:KEYWORDS="amd64 arm arm64 ppc64 x86 ~amd64-linux ~ppc-macos ~x64-macos"

_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 8933

PostPosted: Sat Jan 30, 2021 11:20 pm    Post subject: Reply with quote

www-client/falkon has ppc64 keyword.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 54097
Location: 56N 3W

PostPosted: Sat Jan 30, 2021 11:37 pm    Post subject: Reply with quote

Aww asturm,

We might have got someone keywording ppc64 :)
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Juippisi
Developer
Developer


Joined: 30 Sep 2005
Posts: 722
Location: /home

PostPosted: Sun Jan 31, 2021 5:30 am    Post subject: Reply with quote

Firefox does have ~ppc64 KEYWORDS, but were you after firefox-bin? If you choose firefox, you get some relief by installing rust-bin.
Back to top
View user's profile Send private message
schwarzygesetzlos
Apprentice
Apprentice


Joined: 11 Dec 2004
Posts: 185
Location: Funeralopolis

PostPosted: Sun Mar 14, 2021 12:19 pm    Post subject: Reply with quote

www-client/falkon has ~ppc64 keyword but dev-qt/qtwebengine on which it is based has no ~ppc64 keyword. Also qtwebengine won't run (unpatched) on Big Endian machines like a G5.
www-client/firefox builds and works fine on my Talos II (POWER 9 cpu) but does not build on my G5 (POWER 4 based 970MP cpu). Maybe rust and/or Firefox implicitly use newer cpu instructions?

The only 2 non-text-based browsers which work on my G5 so far are www-client/epiphany and www-client/netsurf. If net-libs/webkit-gtk (which Epiphany uses) crashes on some sites you could try building it with patches included in the ~ppc keywording request. Would be interesting to know whether they improve the situation on ppc64 too.
_________________
Talos II. [Gentoo Linux] | PMac G5 11,2. PMac G4 3,6. PBook G4 5,8. [MorphOS 3.18 / Gentoo Linux] | Vampire V4 SA [ApolloOS / Amiga OS 3.2.2]
Back to top
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 21490

PostPosted: Sun Mar 14, 2021 4:57 pm    Post subject: Reply with quote

On i686, Rust definitely does use newer instructions than technically exist on i686. (Specifically, basic i686 does not have SSE2, but default x86 Rust builds do try to use SSE2 despite claiming a CHOST of i686.) I am not familiar with Rust on PPC64, but I would not be surprised if it also assumed a higher baseline than gcc assumes for a target of ppc64.
Back to top
View user's profile Send private message
schwarzygesetzlos
Apprentice
Apprentice


Joined: 11 Dec 2004
Posts: 185
Location: Funeralopolis

PostPosted: Fri Jun 04, 2021 1:05 am    Post subject: Reply with quote

Firefox working now again on a G5! The key to success is to use a recent dev-libs/nss (3.64 or greater).

nss-3.64 mentions some ppc fixes:
Bug 1687164 - Introduce NSS_DISABLE_CRYPTO_VSX and disable_crypto_vsx.
Bug 1698320 - replace __builtin_cpu_supports("vsx") with ppc_crypto_support() for clang.
Bug 1613235 - Add POWER ChaCha20 stream cipher vector acceleration.

I used dev-libs/nss-3.65-r1 in combination with Firefox 78.10.1 on ppc64-musl and with Firefox 89.0 on ppc64-glibc. Both run fine without crashes, even youtube-playback works! Though you get 'funky' colours. ;)
_________________
Talos II. [Gentoo Linux] | PMac G5 11,2. PMac G4 3,6. PBook G4 5,8. [MorphOS 3.18 / Gentoo Linux] | Vampire V4 SA [ApolloOS / Amiga OS 3.2.2]
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo on PPC All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum