From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7411 invoked by alias); 17 Sep 2012 17:07:16 -0000 Received: (qmail 7402 invoked by uid 22791); 17 Sep 2012 17:07:14 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_HOSTKARMA_NO 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; Mon, 17 Sep 2012 17:07:02 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 2AB861C7B2B; Mon, 17 Sep 2012 13:07:01 -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 987R0y9S18ES; Mon, 17 Sep 2012 13:07:01 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id ED9D21C7B2A; Mon, 17 Sep 2012 13:07:00 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id F2FAEC711F; Mon, 17 Sep 2012 10:06:57 -0700 (PDT) Date: Mon, 17 Sep 2012 17:07:00 -0000 From: Joel Brobecker To: Meador Inge Cc: gdb@sourceware.org Subject: Re: Using Py_SetPythonHome Message-ID: <20120917170657.GB5716@adacore.com> References: <50511945.2070400@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50511945.2070400@codesourcery.com> User-Agent: Mutt/1.5.21 (2010-09-15) Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2012-09/txt/msg00050.txt.bz2 > The use case I am having trouble with is the one where gdb gets > shipped with: (1) its own pythonxy.so, (2) a zipped standard library, > and (3) a directory for the standard library module shared libraries. > In this case, Py_SetPythonHome needs to be called before Py_Initialize > so that the standard library pieces can even be found (Py_Initialize > does some imports). Not sure what (2) and (3) are... > Is there another way around the problem I am having? Have the feelings > concerning Py_SetPythonHome changed since comments in [1] ? > > [1] http://sources.redhat.com/ml/gdb-patches/2010-11/msg00328.html ... The proposed patch has been working flawlessly for us since I installed it in AdaCore's tree, but as far as I know, there has been no change of heart regarding its inclusion in the FSF tree. I believe Jan contacted the Python developers, and their answer seemed to go in Jan's direction. -- Joel