Re: fontconfig-2.1.92 considered harmful

Joe Marcus Clarke wrote:
> 
> Both anholt and I were quick on the draw, but Eric beat me.  Checkout
> ports/50791 for an update to freetype2 which should alleviate this
> problem.

Not sure if this is related, but fc-cache coredumps when trying to 
upgrade to fontconfig-2.1.94 during the installation:

===>   Generating temporary packing list
Running fc-cache to build fontconfig cache...
[...snip...]
fc-cache: "/usr/X11R6/lib/X11/fonts/local": caching, 0 fonts, 0 dirs
fc-cache: "/usr/X11R6/lib/X11/fonts/misc": caching, 51 fonts, 0 dirs
fc-cache: "/usr/X11R6/lib/X11/fonts/util": caching, 0 fonts, 0 dirs
fc-cache: "/usr/X11R6/lib/X11/fonts/URW": caching, 35 fonts, 0 dirs
fc-cache: "/usr/X11R6/lib/X11/fonts/TrueType": Segmentation fault (core 
dumped)
*** Error code 139

Stop in /usr/ports/x11-fonts/fontconfig.

The directory /usr/X11R6/lib/X11/fonts/TrueType has a bunch of symlinks 
to my Windows TT fonts (under /windows/WINDOWS/Fonts/), and a fonts.dir 
and fonts.scale created by an rc.d script 
(http://www.isi.edu/larse/etc/rc.d/truetype).

This approach worked with all older fontconfig ports without problems, 
both on -stable and -current.

Any ideas?

Thanks,
Lars
-- 
Lars Eggert <larse_at_isi.edu>           USC Information Sciences Institute