From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28650 invoked by alias); 20 May 2010 18:54:53 -0000 Received: (qmail 28641 invoked by uid 22791); 20 May 2010 18:54:52 -0000 X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 20 May 2010 18:54:44 +0000 Received: (qmail 21817 invoked from network); 20 May 2010 18:54:43 -0000 Received: from unknown (HELO caradoc.them.org) (dan@127.0.0.2) by mail.codesourcery.com with ESMTPA; 20 May 2010 18:54:43 -0000 Date: Thu, 20 May 2010 19:03:00 -0000 From: Daniel Jacobowitz To: Joel Brobecker Cc: gdb-patches@sourceware.org Subject: Re: Add LIBDIR/gdb/python- to Python search path Message-ID: <20100520185436.GA24123@caradoc.them.org> Mail-Followup-To: Joel Brobecker , gdb-patches@sourceware.org References: <1274380803-25266-1-git-send-email-brobecker@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1274380803-25266-1-git-send-email-brobecker@adacore.com> 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-05/txt/msg00438.txt.bz2 On Thu, May 20, 2010 at 11:40:01AM -0700, Joel Brobecker wrote: > The intent is to allow us to package up a GDB binary with python support. > Since we do not know whether the target system on which GDB is going to > be installed has the correct version of python (or even if it has, whether > it has been built correctly), we want to also package up the python > library as well. That way, regardless of what the target system provides, > we know the debugger will be using a well-defined version of the python > library. > > The location I chose for that is GDB_LIBDIR/python-, where > GDB_LIBDIR is LIBDIR/gdb by default. So, for instance, with a prefix > set to /my/prefix/dir, a default GDB_LIDIR, and Python version 2.5, > we'd be using: /my/prefix/dir/lib/gdb/python-2.5. I have a not-as-nice local patch to achieve a similar goal, so I'm in favor. But what do you see as the role of GDB_LIBDIR, other than this? GDB isn't the only program in our distribution that needs an included Python, so we're not going to put it in lib/gdb. But it'd be nice to have other GDB-private data outside of top-level lib/. -- Daniel Jacobowitz CodeSourcery