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.
You should enable jemalloc to for better memory mangement etc. It's default in the Mozilla builds. This is new in Firefox 3.
–enable-jemalloc
If it is default in the mozilla builds, then my understanding is that it should not be necessary to add it to .mozconfig. I understood that '.mozconfig' settings are only necessary to change the build configuration from the defaults that are specified in the source tree.
You should enable jemalloc to for better memory mangement etc. It's default in the Mozilla builds.
about:buildconfig in the navigation toolbar shows the compiler flags and the configure arguments used. The default linux binary shows only these configure arguments:
about:buildconfig in the navigation toolbar shows the compiler flags and the configure arguments used. The default linux binary shows only these configure arguments:
Yes, this is exactly my point. about:buildconfig will only show the additional build options specified in 'mozconfig'. It does not for example show which 'toolkit' is used for the build or whether libxul is built. Both of these of course are.
I would like to know of a way to query the source tree to find all the default configuration options of which there are many. Bill
Just to update everyone, I changed the slackbuild. It seems if you have read the post "firefox 3.0 + thunderbird = no email links" it turns out the Pat's firefox/thunderbird patch doesn't seem to be needed anymore and in some cases (mine and otheres) it was causing problems, I now have removed the patch from the slackbuild and now my email problem is fixed. So on the safe side I changed the build however you can still download the original slackbuild from here http://webpages.charter.net/daedra/1...SlackBuild.old
So this patch is all you need to fix the application problem? I thought I read that you had to compile a whole bunch of gnome stuff to get that working? Also where did you add the patch, before or after compile?
That so called subpixel rendering of colored pixels makes my eyes water... Its that bad. Blowing cigarette smoke in my face isn't nearly as bad.
I like my fonts with AA but no subpixel rendering. http://img384.imageshack.us/img384/148/fontsfv1.png
That's how its done.
That so called subpixel rendering of colored pixels makes my eyes water... Its that bad. Blowing cigarette smoke in my face isn't nearly as bad.
I like my fonts with AA but no subpixel rendering. http://img384.imageshack.us/img384/148/fontsfv1.png
That's how its done.
I can see what your saying, but without the subpixel rendering they just look to soft to me. I prefer subpixel rendering, but I also like the old bytecode nonAA rendering too, I didn't include that into my howto because it seems so few have CRTs now, most people have switched to LCD.
I can see what your saying, but without the subpixel rendering they just look to soft to me. I prefer subpixel rendering, but I also like the old bytecode nonAA rendering too, I didn't include that into my howto because it seems so few have CRTs now, most people have switched to LCD.
Hmm, now that I think about it, it will look even worse on a CRT. Meaning I've been using LCDs for many years now. Perhaps it needs tuning for my current monitor, like the color order in a pixel, but I've played with that before, and none of the combinations produced a result I would be happy with. I definitely have to have AA on text at all times though, I even went the length of doing a GTK+ 1 hack, although I don't use that many of GTK+ 1 apps anymore.
NonAA renderings have their purpose... But not in a browser.
Matter of taste I guess. It didn't seem like a biggie back in Win 98 days where I had a choice of nonAA and nonAA.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.