From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8331 invoked by alias); 5 May 2008 13:10:49 -0000 Received: (qmail 8322 invoked by uid 22791); 5 May 2008 13:10:48 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 05 May 2008 13:10:29 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 61619980F7; Mon, 5 May 2008 13:10:27 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 3BAD998060; Mon, 5 May 2008 13:10:27 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1Jt0SY-00077p-FO; Mon, 05 May 2008 09:10:26 -0400 Date: Mon, 05 May 2008 14:39:00 -0000 From: Daniel Jacobowitz To: Thiago Jung Bauermann Cc: gdb-patches@sourceware.org Subject: Re: [RFC][patch 1/9] initial Python support Message-ID: <20080505131026.GB27076@caradoc.them.org> Mail-Followup-To: Thiago Jung Bauermann , gdb-patches@sourceware.org References: <20080429155212.444237503@br.ibm.com> <20080429155304.288626880@br.ibm.com> <1209963038.25743.14.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1209963038.25743.14.camel@localhost.localdomain> User-Agent: Mutt/1.5.17 (2007-12-11) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-05/txt/msg00204.txt.bz2 On Mon, May 05, 2008 at 01:50:38AM -0300, Thiago Jung Bauermann wrote: > % ../configure --with-libpython2.5-prefix=/blah > configure: error: invalid package name: libpython2.5-prefix Do we even want this option? The macro it comes from has been surprisingly troublesome and is very complicated. Maybe we just want --with-python, --without-python, and --with-python=/path. BTW, could you do me a favor... make GDB fail to build if --with-python is specified on the command line but Python could not be found. This is something I learned from working on Debian package builds and our own Sourcery G++ product builds. Autoconf configuration is not so good at producing consistent packages build after build. IMO the default should be "use python if we find it", but with --with-python it should be "use python or go boom". Anyway, . -- Daniel Jacobowitz CodeSourcery