From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14354 invoked by alias); 28 Jul 2010 17:27:49 -0000 Received: (qmail 14334 invoked by uid 22791); 28 Jul 2010 17:27:46 -0000 X-SWARE-Spam-Status: No, hits=-4.5 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; Wed, 28 Jul 2010 17:27:41 +0000 Received: from mailhost4.vmware.com (mailhost4.vmware.com [10.16.67.124]) by smtp-outbound-2.vmware.com (Postfix) with ESMTP id E22404000D; Wed, 28 Jul 2010 10:27:39 -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 D550FC9A0C; Wed, 28 Jul 2010 10:27:39 -0700 (PDT) Message-ID: <4C50688B.1050105@vmware.com> Date: Wed, 28 Jul 2010 17:27:00 -0000 From: Michael Snyder User-Agent: Thunderbird 2.0.0.22 (X11/20090609) MIME-Version: 1.0 To: Joel Brobecker CC: Tom Tromey , Thiago Jung Bauermann , "gdb-patches@sourceware.org" Subject: Re: 7.2 branch, configure problem, --with-python References: <4C4E1E0F.80309@vmware.com> <1280244591.2661.104.camel@hactar> <4C4F7A39.9030606@vmware.com> <20100728172017.GK13267@adacore.com> In-Reply-To: <20100728172017.GK13267@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/msg00489.txt.bz2 Joel Brobecker wrote: >> I wonder why that changed. Does your Python come with dynamic >> libraries? Did 7.1 choose those instead? AFAIK we didn't intentionally >> make any change to prefer static libraries -- I think that would be a >> bad decision. > > Perhaps the linker is not finding the python shared library? > I think it should. > > One thing we should be aware of is that it seems that the Python > developers themselves made the static libpython the default, and users > building python need to explicitly request the dynamic libpython for it > to be built. Maybe python-config.py is skewed that way too (meaning, > lack of testing with the dynamic version of libpython). > Ahhh... perhaps we're getting warm. 7.2 gdb/config.log links the conftest program with these args: -L/build/toolchain/lin64/python-2.5/lib/python2.5/config ... -lpython2.5 Whereas the equivalent args in 7.1 config.log are these: -L/build/toolchain/lin64/python-2.5/lib -lpython2.5 Notice the -L directory is different. The first one is where the static library is stored (7.2), and the second (7.1) is where the dynamic library is stored. What I don't know is, who made this change.