On Fri, Oct 26, 2007 at 08:27:12AM -0400, Greg Troxel wrote:
> I think AM_PATH_PYTHON can be set up not to fail if python is not there.
>
> In that case we really should have some sort of @PYTHON_TRUE@
> substitution in makefiles so that gcodacon is then not installed.
Looks like the automake man
I think AM_PATH_PYTHON can be set up not to fail if python is not there.
In that case we really should have some sort of @PYTHON_TRUE@
substitution in makefiles so that gcodacon is then not installed.
On Mon, Oct 22, 2007 at 03:31:17PM -0400, Greg Troxel wrote:
> The following patch fixes this, finding python and substituting it. I
> don't think it will cause trouble on systems that do provide 'python'.
> Could it be committed?
Sure no problem, I didn't know there was an AM_PATH_PYTHON macro.
On pkgsrc systems, python is installed as pythonX.Y, e.g. python2.4, and
the name 'python' is not bound to anything. (Because packages install
files in site-local within some version, scripts must in general use the
same version of python that they were built/configured against. If
there were a d
