hallo Robert,
Es ist schonmal gut, dass Lily 2.12.3 jetzt besser läuft, auch wenn sich auf der Konsole v2.12.2 angesprochen fühlt. Da solltest du die Pfadeinträge ändern – und bei dieser Gelegenheit auch gleich die Pfade zu GS und Python überprüfen.
Es sieht so aus, als ob Du der erfahrenere Terminal-Bediener bist. Um mir langes Herumprobieren zu ersparen, könntest Du so nett sein und mir kurz erklären, wie ich die Pfade ändere? Wenn ich Lilypond 2.12.3 nutze, dann nehme ich an, daß es sich um den Pfad "/Applications/Notation/Lilypond_2.12.3/LilyPond.app/Contents/Resources/bin/gs" (in meinem Fall) handelt. Richtig?
Was Python angeht, so hat eine Fahndung auf meinem Rechner drei Fundorte ergeben: einmal in "Applications", dann noch in "/Library/Frameworks/Python.framework/Versions/2.6/include/python2.6" und in "/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6". Zu welchem muß ich den Weg weisen durch Pfadangabe?
Habe auch noch folgende Entdeckung gemacht: wenn ich im Terminal eingebe: python -v, kriege ich folgende Rückmeldung:
python -v
# installing zipimport hook
import zipimport # builtin
# installed zipimport hook
# /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/site.pyc has bad mtime
import site # from /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/site.py
# can't create /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/site.pyc
# /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/os.pyc has bad mtime
import os # from /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/os.py
# can't create /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/os.pyc
import posix # builtin
# /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/posixpath.pyc has bad mtime
import posixpath # from /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/posixpath.py
# can't create /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/posixpath.pyc
# /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/stat.pyc has bad mtime
import stat # from /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/stat.py
# can't create /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/stat.pyc
# /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/UserDict.pyc has bad mtime
import UserDict # from /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/UserDict.py
# can't create /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/UserDict.pyc
# /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/copy_reg.pyc has bad mtime
import copy_reg # from /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/copy_reg.py
# can't create /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/copy_reg.pyc
# /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/types.pyc has bad mtime
import types # from /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/types.py
# can't create /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/types.pyc
# /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/warnings.pyc has bad mtime
import warnings # from /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/warnings.py
# can't create /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/warnings.pyc
# /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/linecache.pyc has bad mtime
import linecache # from /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/linecache.py
# can't create /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/linecache.pyc
import encodings # directory /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/encodings
# /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/encodings/__init__.pyc has bad mtime
import encodings # from /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/encodings/__init__.py
# can't create /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/encodings/__init__.pyc
# /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/codecs.pyc has bad mtime
import codecs # from /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/codecs.py
# can't create /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/codecs.pyc
import _codecs # builtin
# /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/encodings/utf_8.pyc has bad mtime
import encodings.utf_8 # from /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/encodings/utf_8.py
# can't create /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/encodings/utf_8.pyc
Python 2.3.5 (#1, Jan 12 2009, 14:43:55)
[GCC 3.3 20030304 (Apple Computer, Inc. build 1819)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>>
Die Spotlight-Suche verweist aber nicht auf eine Python 2.6- und nicht auf eine Python 2.3-Installation. Und wenn ich unter den im Terminal angegebenen Pfaden suche, stoße ich auf 2.6. Was hat das zu bedeuten?
Und was heißt "has bad mtime"? Klingt nicht gut...
Ich hoffe, daß Du Licht in dieses Dunkel bringen kannst.
herzlichen Gruß