From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14295 invoked by alias); 28 Jul 2010 21:36:49 -0000 Received: (qmail 14283 invoked by uid 22791); 28 Jul 2010 21:36:48 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 28 Jul 2010 21:36:44 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 9CBDD2BAC07; Wed, 28 Jul 2010 17:36:42 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id NDE6wTmXqpOE; Wed, 28 Jul 2010 17:36:42 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 6B6122BAC02; Wed, 28 Jul 2010 17:36:42 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id C37B2F58FA; Wed, 28 Jul 2010 14:36:36 -0700 (PDT) Date: Wed, 28 Jul 2010 21:36:00 -0000 From: Joel Brobecker To: Michael Snyder Cc: "gdb-patches@sourceware.org" Subject: Re: 7.2 branch, configure problem, --with-python Message-ID: <20100728213636.GX13267@adacore.com> 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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4C50914E.1030408@vmware.com> User-Agent: Mutt/1.5.20 (2009-06-14) 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/msg00526.txt.bz2 > 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 (?). -- Joel