On Mon, Jun 26, 2006 at 12:29:24PM +0200, Karl Hammar wrote:
> > ps: do we really still have to use backticks instead of $(...)?
> > Anyone running LilyPond on old systems with rotten shells?
>
> configure is about portability, why not keep the backticks?
> The same goes for shells with 32bit int
[EMAIL PROTECTED]:
...
> Unfortunately, configure completely bails out then using something like
>
> $ PYTHON=/usr/local/bin/python2.4 ./configure ...
>
> The problem is in STEPMAKE_GETVERSION, since it takes the first
> line that looks like it contains a version number of the output
> from [Pat
On Wed, May 24, 2006 at 11:51:01PM +0200, Karl Hammar wrote:
> Given:
> $ ls -l /usr/bin/python*
> lrwxrwxrwx 1 root root 9 May 24 15:51 /usr/bin/python -> python2.3
> -rwxr-xr-x 1 root root 958764 Mar 6 11:32 /usr/bin/python2.3
> -rwxr-xr-x 1 root root 1024460 Apr 23 01:34 /usr/
Given:
$ ls -l /usr/bin/python*
lrwxrwxrwx 1 root root 9 May 24 15:51 /usr/bin/python -> python2.3
-rwxr-xr-x 1 root root 958764 Mar 6 11:32 /usr/bin/python2.3
-rwxr-xr-x 1 root root 1024460 Apr 23 01:34 /usr/bin/python2.4
configure will report wrong path of python:
$ ./conf
