From owner-freebsd-questions@FreeBSD.ORG Tue May 6 20:32:01 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D1E391065670 for ; Tue, 6 May 2008 20:32:01 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from snoogles.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id 9B8B28FC15 for ; Tue, 6 May 2008 20:32:01 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from localhost (localhost [127.0.0.1]) by snoogles.rachie.is-a-geek.net (Postfix) with ESMTP id 88A7F1CD4A; Tue, 6 May 2008 12:32:00 -0800 (AKDT) From: Mel To: freebsd-questions@freebsd.org, stevefranks@ieee.org Date: Tue, 6 May 2008 22:31:41 +0200 User-Agent: KMail/1.9.7 References: <539c60b90805061313g2c0a7232n2a065cf1190dbb30@mail.gmail.com> In-Reply-To: <539c60b90805061313g2c0a7232n2a065cf1190dbb30@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200805062231.42315.fbsd.questions@rachie.is-a-geek.net> Cc: Subject: Re: configure: how to tell what options were used X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 May 2008 20:32:01 -0000 On Tuesday 06 May 2008 22:13:47 Steve Franks wrote: > I think I'm having problems with a port due to a sub-port having > incorrect configure options. Anyone know how to find out what those > might have been? I'm not seeing a standard way to find that out... Don't clean the build, then: make all-depends-list | while read DIR; do cd ${DIR} configlog=$(make -V WRKSRC)/config.log if test -f ${configlog}; then echo ${configlog} fi done | xargs ${EDITOR} Then have fun finding the problem in the logs. Without knowing what to look for, that can be tedious. -- Mel Problem with today's modular software: they start with the modules and never get to the software part.