firefox 32bit still statically linked?

Olaus · 10-29-2009, 09:22 AM

(Sorry if this emerges as a double posting, the post disappeared on my side...)

According to http://www.vcn.bc.ca/~dugan/slackware-fonts/index.html:

Quote:

...the Firefox binary from mozilla.org is statically linked. This is, unfortunately, what's in 32-bit Slackware (64-bit Slackware has a custom-built Firefox package that is dynamically linked).

But when I run this on the ordinary, non-changed firefox from .../patches/packages

Code:

ldd /usr/lib/firefox-3.5.3/firefox-bin | grep free
        libfreetype.so.6 => /usr/lib/libfreetype.so.6

Doesn't this mean that firefox is NOT statically linked?

knudfl · 10-29-2009, 11:06 AM

ls -l /usr/lib/firefox-3.5.3/lib*
.. will show what's statically linked .. and their size ..
.. where the main lib 'libxul.so' is 14 MB.

But firefox also dynamically links to a lot of libraries,
that just by default are present on most *nix :

ldd /usr/lib/firefox-3.5.3/firefox-bin
.....

lumak · 10-29-2009, 11:07 AM

it may be partially statically linked? Maybe the mozilla libs themselves? try comparing the files in /lib and /lib64 of the two slackware packages.

dugan · 10-29-2009, 11:30 AM

Suffice to say, it is still necessary to recompile the 32-bit Firefox in order to get it to respect your subpixel rendering settings. I just checked.

Olaus · 10-29-2009, 12:30 PM

Quote:

Originally Posted by dugan

Suffice to say, it is still necessary to recompile the 32-bit Firefox in order to get it to respect your subpixel rendering settings. I just checked.

It seems that I get the same result at http://www.lagom.nl/lcd-test/subpixel.php for both the compiled and re-compiled version of firefox, are there any other sites to test firefox that should give me a different result? (I have 10-sub-pixel-rgb.conf in /etc/fonts/conf.d)
That is, how did you find out that the ordinary firefox doesn't follow your sub-pixel settings?

dugan · 10-29-2009, 05:16 PM

With the custom Freetype, Fontconfig and Cairo packages, you can tell the difference between the font rendering in the stock and rebuilt versions of Firefox just by looking at the menu bars.

http://img.photobucket.com/albums/v2...page/stock.png
http://img.photobucket.com/albums/v2...recompiled.png

I don't think it makes a difference if you're using the stock Freetype, Fontconfig and Cairo.

Olaus · 10-30-2009, 04:50 AM

Quote:

Originally Posted by dugan

With the custom Freetype, Fontconfig and Cairo packages, you can tell the difference between the font rendering in the stock and rebuilt versions of Firefox just by looking at the menu bars.

http://img.photobucket.com/albums/v2...page/stock.png
http://img.photobucket.com/albums/v2...recompiled.png

Ok, I have only recompiled freetype, that could be why I don't see any difference. By the way, is it only me who thinks that the text in the recompiled version looks blurrier than in the stock one?

Daedra · 10-30-2009, 05:11 AM

Why don't you just use the slackware64 firefox build to make a dynamically linked firefox package? Also I'm not positive but isn't cairo the problem library with statically linked firefox?

Olaus · 10-30-2009, 05:30 AM

Quote:

Originally Posted by Daedra

Why don't you just use the slackware64 firefox build to make a dynamically linked firefox package? Also I'm not positive but isn't cairo the problem library with statically linked firefox?

As I wrote, I HAVE done that, but I didn't see that much difference, maybe because I didn't also re-compile other libraries but freetype.

Daedra · 10-30-2009, 09:29 PM

Quote:

Originally Posted by Olaus

As I wrote, I HAVE done that, but I didn't see that much difference, maybe because I didn't also re-compile other libraries but freetype.

Sorry about that, I got to stop replying at 3:00 AM. If you just recompiled freetype then that could very well be your problem, you need cairo and libXft recompiled with the font patches to get the full sub-subpixel rendering effect. But you also have to configure fontconfig to enable it. Or you can just use a .fonts.conf file in your /home directory (that's what I usually do).