Having previously tried (and failed) to build Chromium on my Slackware system, the news that a beta build is now available for Linux was a welcome surprise. However, it is a little more tricky to get running than you’d expect, so here’s how to do it:
- Download a package containing the required NSS libraries from here. This package was built using Road_map’s instructions on this forum thread and a slackbuild script by (who else?) Eric. Install it using the standard installpkg command; It shouldn’t be replacing anything…
- Use the following commands (as root or with sudo) to set up Google’s weird, weird symlinks. Does Ubuntu use .so.*d files or something?!
ln -s /usr/lib/libplds4.so /usr/lib/libplds4.so.1d
ln -s /usr/lib/libnss3.so /usr/lib/libnss3.so.1d
ln -s /usr/lib/libsmime3.so /usr/lib/libsmime3.so.1d
ln -s /usr/lib/libssl3.so /usr/lib/libssl3.so.1d
ln -s /usr/lib/libnssutil3.so /usr/lib/libnssutil3.so.1d
ln -s /usr/lib/libnspr4.so /usr/lib/libnspr4.so.0d
ln -s /usr/lib/libplc4.so /usr/lib/libplc4.so.0d
ln -s /usr/lib/libplds4.so /usr/lib/libplds4.so.0d - Download the latest Chrome Linux beta tarball (well, zip file..) from here.
- Extract the ‘chrome’ executable to somewhere in your path.
- Pester me if it doesn’t work, or if I did something wrong. I usually do..
For those interested, having followed the steps above, it should also be possible to build Chromium under Slackware. The poor documentation regarding ‘hammer’ put me off, even though I did find it in the end. Having gotten Chromium working, I decided not to bother with using about 15 Chrome-specific utilities just to set up the build system…
3 Comments
ok, first off, the link to the nss slackbuild you referenced seems to be broken. you have one additional simlink that doesn’t exist on an ubuntu installation of google chrome:
ln -s /usr/lib/libplds4.so /usr/lib/libplds4.so.1d
i’ve been working on getting chrome or chromium to run on VectorLinux, which is based on Slackware. been having some pretty severe issues. just not sure where the problems are. I have a detailed log posted at the following forum:
http://forum.vectorlinux.com/index.php?topic=10210.0
I was hoping you might lend your insight to the problem.
thx, in advance.
Ah, I see that the hosting service I was using has given up on me
. I will rectify that asap, and also try and look into your other problems if/when I get a chance. To my inexperienced eye, it certainly does look like you have a dependency problem – did you replace NSS with a version that contains NSPR, or are you relying on the version of NSS that comes with Firefox?
In the meantime, you may want to try the method I used to make the dependency .tgz in the first place, which is outined in steps 1 to 3 here – http://www.linuxquestions.org/questions/slackware-14/build-chrome-on-slackware-current-fail-no-package-nss-found-667546/#post3269547 (post #6).
My instructions are obviously quite outdated by now and I haven’t played around with any recent Chromium builds, but please let me know how you get on
I downloaded the .rpm and used rpm2tgz to install Chrome today, and after getting the library issues I more or less followed your instructions – but I changed the ln -s to cp in my script. Consequently, Chrome works beautifully so far. Thanks.
One Trackback/Pingback
[...] Eu não criei um pacote para o chromium, talvez eu o faça no futuro. Até lá baixe o ultimo tarball e rode só pro seu usuário, caso você tenha problemas com os nomes estranhos criados pelo pessoal que empacota para o debian (alguém faz ideia de por que o .d??) faça o seguinte que tirei daqui. [...]