Opened 14 years ago
Closed 9 years ago
#3594 closed defect (duplicate)
python installation directory
Reported by: | dstahlke | Owned by: | hobu |
---|---|---|---|
Priority: | normal | Milestone: | 1.11.0 |
Component: | PythonBindings | Version: | 1.10.1 |
Severity: | normal | Keywords: | |
Cc: | antonio |
Description
The python swig bindings seem to have improper logic with regards to the installation directory. If I run
./configure --prefix=/opt/gdal-1.7.2 --with-python ...etc..
Then "make install" in swig/python tries to install into the system python directory /usr/lib64/python2.6/site-packages/. Now, if I edit swig/python/GNUMakefile and replace
ifeq ($(PY_HAVE_SETUPTOOLS),1) $(PYTHON) setup.py install else $(PYTHON) setup.py install --prefix=$(DESTDIR)$(prefix) endif
with
#ifeq ($(PY_HAVE_SETUPTOOLS),1) # $(PYTHON) setup.py install #else $(PYTHON) setup.py install --prefix=$(DESTDIR)$(prefix) #endif
then it tries to install into /opt/gdal-1.7.2/lib64/python2.6/site-packages/ but fails because it doesn't exist. After running
mkdir -p /opt/gdal-1.7.2/lib64/python2.6/site-packages/
make install will run correctly.
Change History (3)
comment:1 by , 14 years ago
Cc: | added |
---|
comment:2 by , 10 years ago
Milestone: | → 1.11.0 |
---|---|
Version: | unspecified → 1.10.1 |
comment:3 by , 9 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
I close this as duplicate and leave #4563 open because it has more comments.
Note:
See TracTickets
for help on using tickets.
Same prefix issue on Scientific Linux (and I cannot manually modify Makefiles on a production system...).
Same issue reported in #4563