Re: www/firefox3: font rendering regression with 3.0.9

[Jukka Salmi <j+nbsd%2009.salmi.ch@localhost>]

Tobias Nygren --> pkgsrc-users (2009-04-29 09:28:11 +0200):
> On Tue, 28 Apr 2009 23:39:06 +0200
> Jukka Salmi <j+nbsd%2009.salmi.ch@localhost> wrote:
> 
> > Hello,
> > 
> > after updating www/firefox3 from 3.0.7 to 3.0.9 on a NetBSD/i386 current
> > system I noticed a font rendering regression; e.g. the NetBSD home page
> > used to look like [1]this, but now looks like [2]this.
> > 
> > Any hints?
> 
> It renders correctly here. pkgsrc HEAD or 2009Q1?

HEAD.


> There's a 3.0.10 package now but I doubt it changes anything.

Indeed; I see the same problems with 3.0.10 as with 3.0.9.


> Also, is freetype2 builtin or from pkgsrc

Uh, firefox links against both builtin (I'm using XFree86 built from
HEAD xsrc) and pkgsrc freetype2:

$ ldd /usr/pkg/lib/firefox3/firefox-bin | grep freetype
        -lfreetype.6 => /usr/pkg/lib/libfreetype.so.6
        -lfreetype.9 => /usr/X11R6/lib/libfreetype.so.9

While I don't know whether this is a problem or not, it probably does not
cause the rendering problem I'm seeing: Firefox 3.0.7 also linked against
both freetype2 libraries and rendered fine.


> (and what PKG_OPTIONs in that case)?

I built graphics/freetype2 with options `subpixel' and `truetype'; the
builtin freetype2 was built with MKTTINTERP=yes.

Comparing the +BUILD_INFO files from the 3.0.7 and 3.0.9 packages I see
that the order of freetype2 include and library paths as they are passed to
compiler and linker respectively are different.  Some (hand-edited) diff(1)
output:

--- 307/+BUILD_INFO     2009-03-13 12:13:44.000000000 +0100
+++ 309/+BUILD_INFO     2009-04-24 16:29:08.000000000 +0200
[...]
-CFLAGS=-O2 -g -I/usr/pkg/include -I/usr/include -I/usr/pkg/include/freetype2 
-I/usr/pkg/include/python2.5 -I/usr/X11R6/include
+CFLAGS=-O2 -g -I/usr/pkg/include -I/usr/include -I/usr/X11R6/include 
-I/usr/pkg/include/freetype2 -I/usr/pkg/include/python2.5
[...]
-CPPFLAGS=[...] -I/usr/pkg/include/freetype2 [...] -I/usr/X11R6/include
+CPPFLAGS=[...] -I/usr/X11R6/include -I/usr/pkg/include/freetype2 [...]
[...]

Could this be the source of this problem?


Regards, Jukka

-- 
This email fills a much-needed gap in the archives.