From owner-freebsd-ports@FreeBSD.ORG Fri Mar 22 18:11:42 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id F1EF4AC1 for ; Fri, 22 Mar 2013 18:11:42 +0000 (UTC) (envelope-from freebsdml@marino.st) Received: from shepard.synsport.net (mail.synsport.com [208.69.230.148]) by mx1.freebsd.org (Postfix) with ESMTP id D2B5C721 for ; Fri, 22 Mar 2013 18:11:42 +0000 (UTC) Received: from [192.168.0.101] (unknown [130.255.28.143]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id 5D13643BBD for ; Fri, 22 Mar 2013 13:11:38 -0500 (CDT) Message-ID: <514C9ED1.4070601@marino.st> Date: Fri, 22 Mar 2013 19:11:29 +0100 From: John Marino User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0) Gecko/20120129 Thunderbird/10.0 MIME-Version: 1.0 To: freebsd-ports@freebsd.org Subject: Re: How to see errors with poudriere? References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Mar 2013 18:11:43 -0000 On 3/22/2013 18:51, J David wrote: > We are rapidly converting all of our ports-building infrastructure to > poudriere, which is a fantastic tool and has been a huge improvement for us. > > However, I do run across the occasional stubborn ports that refuse to build > (example: lang/ghc) under poudriere, and I'm not sure how to debug this. > > I am pretty sure this is possible/easy and I'm just being stupid. If > anyone would mind giving me a shove in the right direction, I would really > appreciate it. > I wouldn't be so quick to blame poudriere. There are many ports that won't build in poudriere due to problems with the port makefiles. In fact, I've only seen one legitimate case of a port that was fine but poudriere erroneously didn't build it. The rest were problems that poudriere flagged. You have to look at the log and see what the problem is, then report the problem via PR. e.g. look in /usr/local/poudriere/data/logs/.... John