From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18734 invoked by alias); 21 Sep 2012 16:01:31 -0000 Received: (qmail 18724 invoked by uid 22791); 21 Sep 2012 16:01:29 -0000 X-SWARE-Spam-Status: No, hits=-6.6 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 21 Sep 2012 16:01:12 +0000 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q8LG18nQ020955 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 21 Sep 2012 12:01:08 -0400 Received: from host2.jankratochvil.net (ovpn-113-58.phx2.redhat.com [10.3.113.58]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q8LG14EQ010930 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 21 Sep 2012 12:01:07 -0400 Date: Fri, 21 Sep 2012 16:01:00 -0000 From: Jan Kratochvil To: Meador Inge Cc: Joel Brobecker , gdb@sourceware.org Subject: Re: Using Py_SetPythonHome Message-ID: <20120921160103.GA31526@host2.jankratochvil.net> References: <50511945.2070400@codesourcery.com> <20120917170657.GB5716@adacore.com> <505C8DC7.5090104@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <505C8DC7.5090104@codesourcery.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-IsSubscribed: yes 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/msg00065.txt.bz2 On Fri, 21 Sep 2012 17:54:47 +0200, Meador Inge wrote: > We distribute the toolchain with a layout that looks like: > > bin/ > $cross-gdb > lib/ > libpython2.6.so.1.0 > python2.6/ > python26.zip Sorry but this is very custom setup of GDB. In such case GDB should be configured with special configure option for it (if any, IMO it should be rather a vendor patch). Unaware why such custom setup should complicate usage of GDB by all the users on regular GNU/Linux systems. It is normal nowadays to use various virtualizations and chroot setups (like I also do) and one does not expect called GDB does not follow standard PYTHONHOME/PYTHONPATH/LD_LIBRARY_PATH environment variables like all the other system binaries do. I believe these arguments just repeat the discussion several months old, without any new facts brought in. Regards, Jan