From owner-freebsd-gnome@FreeBSD.ORG Sun Feb 2 21:25:15 2014 Return-Path: Delivered-To: gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C36A2542 for ; Sun, 2 Feb 2014 21:25:15 +0000 (UTC) Received: from fep22.mx.upcmail.net (fep22.mx.upcmail.net [62.179.121.42]) by mx1.freebsd.org (Postfix) with ESMTP id 0F489111A for ; Sun, 2 Feb 2014 21:25:14 +0000 (UTC) Received: from edge02.upcmail.net ([192.168.13.237]) by viefep22-int.chello.at (InterMail vM.8.01.05.05 201-2260-151-110-20120111) with ESMTP id <20140202212514.IJUL13097.viefep22-int.chello.at@edge02.upcmail.net>; Sun, 2 Feb 2014 22:25:14 +0100 Received: from crashalot.rainbow-runner.nl ([178.84.134.112]) by edge02.upcmail.net with edge id MZRD1n0062Rg3Ey02ZRDzm; Sun, 02 Feb 2014 22:25:14 +0100 X-SourceIP: 178.84.134.112 Message-ID: <52EEB7A8.9000909@rainbow-runner.nl> Date: Sun, 02 Feb 2014 22:24:56 +0100 From: Koop Mast User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Reed Loefgren , gnome@FreeBSD.org Subject: Re: FreeBSD Port: textproc/gtk-doc References: <52ED3725.2040700@forethought.net> In-Reply-To: <52ED3725.2040700@forethought.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Feb 2014 21:25:15 -0000 On 01/02/2014 19:04, Reed Loefgren wrote: > Hi! > > Just a heads-up that I'm getting a build failure on textproc/gtk-doc. > This cascades to docbook-sk and then midori, which is what I'm after. I > really don't care if I get any docbook docs so if this can be hashed out > in a config or Makefile I'd be OK with it. :) > > Otherwise, just sayin'. > > Regards, > > Reed Loefgren Hi, Normally parsing the error message (and probably a few lines before it happened) will help us understand more about likely causes. We like to have our ports working without any hacks. And as you noted it probably is a issue regarding the docbook ports. -Koop