From owner-freebsd-gnome@FreeBSD.ORG  Tue Aug 24 01:31:14 2010
Return-Path: <owner-freebsd-gnome@FreeBSD.ORG>
Delivered-To: gnome@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 1BEAD1065670
	for <gnome@FreeBSD.org>; Tue, 24 Aug 2010 01:31:14 +0000 (UTC)
	(envelope-from jason@naughton.ca)
Received: from trooper.jnaughton.com (naughton.ca [206.248.137.184])
	by mx1.freebsd.org (Postfix) with ESMTP id AE3CB8FC0A
	for <gnome@FreeBSD.org>; Tue, 24 Aug 2010 01:31:07 +0000 (UTC)
Received: from webmail.jnaughton.com (localhost [127.0.0.1])
	by trooper.jnaughton.com (8.14.4/8.14.4) with ESMTP id o7O1TqVw002240
	for <gnome@FreeBSD.org>; Mon, 23 Aug 2010 21:29:52 -0400 (EDT)
	(envelope-from jason@naughton.ca)
Received: from 192.168.1.2 (SquirrelMail authenticated user jnaughto)
	by webmail.jnaughton.com with HTTP; Mon, 23 Aug 2010 21:29:52 -0400
Message-ID: <735a8408306c615af1083174258c04e2.squirrel@webmail.jnaughton.com>
Date: Mon, 23 Aug 2010 21:29:52 -0400
From: "Jason Naughton" <jason@jnaughton.com>
To: gnome@FreeBSD.org
User-Agent: SquirrelMail/1.4.20-RC2
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Cc: 
Subject: pango compiles
X-BeenThere: freebsd-gnome@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: GNOME for FreeBSD -- porting and maintaining
	<freebsd-gnome.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-gnome>,
	<mailto:freebsd-gnome-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-gnome>
List-Post: <mailto:freebsd-gnome@freebsd.org>
List-Help: <mailto:freebsd-gnome-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-gnome>,
	<mailto:freebsd-gnome-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Aug 2010 01:31:14 -0000

Hi All,

Please ignore my last post.  It seems that

gobject-introspection-0.6.7

needed updating.  After updating this port to version 0.6.14 the
problem went away.

Cheers

Jason