Re: [Visualpython-users] new installer glitches

[Jonathan B. <jbr...@ea...>]

On Wed, 2003-06-11 at 05:59, Arnd Baecker wrote:
> 1.) As I used
>   export PHOME=/home/baecker/morepub/PYTHON/
> instead of
>   export PHOME=/home/baecker/morepub/PYTHON
> (notice the missing back-slash at the end of the previous line!)
> I got the following error message

> The "//" prevents configure to see that it is in the  python module search
> path.
> (Surely, mea culpa, but hard to spot ;-)

If we were preforming a genuine directory search to verify this, the
trailing slash wouldn't matter.  However, we are actually using string
comparison within python, comparing the computed destination for the
visual module against the python variable sys.path (a python list).

If you want to improve this, you can check the file acinclude.m4,
shortly below the line AC_DEFUN([VISUAL_CHECK_PYTHON_SYS_PATH], you
should see a python script, bounded by _ACEOF.

> Also the reference to Python 2.3 might be misleading, in the sense
> that someone could think that Python 2.3 is necessary for the installation
> of Visual.

It isn't required.  This manual section is MUCH better than the
equivalant documentation in the 2.2.x manuals, and equally applicable to
both; that is why we point there.  The 2.2.x manuals are almost useless
in this particular regard.

> 2.) The second glitch occurs for "make install":
> 
> /usr/bin/install -c -m 755 vpython /bin/vpython
> /usr/bin/install: cannot create regular file `/bin/vpython': Permission
> denied
> make[1]: *** [install] Error 1
> make[1]: Leaving directory
> `/home/scratch/baecker/INSTALL_SOFT/PythonNeu/visual-2.0.3/cvisual'
> make: *** [install-recursive] Error 1
> 
> As a hack I changed the Makefile in the "cvisual" subdirectory,
> (Namely bindir = ${exec_prefix}/bin to bindir = ${prefix}/bin
> but I don't know configure at all to provide the correct fix here ...)

The value of 'bindir' as a variable in the makefile is set automatically
by configure.  You can manually set $(bindir) with --bindir=/foo/bar at
configure time to install wherever you like.  I don't think that this
particular file sets exec_prefix, which is a problem for me to fix. 
Otherwise, it would have worked for you as-is.

You can run configure --help to get a list of most of the options and
environment variables that are supported.

Thanks for your feedback,
-Jonathan