SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
i currently have slack 14 on a vm (virtualbox), firefox22 from current runs fine.
edit: as i now looked at the bug link ive seen "x86_64".. so ff21 crashes on slack 14 64bit?! i run 32bit on my vm and plan to run 32bit if i get slack installed on my routerbox. could be a 64bit compile problem?
Last edited by Stuferus; 07-01-2013 at 01:01 PM.
Reason: added detail/question
I also don't know if this will help, but when I saw the changelog I did download Firefox 22 directly from the Firefox site. I am running a stock Slackware 14 system on my laptop and I am using KDE. I removed the mozilla-firefox package and extracted the Firefox download. It is running just fine, no crashes (at least not yet).
Regardless of that, I do see that the ESR version probably more closely aligns with Slackware's philosophy. I have a need/desire to stay on the latest versions, but I can easily deal with that myself.
Distribution: Slackware64 stable (started with 13.37(32))
I'm already using Firefox and Thunderbird ESR since January.
There is no big difference, just some interface improvements.
I like the new "Downloads" window from Main Release, in ESR we have the old one,
but the main release number version is amazing, at Christmas it must be 30 or more
I heard that building Firefox is long and complicated. It has scared me off trying to do it myself. How long did your build take (machine specs too, if poss.)?
You are right!
I compiled in a Intel Core 2 Quad 2.40GHz, 4GB RAM. The first time I tried it was taking more than 2 hours with full ram + 1GB of swap! I aborted it, and modified the slackbuild script to use "make -j 4" to compile in parallel. It took "only" 54 minutes using ~ 3GB ram.
(BTW, is there a better way to make a slackbuild compile in parallel?)
with SlackBuilds.org scripts generally passing MAKEFLAGS (like MAKEFLAGS=" -j8 ") works, but the official slackbuilds in Slackware use NUMJOBS in the same way.
BTW, in some of them it's explicitly disabled (because not supported).