From owner-freebsd-questions@FreeBSD.ORG Sun Jan 13 02:05:52 2013 Return-Path: Delivered-To: freebsd-questions@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 8DC95FD9 for ; Sun, 13 Jan 2013 02:05:52 +0000 (UTC) (envelope-from freebsd@chthonixia.net) Received: from www5.pairlite.com (www5.pairlite.com [64.130.10.15]) by mx1.freebsd.org (Postfix) with ESMTP id 5D1A01D3 for ; Sun, 13 Jan 2013 02:05:52 +0000 (UTC) Received: from whisperer.chthonixia.net (unknown [184.152.30.105]) by www5.pairlite.com (Postfix) with ESMTPSA id E64A22E2E0 for ; Sat, 12 Jan 2013 21:00:34 -0500 (EST) Date: Sat, 12 Jan 2013 21:01:14 -0500 From: Joe Altman To: freebsd-questions@freebsd.org Subject: Regarding: Script "configure" failed unexpectedly. Message-ID: <20130113020114.GA23658@whisperer.chthonixia.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jan 2013 02:05:52 -0000 Greetings... I was upgrading kino tonight, and the upgrade process failed and tossed this request at the tail of the error: ===> Script "configure" failed unexpectedly. Please report the problem to ports@FreeBSD.org [maintainer] and attach the "/usr/ports/multimedia/kino/work/kino-1.3.4/config.log" including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. a /usr/sbin/pkg_info -Ea). On January 2, the same thing happened and I did as requested...my email can be seen in the January 2013 thread in the mailing lists and seems unacknowledged. Looking at it, I saw (and remembered) send-pr as the method to use. My question: should a PR be opened on the "Script 'configure..." message, such that "use send-pr" instead of "send it to ports@" is used? I imagine this sort of problem is common. Regards, Joe Altman