Python modules installed to wrong location
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
UFC | Status tracked in Trunk | |||||
2.0.x |
Fix Committed
|
Medium
|
Johannes Ring | |||
2.1.x |
Fix Released
|
Medium
|
Unassigned | |||
Trunk |
Fix Released
|
Medium
|
Johannes Ring |
Bug Description
Currently, the python modules end up getting installed, on a 64 bit system redhat/fedora, to:
/usr/lib64/
which I think is incorrect - the python modules are architecture independent, and so should go under
/usr/lib/
[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.
which I think should be:
-c "import sys, distutils.
Have attached a (trivial) patch which fixes this.
Related branches
Changed in ufc: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in ufc: | |
assignee: | nobody → Johannes Ring (johannr) |
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.