Fix install location for Python bindingscpumask-v2cpumask-v3
commitbdbb7aa1239a35c8b9c96d2aa59251cd8be0bdc1
authorMatthias Bolte <[email protected]>
Fri, 11 Dec 2009 23:11:31 +0000 (12 00:11 +0100)
committerMatthias Bolte <[email protected]>
Mon, 14 Dec 2009 21:14:06 +0000 (14 22:14 +0100)
tree869e8798fa1c0e6d3335bf1be9e61f5129089163
parent6d1c8a436dc5b543ba2ad56b453a34ce43d9ba14
Fix install location for Python bindings

Commit 66137344feb488ea87b0d92f3c03844d9a7a7786 changed the Python detection
mechanism in configure to use AM_PATH_PYTHON. This results in a changed
install location for the Python bindings, at least on Fedora 12 64bit systems.

Before this commit libvirt.py and libvirtmod.so were installed to

  /usr/lib64/python2.6/site-packages

After this commit they are installed to

  /usr/lib/python2.6/site-packages

Mixed Python packages (containing *.py and *.so files) should be installed to
the pyexecdir directory detected by AM_PATH_PYTHON.

This restores the install location from before the AM_PATH_PYTHON commit.

* configure.in: remove unnecessary pythondir export
* python/Makefile.am: switch from pythondir to pyexecdir
Makefile.am