From owner-freebsd-current@FreeBSD.ORG  Sun Jul 25 19:14:06 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3A39E16A4CE
	for <freebsd-current@freebsd.org>;
	Sun, 25 Jul 2004 19:14:06 +0000 (GMT)
Received: from gate.bitblocks.com (bitblocks.com [209.204.185.216])
	by mx1.FreeBSD.org (Postfix) with ESMTP id CFF4B43D4C
	for <freebsd-current@freebsd.org>;
	Sun, 25 Jul 2004 19:14:05 +0000 (GMT)
	(envelope-from bakul@bitblocks.com)
Received: from bitblocks.com (localhost [127.0.0.1])
	by gate.bitblocks.com (8.12.11/8.12.10) with ESMTP id i6PJE5KF005605
	for <freebsd-current@freebsd.org>;
	Sun, 25 Jul 2004 12:14:05 -0700 (PDT)
	(envelope-from bakul@bitblocks.com)
Message-Id: <200407251914.i6PJE5KF005605@gate.bitblocks.com>
To: freebsd-current@freebsd.org
In-reply-to: Your message of "Sun, 25 Jul 2004 21:06:11 +0200."
             <200407252106.12192.dejan.lesjak@ijs.si> 
Date: Sun, 25 Jul 2004 12:14:05 -0700
From: Bakul Shah <bakul@BitBlocks.com>
Subject: Re: Problem with xorg-vfbserver [and other -server] build[s] 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Jul 2004 19:14:06 -0000

> > I looked at X.org CVSweb, and they also have freetype2-2.1.8 in there.
> > Also, I tried looking at the port skeleton for xorg ports, but maybe I
> > did not understand it? There does not appear any steps to *not* use the
> > bundled freetype library during the build. Maybe it does not get
> > installed in the end, but this may be a reason why the package builds
> > suceed... in any event, I had to add "magic" lines in my host.def in
> > order to skip the bundled freetype library in favor of the system one,
> > and it works for me...

Chances are, you have an older libfreetype in /usr/X11R6/lib
(libfreetype.9 gets installed in /usr/local/lib)
so
    rm /usr/X11R6/lib/libfreetype.*
and try again.