Python modules installed to wrong location

[Jonathan Underwood]

Currently, the python modules end up getting installed, on a 64 bit system redhat/fedora, to:

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

which I think is incorrect - the python modules are architecture independent, and so should go under

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

[note lib vs lib64].

The reason for this is in CMakeLists.txt, the python module path is set up using:

python -c -c "import sys, distutils.sysconfig; sys.stdout.write(distutils.sysconfig.get_python_lib(plat_specific=True, prefix='${CMAKE_INSTALL_PREFIX}'))"

which I think should be:

-c "import sys, distutils.sysconfig; sys.stdout.write(distutils.sysconfig.get_python_lib(plat_specific=False, prefix='${CMAKE_INSTALL_PREFIX}'))"

Have attached a (trivial) patch which fixes this.

[Garth Wells (garth-wells)]

I haven't tested yet, but this looks like it will put everything in /usr/lib/...., whereas it should only be 'ufc_utils' since 'ufc' has some compiled code.

[Jonathan Underwood (jonathan-underwood)]

Hm, right, I did wonder about this. For some reason, when I build it, no compiled code is created (despite the fact that swig (version 2.0.5) is installed). Perhaps this is due to using CMake 2.6. Will investigate, but any pointers welcome.

[Jonathan Underwood (jonathan-underwood)]

Commit 348 nearly fixes this... but not quite. The one liner attached finishes the job.

[Johannes Ring (johannr)]

Thanks. This should be fixed now.