From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 913 invoked by alias); 28 Jul 2010 22:56:18 -0000 Received: (qmail 897 invoked by uid 22791); 28 Jul 2010 22:56:18 -0000 X-SWARE-Spam-Status: No, hits=-4.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from smtp-outbound-1.vmware.com (HELO smtp-outbound-1.vmware.com) (65.115.85.69) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 28 Jul 2010 22:56:14 +0000 Received: from mailhost4.vmware.com (mailhost4.vmware.com [10.16.67.124]) by smtp-outbound-1.vmware.com (Postfix) with ESMTP id C577713031; Wed, 28 Jul 2010 15:56:10 -0700 (PDT) Received: from msnyder-server.eng.vmware.com (promd-2s-dhcp138.eng.vmware.com [10.20.124.138]) by mailhost4.vmware.com (Postfix) with ESMTP id BBC4CC9A1C; Wed, 28 Jul 2010 15:56:10 -0700 (PDT) Message-ID: <4C50B58A.5080408@vmware.com> Date: Wed, 28 Jul 2010 22:56:00 -0000 From: Michael Snyder User-Agent: Thunderbird 2.0.0.22 (X11/20090609) MIME-Version: 1.0 To: Joel Brobecker CC: "gdb-patches@sourceware.org" Subject: Re: 7.2 branch, configure problem, --with-python References: <4C506FF0.3010405@vmware.com> <20100728180845.GT13267@adacore.com> <4C50728A.4090708@vmware.com> <20100728181926.GU13267@adacore.com> <4C507583.4010801@vmware.com> <20100728182734.GV13267@adacore.com> <4C508BE3.4000705@vmware.com> <4C508CD3.4070309@vmware.com> <4C508DE6.8020807@vmware.com> <4C50914E.1030408@vmware.com> <20100728213636.GX13267@adacore.com> In-Reply-To: <20100728213636.GX13267@adacore.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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: 2010-07/txt/msg00534.txt.bz2 Joel Brobecker wrote: >> So... aren't there some distro-related concerns about linking >> gdb against a static system library? > > I don't understand why you are seeing this. For instance, on my Ubuntu > distribution where the system python was installed with a shared > libpython, I see that GDB is correctly linked against a libpython.so > rather than linked with the archive: > > % ldd gdb > [...] > libpython2.6.so.1.0 => /usr/lib/libpython2.6.so.1.0 (0x00007fae940a8000) > [...] > > There must be something else in your case that causes the problem (?). > Hmmm, what if you try configure --with-python=/usr? That will approximate what I'm doing (only with me it's a non-standard install location). I see when I do that, gdb seems to be statically linked to the system python static library.