Date: Sun, 25 Jul 2004 19:57:31 +0200 From: Szilveszter Adam <sziszi@bsd.hu> To: freebsd-current@freebsd.org Subject: Re: Problem with xorg-vfbserver [and other -server] build[s] Message-ID: <20040725175731.GA815@momo.buza.adamsfamily.xx> In-Reply-To: <20040725153837.GA14282@panix.com> References: <20040724013156.GA18029@panix.com> <1090638211.44506.18.camel@leguin> <20040725153837.GA14282@panix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello,
On Sun, Jul 25, 2004 at 11:38:37AM -0400, Jesse Sheidlower wrote:
> I'm afraid I'm still having these problems with all of the
> xorg-{something}server ports, even after a forced reinstall
> of freetype2. For example, when I tried the latest xorg upgrade,
> I died on:
<...>
> I am able to install these as packages, and everything seems to be
> working neatly. However I'd love to figure out why this is happening.
>
> Anyone else having these problems? Anything else I can try to reinstall
> to help?
As I said in my previous msg to the list, this likely due to the fact
that later versions of XFree (and therefore likely X.org too) require
freetype2-2.1.8, which has some new APIs that the version in the ports
does not. I remember an error very much like this, when I attempted to
build a late XFree snapshot.
So, your best bet is to manually upgrade freetype2, without using the
port or wait until somebody does the upgrade of the port skeleton.
FWIW, the reason that it "worked" for eg the package building might be
probably that somehow the bundled freetype2 library got used, which is
at the right version.
While I do not have the X.org sources handy at the moment, this is worth
a check.
--
Regards:
Szilveszter ADAM
Budapest
Hungary
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040725175731.GA815>