[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 [Path stripped to take the line shorter]: > > $ python2.4 --version 2>&1 || python2.4 -V 2>&1 > > which is > > Unknown option: -- > usage: python2.4 [option] ... [-c cmd | -m mod | file | -] [arg] ... > Try `python -h' for more information. > Python 2.4.3 > > The net result is that, for whatever reason, configure first detects > 2.4.3, but later 2.3.5. > > I think the attached patch fixes this. (Works at least when configuring > on OpenBSD).
Seen same problem, your patch fixes this for me also. > Note that the patch contains another quick hack to let the version > check work on OpenBSD and other systems where the shell has 32 bit > integer arithmetic (without it, you'll get too large version numbers > for fontforge, letting configure think that 20060413 is smaller > than the requested version). > > Ciao, > Kili > > 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 arith. > pps: I *only* tested the configure step yet. No idea wether it will > actually build and run. ... It builds and runs ok (using debian v3.1). Regards, /Karl _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
