Re: [Visualpython-users] make failure

[Bruce S. <Bru...@nc...>]

I haven't had a chance to look at the files you sent, but I can address 
point 1 in your question. In INSTALL.txt you will find the following:

If you have multiple versions of Python installed, and the one named 
'python' that is first on your PATH (identified with `which python`) is 
not the one you want to build Visual for, specify the correct 
interpreter by setting the PYTHON environment variable to the desired 
interpreter's full path.

And on the Linux download page at vpython.org this point is also made:

If you want to use a different version of Python than the one found with 
"which python", or (b) is not appropriate, specify both the particular 
Python and where to install Visual:
    PYTHON=/somewhere1/bin/python ../visual-x.x.x/configure 
--prefix=/somewhere2
If "somewhere1" and "somewhere2" are different, you must also add the 
"somewhere2" directory to Python's module search path. For details, at 
www.python.org read section 4.1 (Modifying Python's Search Path) in the 
section Installing Python Modules of the Python 2.3 on-line documentation.

The key point is that --prefix governs where you put stuff, while PYTHON 
refers to the path to your Python, which are two different things (at 
least in principle).

Bruce Sherwood

James Foadi wrote:
> I have had, so far, 2 problems installing VPython.
> 
> 1) During the configure stage, although I run the configure script as:
> 
>  ./configure --prefix=/home/james/binPYTHON
> 
> given that I hold a local version of Python, the script found 
> $PYTHON=/usr/bin/python, which is the root version. I had to (manually) 
> insert PYTHON=/home/james/binPYTHON/bin/python  to proceed with correct 
> configuration. Without it the configure script was telling me that it was 
> unable to find Numeric and Numarray.
> 
> 2) For the compilation error (which is beyond my ability to repair), please 
> look at the attached files
> 
> Thank you very much fort your help
> 
> J