Im trying to compile Firefox 53.0, and I got this error:
I have the line
as it says as an option in the book. This is the only place in my mozconfig where it says cairo-gtk2.

According to this link, which is specific to Firefox v. 53, that version needs "GTK+ 3.4 or higher." The page notes that

You might also want to take a look at Mozila's Firefox compatibility chart, but it looks to me that it needs updating.
https://developer.mozilla.org/en-US/...ibility_matrix

Those links were about precompiled packages. I'm compiling it from source, as I wrote in my first post...

@Lennie:

Mozilla has effectively dropped gtk2 support from version 53. You can still build Firefox with gtk2 support by getting the 52 ESR version.

1 members found this post helpful.

Thanks. Then I'll do that.

The bigger problem is that firefox v53 requires rust and its underlying infrastructure, cargo and llvm 3.x. If you are a llvm 4.x user, you still have to compile llvm 3.x. This is a lot of disk space just to be able to compile firefox.

Since I don't use llvm/rust, I compiled firefox v53 using --disable-rust. So far, it seems to be working.

The mozilla website states that, starting with firefox 55, rust will be mandatory.

There is also the debate going on between Stallman and the llvm people concerning GPL (Gnu C/C++) vs non-GPL (llvm/clang). Stallman does not like llvm because it is non-GPL and is being backed by Apple.

Maybe time to switch to chromium.

Switched to chromium permanantly couple of years ago, very stable much better than firefox, bit of a pain to compile though, but then so is ff

A complete and utter disregard for backwards compatibility is one of the core issues with Linux on the desktop. Strangely, I never see it mentioned in presentations and whitepapers purporting to explain why Linux never claimed significant desktop share. Personally, I think it is a top 5 reason business software developers look at the Linux desktop and think, "nope." There's few things more annoying than having the rug pulled out of from under you without a good reason, or even a reason given at all. It's hard enough dealing with developers in your own company making changes that f' things up without relying on an external ecosystem where design decisions are made based on the moods of cliques and popularity. There's just too much chaos in The Bazaar and I'll wager 3/4 of it is prompted for reasons other than those that are logical or engineering in nature. That said, freedom will have a price, regardless of what you do.

1 members found this post helpful.