[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Tue, 8 Jul 2008 21:46:26 -0500
On Jul 8, 2008, at 4:26 PM, Graham Percival wrote:
On Tue, 08 Jul 2008 23:19:31 +0200
John Mandereau <address@hidden> wrote:
On 2008/08/08 15:52 -0500, Stan Sanderson wrote:
I installed 2.11.51 (ppc version) on my Intel iMac running 10.5.4.
Convert-ly works on the iMac and the updated .ly file compiles
correctly (from the command line).
I don't understand; what would make convert-ly fail on MacOS 1O.4 and
work on Mac OS 10.5, if you say you have Python 2.5.2 on 10.4?
(Maybe I should left this issue up to Mac users and developers, I've
never got nor used a Mac.)
No mystery here; the package managers are just being polite:
tsubasa:~ gperciva$ which python
tsubasa:~ gperciva$ python -V
tsubasa:~ gperciva$ /usr/bin/python -V
(I'm on OSX 10.4; 10.5 comes with python 2.5.x by default)
That's why I changed buildscripts/makelsr.py to
but there was some reason why Han-Wen said that wouldn't be good
for lilypond-book (and presumably convert-ly as well)
And now for the finale- I have installed 10.5.4 on the PPC 1.67MHz
PowerBook. The same Lilypond 2.11.51 file is installed; command line
convert-ly now works.
Re: convert-ly..., Wilbert Berendsen, 2008/07/08