[issue18320] idle, pydoc search python on wrong path at make altinstall with different exec- and prefix e.g. $HOME
New submission from cosmicduck:
Using Solaris 10 x86
Compiling actual 3.3.2 or 2.7.5 looks like work.
Installing as non-root with
make altinstall prefix='${HOME}/scripts/tools/python/python-3.3.2'
exec-prefix='${HOME}/scripts/tools/python/python-3.3.2' installs looks like
correctly to the target.
Extends LD_LIBRARYPATH and PATH to
${HOME}/scripts/tools/python/python-3.3.2/lib and
${HOME}/scripts/tools/python/python-3.3.2/bin has been done.
Python is started correctly with python3.3.
If I start idle3.3 or pydoc3.3 I get error:
/usr/local/bin/python3.3: bad interpreter: No such file or directory.
So it looks like the she-bang is not correctly set for shell scripts to the
path prefix and exec-prefix path.
Correcting that by manually setup to
${HOME}/scripts/tools/python/python-3.3.2/bin fix that problem. But I guess
it's better to modify the installation process by make to have not future
problems.
--
components: IDLE
messages: 191977
nosy: cosmicduck
priority: normal
severity: normal
status: open
title: idle, pydoc search python on wrong path at make altinstall with
different exec- and prefix e.g. $HOME
versions: Python 2.7, Python 3.3
___
Python tracker
<http://bugs.python.org/issue18320>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18320] python installation is broken if prefix is overridden on an install target
cosmicduck added the comment: Hi, this is a problem for all users which have to want to use python on there own home directory. I wonder me, how did some other projects could install python to different directories e.g. OpenCSW it did on /opt/csw/... My most problem is, that I can do many but without root access, which is denied. In this case a installation/build to a different path is very helpfull. The situation was, that python and there most modules are working well also post installed ones. Only the problem with the shebang to the scripts was the major problems which I've fixed by a line change on all scripts. But to build python on a different root path e.g. my home folder, this should be changed simply by make itself and not by hand as I did it. I'm unsure that other problems with my steps exists, but only the shebang problem is found by me. This problem could also exists on later releases than 3.3. So for me it's ok to close this issue for 3.3. But for later releases, e.g. 3.4 it should checked and fixed, please. -- ___ Python tracker <http://bugs.python.org/issue18320> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
