Michael Kuhn added the comment:
Thanks a lot Ned: you're right, the unexpected path was indeed set in
~/.pydistutils.cfg. So I agree with what has been written in the other issues,
that the installation should detect the clash between the command line
configuration and the configuration file t
Ned Deily added the comment:
Sorry, I'm unable to reproduce your results and they look rather suspicious.
Keep in mind that the Python build uses its copy of Distutils to build and
install the interpreter's shared extension modules, like _ctypes.so. My guess
is that your "make install" is be
New submission from Michael Kuhn:
I need to install Python 2.7 in two architectures, but under one file system. I
thus configure:
/home/cellnet/michaelk/SRC/Python-2.7.3> ./configure
--prefix=/home/cellnet/michaelk/biocluster
--exec-prefix=/home/cellnet/michaelk/biocluster -q
When I compile
