[reportlab-users] installation dir troubles

[Robin Becker]

Frederik Himpe wrote:
.........

> Two examples from the log:

> 

> byte-compiling /home/fhimpe/python-reportlab/BUILDROOT/python-reportlab-root/usr/lib/python2.5/site-packages/reportlab/tools/__init__.py to __init__.pyc

>                                                                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

> 

> copying docs/userguide/app_demos.py -> /home/fhimpe/python-reportlab/BUILDROOT/python-reportlab-root/usr/lib64/python2.5/site-packages/reportlab/docs/userguide

>                                                                                                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

> 

OK now I see; something appears to be very wrong with your installation prefix. 
You appear to have two. Can you remember how you actually installed python? Did 
you do something like

./configure --prefix=/home/fhimpe/python-reportlab
make
make install

If so I can try to do exactly the same on one of our machines. When I do this on 
our amd I see this sort of thing

copying 
build/lib.freebsd-6.1-RELEASE-amd64-2.5/reportlab/graphics/samples/stacked_bar.py ->
/home/rptlab/PYTHON/lib/python2.5/site-packages/reportlab/graphics/samples
 

......
byte-compiling 
/home/rptlab/PYTHON/lib/python2.5/site-packages/reportlab/__init__.py to 
__init__.pyc
......
running install_data
creating /home/rptlab/PYTHON/lib/python2.5/site-packages/reportlab/demos
......
copying docs/images/Edit_Prefs.gif -> 
/home/rptlab/PYTHON/lib/python2.5/site-packages/reportlab/docs/images

so in this case at least the code and data ends up exactly where it's supposed to.

We have multiple pythons installed using the above approach. What I don't 
understand is why your machine needs to mention lib64 at all. What kind of 
OS/hardware are you installing on.


-- 
Robin Becker