ccing list
)-----Original Message-----
)From: Frank Tegtmeyer [mailto:
[hidden email]]
)Sent: 22 July 2011 18:04
)To: James Lowe
)Cc: Frank Tegtmeyer
)Subject: Re: Mac OS X Lion killed LilyPond
)Importance: Low
)
)
)> It could be what you suggest but could it also be that the newer Python
)install is being found first in the $PATH and so the wrong version or the
)right libraries are being called?
)
)I don' think that $PATH matters. LilyPond must provide it's own path
)anyway for it's subprocesses.
)And the purpose of shipping it's own Python is to call it, so LilyPond will
)ensure that it's own Python is called. What we see is that Python 2.6 is
)called (the LilyPond Python).
)Python itself sets its PYTHONPATH depending on how it was built. This
)hasn't changed after switching to Lion (it's the same binaries of Python).
)So either Lion doesn't have a library that is required by some Python
)module or it's name/path has changed.
)
)I would build LilyPond if it were a "self contained" process and wouldn't
)pollute my Mac with all the dependencies. But all descriptions of the build
)process suggest that it is complicated and requires a lot of preconditions.
)So I don't think I can do it.
)
)
)With kind regards,
)Frank
_______________________________________________
bug-lilypond mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Locked
