From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4458 invoked by alias); 29 Jul 2010 21:45:18 -0000 Received: (qmail 4449 invoked by uid 22791); 29 Jul 2010 21:45:17 -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-2.vmware.com (HELO smtp-outbound-2.vmware.com) (65.115.85.73) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 29 Jul 2010 21:45:11 +0000 Received: from mailhost2.vmware.com (mailhost2.vmware.com [10.16.67.167]) by smtp-outbound-2.vmware.com (Postfix) with ESMTP id 53C35300B; Thu, 29 Jul 2010 14:45:10 -0700 (PDT) Received: from msnyder-server.eng.vmware.com (promd-2s-dhcp138.eng.vmware.com [10.20.124.138]) by mailhost2.vmware.com (Postfix) with ESMTP id 4C0A58E777; Thu, 29 Jul 2010 14:45:10 -0700 (PDT) Message-ID: <4C51F665.5000305@vmware.com> Date: Thu, 29 Jul 2010 21:45: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: <4C50914E.1030408@vmware.com> <20100728213636.GX13267@adacore.com> <4C50B58A.5080408@vmware.com> <20100729152827.GZ13267@adacore.com> <4C51BC60.1040104@vmware.com> <4C51BFEE.20602@vmware.com> <20100729184046.GB13267@adacore.com> <4C51CD34.8040501@vmware.com> <20100729190439.GC13267@adacore.com> <4C51D71C.2080302@vmware.com> <20100729213219.GD13267@adacore.com> In-Reply-To: <20100729213219.GD13267@adacore.com> Content-Type: text/plain; charset=ISO-8859-1; 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/msg00563.txt.bz2 Joel Brobecker wrote: >>> The bottom line, IMO, is that you python install is simply broken. >> It works fine with gdb-7.1 (dynamically linked)... > > If it works with 7.1, I think it was by accident (IMO). > >> Um, no, it appears to be linked statically. >> What about yours (the 2.7 version that you built)? > > Exactly what I thought. Mine shows a dynamic dependency on libpython.so. > > I really think that the problem is with your Python install. If you want > to be able to link dynamically with your python install, you'll have to > add a link to libpython.so in your lib/python-/config directory. > The problem is that your python binary was built without --enable-shared > and thus Python itself believes that there is no libpython.so. And > because of that, it is telling the GDB configure to use the static > archive. The Ubuntu python install is equally broken (IMO), but it > happens to work because there is a copy of the the libpython.so in > the config/ directory as well. > OK, I'm on the same page. Thanks!