Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 6938A63668D for ; Sat, 11 Sep 2010 20:28:38 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 36523-02-5 for ; Sat, 11 Sep 2010 23:28:30 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from glacier.frostconsultingllc.com (glacier.frostconsultingllc.com [69.36.227.170]) by mail.postgresql.org (Postfix) with ESMTP id 962426361ED for ; Sat, 11 Sep 2010 20:11:56 -0300 (ADT) Received: from adsl-63-195-55-98.dsl.snfc21.pacbell.net ([63.195.55.98] helo=[192.168.47.100]) by glacier.frostconsultingllc.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.69) (envelope-from ) id 1OuZEc-00085K-GO; Sat, 11 Sep 2010 16:11:53 -0700 Message-ID: <4C8C0CAF.2050600@agliodbs.com> Date: Sat, 11 Sep 2010 16:11:43 -0700 From: Josh Berkus User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9pre) Gecko/20100217 Shredder/3.0.3pre MIME-Version: 1.0 To: James William Pye CC: pgsql-testers@postgresql.org Subject: Re: Configure/Build 9.0 rc1 - cannot build against python3.1, with two versions of python in the environment References: <5289151C-F7C2-4012-92F1-346FB9E1578F@comcast.net> <4C8BF66A.5020108@agliodbs.com> <1E79C9FD-5CA1-4194-BE88-417DE705EF6C@jwp.name> In-Reply-To: <1E79C9FD-5CA1-4194-BE88-417DE705EF6C@jwp.name> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201009/11 X-Sequence-Number: 187 >> I'm pretty sure this was hashed out on hackers, and turned out to be an issue with Python and not our fault. James? > > Nah, this isn't a Python issue. It's our configure script. So, is this a bug? Should we be fixing it before release? -- -- Josh Berkus PostgreSQL Experts Inc. http://www.pgexperts.com