Discussion: https://lists.gnu.org/archive/html/lilypond-user/2016-04/msg00026.html
Versions of OS X greater than 10.10.4 seem to have problems with the fondu utility, in the areas of font specification and resource fork handling:
\header { composer = \markup \right-align { \override #'(font-name . "Times Bold") "Rodgers/Hart" } }
Extract from running lilypond –V:
Invoking `fondu -force /System/Library/Fonts/Times.dfont'...
dyld: Symbol not found: __cg_jpeg_resync_to_restart
Referenced from: /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO
Expected in: /Users/andro/Lilypond.app/Contents/Resources/bin/../lib/libJPEG.dylib
in /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO
warning: `(fondu -force /System/Library/Fonts/Times.dfont)' failed (5)
fatal error: failed files: "t.ly"
The fondu utility seems to be unmaintained since 2013.
Mtas Behr has found a workaround for the resource forking issue:
"I've found out that the method for opening resource forks used in fondu - appending "/rsrc" to the file name - stopped working already in 10.7 Lion. (This surprises me a bit, I thought I'd used Lilypond successfully since then, but perhaps not with resource fork fonts ...) Instead you must append "/..namedfork/rsrc".
Per Carl Sorensen:
We need to discuss this on the developer list. It
seems we have a few options:
1) Get George Williams to fix fondu
2) Get somebody on the LilyPond team to take over maintenance of fondu
3) Put a fork of fondu into the lilypond source tree and take over
maintenance of the fork
4) Find an alternative utility that provides us the same functionality
5) Write our own utility to get the same functionality
It seems like we almost have a patch prepared, thanks to Mats's work. So
we could probably fork it if need be. But I'd sure rather have George
apply all the pending patches plus ours, and just release a new version.
Diff: