Re: fontconfig-2.1.92 considered harmful

Is the problem during xclock execution or xclock compilation?

Anthony


On Tuesday 08 April 2003 15:27, Ruslan Ermilov wrote:
> On Tue, Apr 08, 2003 at 03:25:29PM +0200, CARTER Anthony wrote:
> > Originally (end of last week) there was a loop where the xft had a
>
> looping
>
> > dependency that caused an "out of swap space" bug appearing while
>
> compiling
>
> > Mesa (among others).
> >
> > What version of Xft are you using?
>
> Like I said, I rebuilt everything from ports yesterday.
> The latest, Xft-2.1_7.
>
> > Maybe it is not related, but I am running latest XFree and KDE and
>
> Xclock and
>
> > fontconfig without any problems so far ;)
>
> The WM is not an issue here.
>
> > On Tuesday 08 April 2003 15:18, Ruslan Ermilov wrote:
> > > On Tue, Apr 08, 2003 at 02:46:39PM +0200, CARTER Anthony wrote:
> > > > I had this bug, but now it is over...It has been fixed. Do a CVSUP
>
> and
>
> > > all
> > >
> > > > should now be ok.
> > >
> > > No.  This is with the latest port.  Where specifically it
> > > was fixed?
> > >
> > > > On Tuesday 08 April 2003 14:41, Ruslan Ermilov wrote:
> > > > > I have been unlucky to try to do a major update of all
> > > > > of my ports, including upgrading XFree86 to version 4.3,
> > > > > on my 5.0-CURRENT notebook.
> > > > >
> > > > > The update went fine except things like xclock(1) now
> > > > > angry and eat all system memory and are eventually get
> > > > > killed due to the ``out of swap space'' bug ;-).
> > > > >
> > > > > I've tracked it down to the update of fontconfig port
> > > > > to version 2.1.92.  Reverting to fontconfig-2.1_7 made
> > > > > the symptoms go away.
> > > > >
> > > > > This was a standard install of XFree86-4, with the
> > > > > xf86config(1) generated config file.
> > > > >
> > > > >
> > > > > Cheers,