From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2658 invoked by alias); 1 Jun 2010 20:53:42 -0000 Received: (qmail 2648 invoked by uid 22791); 1 Jun 2010 20:53:41 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 01 Jun 2010 20:53:31 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 41A352BAC5D; Tue, 1 Jun 2010 16:53:29 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id rn5MAxnv7WYW; Tue, 1 Jun 2010 16:53:29 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id F18B52BAC5C; Tue, 1 Jun 2010 16:53:28 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 74C66F58FA; Tue, 1 Jun 2010 13:53:25 -0700 (PDT) Date: Tue, 01 Jun 2010 20:53:00 -0000 From: Joel Brobecker To: Doug Evans Cc: tromey@redhat.com, gdb-patches@sourceware.org Subject: Re: [RFA/python:1/2] Add support for --with-pythondir. Message-ID: <20100601205325.GR3019@adacore.com> References: <1274918921-23200-1-git-send-email-brobecker@adacore.com> <1274918921-23200-2-git-send-email-brobecker@adacore.com> <20100528160818.GN3019@adacore.com> <20100601201537.GQ3019@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) 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: 2010-06/txt/msg00023.txt.bz2 > I don't have any concerns other than those expressed. > They're not showstoppers or anything, I just want to make sure that > if/when the time comes to add --with-python-sodir (or some such), it's > not willy-nilly shot down because of the claim that there are already > too many configure options. Aaaah - I see where you are coming from now. Personally, I certainly would not object. The number of configure options can indeed be somewhat of a concern (I'm slightly concerned about the distinction between the gdb-pythonlib path, and the python path), but nothing blocking. At worst, I think we can do without the configure option, by forcing the lib-dynload directory to be inside the gdb-pythonlib. WDYT? I need to discuss the second patch with Tom anyways, so I'll wait a few more days, to see if anyone else would like to comment on this. -- Joel