From owner-freebsd-gnome@FreeBSD.ORG Tue Oct 10 18:40:32 2006 Return-Path: X-Original-To: freebsd-gnome@freebsd.org Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C6AED16A40F for ; Tue, 10 Oct 2006 18:40:32 +0000 (UTC) (envelope-from piotr.smyrak@heron.pl) Received: from mail.heron.pl (sys.heron.com.pl [89.174.255.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4380C43D5E for ; Tue, 10 Oct 2006 18:40:31 +0000 (GMT) (envelope-from piotr.smyrak@heron.pl) Received: from [127.0.0.1] (helo=poczta.heron.pl) by mail.heron.pl with esmtp (Exim 4.63) (envelope-from ) id 1GXMVj-000N53-So for freebsd-gnome@freebsd.org; Tue, 10 Oct 2006 20:39:28 +0200 From: piotr.smyrak@heron.pl To: freebsd-gnome@freebsd.org Date: Tue, 10 Oct 2006 20:39:27 +0200 Message-Id: <20061010174255.M97635@heron.pl> In-Reply-To: <1160495442.493.16.camel@shumai.marcuscom.com> References: <20061010141519.M63088@heron.pl> <1160495442.493.16.camel@shumai.marcuscom.com> X-Mailer: WebMail at HERON 2.32 20040813 X-OriginatingIP: 87.206.103.51 (smyru) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Subject: Re: hal not calling dbus-glib to install X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Oct 2006 18:40:32 -0000 On Tue, 10 Oct 2006 11:50:42 -0400, Joe Marcus Clarke wrote > On Tue, 2006-10-10 at 16:20 +0200, piotr.smyrak@heron.pl wrote: > > > > I was just upgrading 2.16 with Marcus repo and it seems to me that > > sysutils/hal should call devel/dbus-glib to install, since it > > breaks on configure stage: > > Must be something on your machine as I have now built > GNOME 2.16.1 successfully in Tinderbox for 6.1, 5.5, 6- > STABLE, and 5-STABLE (well, I've built hal). Where is hal's dbus-glib dependency defined? I fail to see it in Makefile, and ports/Mk/*. The only nested one I see is through devel/py-dbus but it is just for the slave port and its a RUN_DEPENDS so it is not checked until from within the install target. And port build dies at the configure stage. Please CC me, if replying. Thanks, -- Piotr Smyrak piotr.smyrak@heron.pl