From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18988 invoked by alias); 28 Jul 2010 20:07:10 -0000 Received: (qmail 18978 invoked by uid 22791); 28 Jul 2010 20:07:10 -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 20:07:03 +0000 Received: from mailhost2.vmware.com (mailhost2.vmware.com [10.16.67.167]) by smtp-outbound-1.vmware.com (Postfix) with ESMTP id 844FF1307A; Wed, 28 Jul 2010 13:07:02 -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 796F28E77E; Wed, 28 Jul 2010 13:07:02 -0700 (PDT) Message-ID: <4C508DE6.8020807@vmware.com> Date: Wed, 28 Jul 2010 20:07: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: <4C4F7A39.9030606@vmware.com> <20100728172017.GK13267@adacore.com> <4C50688B.1050105@vmware.com> <20100728173706.GO13267@adacore.com> <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> In-Reply-To: <4C508CD3.4070309@vmware.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/msg00518.txt.bz2 Michael Snyder wrote: > Michael Snyder wrote: >> Joel Brobecker wrote: >>>> Are we talking about the same patch? >>> Yep! >> I see -- I need to apply both changes to the branch. >> >> Well, that didn't help, and neither did applying the one change to HEAD. >> >> I tried configuring both with and without --enable-shared. >> >> In all cases, it tried to link statically. >> >> I'm thinking, if gdb links against python statically, that will >> certainly bloat the gdb executable... >> > > Hmmm, yes, unstripped gdb-7.2 is about 6 meg bigger than 7.1. And even stripped, gdb is now 32 percent bigger.