From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13010 invoked by alias); 28 Jul 2010 16:56:17 -0000 Received: (qmail 12998 invoked by uid 22791); 28 Jul 2010 16:56:16 -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 16:56:12 +0000 Received: from mailhost2.vmware.com (mailhost2.vmware.com [10.16.67.167]) by smtp-outbound-2.vmware.com (Postfix) with ESMTP id EABEC5301D; Wed, 28 Jul 2010 09:56:08 -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 DF70B8E77E; Wed, 28 Jul 2010 09:56:08 -0700 (PDT) Message-ID: <4C506128.9040108@vmware.com> Date: Wed, 28 Jul 2010 16:56:00 -0000 From: Michael Snyder User-Agent: Thunderbird 2.0.0.22 (X11/20090609) MIME-Version: 1.0 To: Tom Tromey CC: 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> In-Reply-To: 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/msg00485.txt.bz2 Tom Tromey wrote: > Michael> So this problem shows up because we've switched to static linking > Michael> (at least for configure). > > I wonder why that changed. Me too. > Does your Python come with dynamic libraries? Yep. > Did 7.1 choose those instead? Yep. > AFAIK we didn't intentionally make any change to prefer static libraries -- That's odd, because it seems like a non-trivial change was required. > I think that would be a bad decision. Me too. Both 7.1 and 7.2 use "ac_fn_c_try_link", which is locally defined in configure. In configure.ac, it appears to be AC_TRY_LIBPYTHON.