Main menu:


Please consider a small donation:



Or you can donate bitcoin:


Thanks to TekLinks in Birmingham, AL, for providing colocation and bandwidth.

Page Rank


FOSS Force Best Blog--2013 Award

Recent posts

Recent comments

About this blog

I am Eric Hameleers, and this is where I think out loud.
More about me.


Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 422 other subscribers

My Favourites



March 2019
« Feb    

RSS Alien's Slackware packages

RSS Alien's unofficial KDE Slackware packages

RSS Alien's multilib packages

RSS Slackware64-current



Chromium 64 – and 32bit pain

The new release of the Chromium sources gives us version 64 of Google’s browser. I have created Slackware packages for you, but that was not entirely trivial.
The Chromium compilation on my 32bit Slackware OS kept failing on the embedded ffmpeg. I am afraid the fact that some of the bigger distros are dropping 32bit variants starts showing and things are coming apart at the seams.
When you are a developer and there’s no 32bit release of your favorite OS, this makes it quite difficult to test the validity of code paths when you only compile and test your code on a 64bit platform. This is what’s happening with Google’s Chromium code and it will probably only get worse.

For now, I could get away by disabling assembly code in the 32bit avcodec library, but in order to get that going I had to study the Chromium code carefully – Google does not use the standard autotools or cmake configurations that the Average Joe would employ when compiling ffmpeg, instead they re-invent the wheel every so often to keep everyone on edge. First it was Gyp, but that did not work out too well and the current fad is called GN (as Google state themselves “GN is a meta-build system that generates Ninja build files so that you can build Chromium with Ninja“).

Some time soon, I need to dissect Chromium’s embedded ffmpeg code, to see if I can get assembly code compiling again on 32bit. Else it may be more prudent to start depending on an external (system-wide) ffmpeg installation, which I can compile without any pain on 32bit Slackware.

We’re fine for now, at least. Let’s hope it does not get worse.

Get your chromium 64 packages for Slackware 14.2 and -current:

Cheers, Eric


Pingback from Links 30/1/2018: Godot 3.0 and ncurses 6.1 | Techrights
Posted: January 30, 2018 at 14:42

[…] Chromium 64 – and 32bit pain […]

Comment from Gérard Monpontet
Posted: January 30, 2018 at 15:32

I use it, just occasionally, it work, Thanks, Eric. 😉

Comment from Eduardo
Posted: January 30, 2018 at 16:35

Thank you Eric!

Comment from Mohammad Etemaddar
Posted: January 30, 2018 at 23:02

Dear Eric,
Do you have any experience in compiling android OS for mobile? Would you mind write about it?

Comment from alienbob
Posted: January 31, 2018 at 10:34

Mohammad , I do not see the relevance of your question to the topic of this post.
Anyway the answer is no and no.

Comment from Fellype
Posted: February 1, 2018 at 17:17

I’d like to tell you to kick the Chromium ass. But… I still using Chromium for Google’s products because all them work better with it :-þ
Then, thank you for your effort 🙂

Comment from ajevremovic
Posted: February 8, 2018 at 08:39

Anybody else faced with memory leak with this new version? It eated 10GB+ within 24 hours.

Write a comment