[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: testing 2.13.7, bumped fontforge+double

From: Jan Nieuwenhuizen
Subject: Re: testing 2.13.7, bumped fontforge+double
Date: Fri, 06 Nov 2009 08:32:06 +0100

Op donderdag 05-11-2009 om 22:23 uur [tijdzone +0000], schreef Graham
> On Thu, Nov 05, 2009 at 10:36:41PM +0100, Jan Nieuwenhuizen wrote:
> > Op donderdag 05-11-2009 om 17:27 uur [tijdzone +0000], schreef Graham
> > Percival:

> Jan, since you know both python and GUB, could you try making the
> lilypond scripts on darwin  (convert-ly, lilypond-book, etc)
> point to the python that we distribute with lilypond, rather than
> #!/usr/bin/env?  I think that might fix

This issue looks like an installation error on part of reporter.
Reporter seems to have a [partly/roken] python [library] installed 
in his home directory.  Don't do that -- or don't write bug
reports when doing that ;-)

Moreover, python2.6 should be able to import md5 [try it on your
linux box] /and/ all lilypond scripts should "just" run with
python2.6 -- otherwise we'd have a slew of problems with just
about any linux distro.

Furthermore, I do not have much darwin knowledge, and it seems
that someone more knowledgable than me [Han-Wen?] has explicitly
specified to use darwin's native python by setting

    make_flags = ' TARGET_PYTHON="/usr/bin/env python"'

unfortunately, there is no comment there, but I would suggest
not to change it unless you know what you are doing.


Jan Nieuwenhuizen <address@hidden> | GNU LilyPond - The music typesetter
AvatarĀ®:    |

reply via email to

[Prev in Thread] Current Thread [Next in Thread]