Error in fontconfig
kstewart at owt.com
Mon Apr 14 09:53:11 PDT 2003
On Monday 14 April 2003 01:44 am, Roger Merritt wrote:
> At 03:02 PM 4/14/03, you wrote:
> >On Sunday 13 April 2003 11:10 pm, Roger Merritt wrote:
> > > I've been trying to update fontconfig for some time now. I've
> > > re-cvsupped
> > >
> > > over the last three weeks or so, but I keep getting the same
> > > >fc-cache: "/usr/X11R6/lib/X11/fonts/latin2": caching, 0 fonts, 2
> > > > dirs fc-cache: "/usr/X11R6/lib/X11/fonts/latin2/100dpi":
> > > > caching, 0 fonts, 0 dirs fc-cache:
> > > > "/usr/X11R6/lib/X11/fonts/latin2/75dpi": caching, 0 fonts, 0
> > > > dirs fc-cache: "/usr/X11R6/lib/X11/fonts/util": caching, 0
> > > > fonts, 0 dirs fc-cache:
> > > > "/usr/X11R6/lib/X11/fonts/TrueType": Segmentation fault (core
> > > > dumped)
> > > >*** Error code 139
> > > >
> > > >Stop in /usr/home/ports/x11-fonts/fontconfig.
> > > >*** Error code 1
> > >
> > > The error always occurs at the same place. What should I try
> > > doing?
> >I would cvsup again and rebuilt your INDEX files. There were some
> >problems with memory leakage that was using up all of your swap and
> >dying. Your segmentation fault could be that problem. The latest
> >version is fontconfig-2.1.93. Freetype2 was recently updated and
> > that is one of your build-dependancies.
> I'll give it another try. Good heavens, I just cvsupped again on
> Friday and the port I have is fontconfig-2.1_6!
I would suspect that something is wrong with your port cvsup setup. The
previous version was 2.1.92 (4 Apr) and the next one back was 2.1_7 (28
Mar). Version 2.1_7 fixed a bug in fontconfig's configure script that
was causing crashes.
If you aren't rebuilding your INDEX* files after you cvsup, you are
using an INDEX dated 29 Mar.
More information about the freebsd-questions