From: Bruce S. <bas...@un...> - 2002-05-09 12:51:53
|
Thanks for the reports. I've updated the installation documentation on the VPython web site to explain that the Makefile as well as the install script have to be changed if python2.2 isn't in /usr/local/bin. A better installer would use the Python "dist-utils" mechanism, because it runs through Python, and Python knows where Python is. David Andersen wrote a dist-utils component, but I haven't yet incorporated it into the full installer. Another alternative would be for the install script to do a "which" operation on python2.2 and use the results to construct the correct locations. Unfortunately I'm not sufficiently facile with shell programming to do this quickly. (But I'd accept advice or help!) > The problem at my end was that when I installed Py 2.2 -- from > http://python.org/ftp/python/2.2.1/rpms/python2-2.2.1-1.src.rpm, > rather than from the object rpm -- it was put into /usr/bin/ and > /usr/include/ rather than (as the VP scripts expect) /usr/local/bin/ and > /usr/local/include/ . > > -- > Anton Sherwood, http://www.ogre.nu/ Bruce Sherwood Joining the NCSU Dept. of Physics June 1, 2002 |