CVS builds not working with Python?

CVS builds not working with Python?

[Greg Law]

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 <type 'exceptions.ImportError'> 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 "<string>", line 1, in <module>
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

Re: CVS builds not working with Python?

[Jan Kratochvil]

On Mon, 17 Sep 2012 18:24:13 +0200, Greg Law wrote:
> 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:

It is because your system GDB Python scripts directory is too old for FSF GDB
HEAD as updated + analysed by Khoo Yit Phang.
	Re: Regression for --batch [Re: [RFC] Make python/lib/gdb and submodules proper Python modules]
	http://sourceware.org/ml/gdb-patches/2012-09/msg00266.html
	http://sourceware.org/ml/gdb-patches/2012-09/txt00010.txt

Use:
$ ./gdb -data-directory ./data-directory


Regards,
Jan