From owner-freebsd-ports@FreeBSD.ORG Tue Dec 7 02:27:57 2010 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7C76C1065670 for ; Tue, 7 Dec 2010 02:27:57 +0000 (UTC) (envelope-from corky1951@comcast.net) Received: from qmta10.emeryville.ca.mail.comcast.net (qmta10.emeryville.ca.mail.comcast.net [76.96.30.17]) by mx1.freebsd.org (Postfix) with ESMTP id 685608FC19 for ; Tue, 7 Dec 2010 02:27:57 +0000 (UTC) Received: from omta22.emeryville.ca.mail.comcast.net ([76.96.30.89]) by qmta10.emeryville.ca.mail.comcast.net with comcast id fpQn1f0011vN32cAA2Tw7E; Tue, 07 Dec 2010 02:27:57 +0000 Received: from comcast.net ([98.203.142.76]) by omta22.emeryville.ca.mail.comcast.net with comcast id g2Tv1f0021f6R9u8i2TvQg; Tue, 07 Dec 2010 02:27:56 +0000 Received: by comcast.net (sSMTP sendmail emulation); Mon, 06 Dec 2010 18:27:54 -0800 Date: Mon, 6 Dec 2010 18:27:54 -0800 From: Charlie Kester To: freebsd-ports@freebsd.org Message-ID: <20101207022753.GB5042@comcast.net> Mail-Followup-To: freebsd-ports@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline X-Mailer: Mutt 1.5.20 X-Composer: Vim 7.2 User-Agent: Mutt/1.5.20 (2009-06-14) Subject: failed configure of multimedia/handbrake X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2010 02:27:57 -0000 I'm getting a strange error while trying to install the handbrake port: ===> Configuring for handbrake-0.9.3 sed: /usr/ports/multimedia/handbrake/work/HandBrake-0.9.3//usr/ports/multimedia/handbrake/work/HandBrake-0.9.3/configure: No such file or directory *** Error code 1 Stop in /usr/ports/multimedia/handbrake. Looking at the port Makefile and bsd.port.mk, I can't see why sed is being run here. Nor can I see why ${WRKSRC} is appearing twice in the path to the configure script. Any ideas?