From owner-freebsd-gnome@FreeBSD.ORG Tue Jan 29 20:45:49 2013 Return-Path: Delivered-To: gnome@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 22F2D2C1 for ; Tue, 29 Jan 2013 20:45:49 +0000 (UTC) (envelope-from gnome-jfbml@snkmail.com) Received: from sneak2.sneakemail.com (sneak2.sneakemail.com [38.113.6.65]) by mx1.freebsd.org (Postfix) with SMTP id 90ABF737 for ; Tue, 29 Jan 2013 20:45:47 +0000 (UTC) Received: (qmail 30873 invoked from network); 29 Jan 2013 20:45:46 -0000 Received: from unknown (HELO localhost.localdomain) (192.168.0.1) by sneak2.sneakemail.com with SMTP; 29 Jan 2013 20:45:46 -0000 Received: from 206.168.13.214 by mail.sneakemail.com with SMTP; 29 Jan 2013 20:45:46 -0000 Received: (sneakemail censored 26908-1359492334-209054 #2); 29 Jan 2013 20:45:46 -0000 Received: (sneakemail censored 26908-1359492334-209054 #1); 29 Jan 2013 20:45:46 -0000 Date: Tue, 29 Jan 2013 13:45:20 -0700 (MST) Message-ID: <26908-1359492334-209054@sneakemail.com> From: "John Hein" To: gnome@freebsd.org To: "Koop Mast" , "Sulabh Kausal" , MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: Script "configure" failed unexpectedly. In-Reply-To: <51082D73.90505@rainbow-runner.nl> References: <24831-1359488878-723419@sneakemail.com> <51082D73.90505@rainbow-runner.nl> X-Mailer: Perl5 Mail::Internet v X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2013 20:45:49 -0000 > the pth port isn't at fault here. Just rebuild python without the PTH > option selected should fix this. Well, if his python was built WITH_PTH at one point as it seems, then it does seem like a problem with the pth package now being missing or corrupted. Even if he rebuilds python _with_ the PTH option selected it should fix the issue, too. In this case, I guess it's a matter of semantics, but I blame the pth port (or the lack of it). Somehow his existing python port is expecting pth and is being brutally disappointed.