[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: configure bug?
From: |
Jan Nieuwenhuizen |
Subject: |
Re: configure bug? |
Date: |
Sun, 18 Aug 2002 14:21:35 +0200 |
User-agent: |
Gnus/5.090006 (Oort Gnus v0.06) Emacs/21.2 (i386-debian-linux-gnu) |
Han-Wen Nienhuys <address@hidden> writes:
> address@hidden writes:
>> Also one other thing that would possibly a nice thing to have
>> is for the configure script to check for the python binary as
>> python2.1 or python1.5 and use the most appropriate one (for
>> those of use who have more than one version installed). The
>> python binary named python1.5 (or python2.1 etc.) is done
>> with the FreeBSD packages so I am not just making this up :)
>
> ?
>
> Both are possible. If you have a preference for either, link /usr/bin/python
> to pythonX.Y that you prefer.
To elaborate: if after installing a (or more than one) Python
package(s), there is no 'python' executable, your package management
system is broken, imho of course.
Jan.
--
Jan Nieuwenhuizen <address@hidden> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org