SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
<insert typically long drawn out background essay here>
In closing:
My compiled Firefox (for x86_64) was slower than the one I downloaded (for x86) off Mozilla's site. It was somewhat distressing, but, lesson learnt: the Mozilla dev team know what they're doing better than I do =D
I've always compiled Firefox for Slack, using the latest BLFS book as a guide.
It gets awkward only if you want to create a Slackware package (which I do), because you need the five or so files that are created by running firefox as root the first time.
Next time I'm at my Slack box, I'll post the exact ./configure line I use - if you like.
So if those options seem OK to you, or at least OK enough, then there would be no real need to compile a custom version of Firefox, although at the same time it couldn't hurt anything to compile against the specific libraries on your system.
Are you on 64 bit right now? If so, you might take a look at the Gentoo on AMD64 forum. The advice there is to use the 32 bit binary for Firefox rather than compiling, so that 32-bit plugins will work (I think that's the argument, anyway).
Well, if and when you do decide to look into it further, my guess would be that you're needing the x-11 devel package. As I understand it, that's what allows XFT and freetype support to be compiled in, among other things.
Sorry, yes, the configure stopped right there. I'm not sure if that's good or bad.. running make works, but i wanted to ask just to check if it mised anything in configure or not.
Well, like I said, I'm not a compiling expert. But if it were my system, if that was the only warning in ./configure, and then if make seemed to roll along just fine, I wouldn't worry about it.
You should probably wait for a more informed opinion that however, if you're planning to wait.
Originally posted by piete <insert typically long drawn out background essay here>
Thank you so much for making my morning that much more enjoyable!
I am starting to feel like a deadbeat Slackware user, using slackpackages that others have compiled and posted on the web!
I guess I had better move pkg making further up my "Learn to do" list!
Well so far it works, appart from the annoying user profile thing that popps up again... Whenever i want to start more than one instance of FF, it forces me to choose another user profile.. Last time i saw that was in FF 0.9
That's controlled by the startup script for Firefox, which is the file named "firefox" (as opposed to "firefox-bin") in /usr/lib or wherever you installed the application. You might try editing that script.
But I think that this is supposed to prevent other programs from possibly messing up the profile by writing to the profile folder when it's in use - that's why it's locked and a second session cannot start up. See: http://kb.mozillazine.org/Profile_in_use
I don't know that there is anything on my Linux system that would try to write to my profile folder, but maybe it's a security thing? It doesn't bug me, because I'd rather open a new tab in my existing window than a new window altogether. But everyone has his or her own preferences.
Anyway, glad to hear that it compiled OK. I'm jealous that it went so fast (lightening fast, from my perspective. My computer is so old and slow that I only compile things when there is absolutely no other alternative!)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.