From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10794 invoked by alias); 17 Sep 2012 16:24:47 -0000 Received: (qmail 10769 invoked by uid 22791); 17 Sep 2012 16:24:39 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from smarthost02.mail.zen.net.uk (HELO smarthost02.mail.zen.net.uk) (212.23.1.2) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 17 Sep 2012 16:24:14 +0000 Received: from [82.71.15.62] (helo=[192.168.123.72]) by smarthost02.mail.zen.net.uk with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1TDe7J-00074G-MH for gdb@sourceware.org; Mon, 17 Sep 2012 16:24:13 +0000 Message-ID: <50574EAD.3040504@greglaw.net> Date: Mon, 17 Sep 2012 16:24:00 -0000 From: Greg Law User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: gdb@sourceware.org Subject: CVS builds not working with Python? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Originating-Smarthost02-IP: [82.71.15.62] X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2012-09/txt/msg00048.txt.bz2 Hi list, I can't seem to get a build of gdb from cvs to work properly with Python. When I start gdb I get a warning message, and an attempt to import gdb from Python generates an exception, like so: $ ./gdb/gdb -q Python Exception No module named gdb: warning: Could not load the Python gdb module from `/usr/local/share/gdb/python'. warning: Limited Python support is available from the _gdb module. (gdb) python >import gdb >end Traceback (most recent call last): File "", line 1, in ImportError: No module named gdb Error while executing Python code. (gdb) This worked until recently. I've tried it with a clean checkout from two different machines (one CentOS and one Ubuntu) and they both show the problem. I've tried passing --with-python to configure, but it seems to make no difference. Am I doing something wrong, or has something rotted here recently? Greg