lilypond @2.18.2 failed to configure

[HagenBarz]

after a fresh clean installation of OS X 10.12.2 and macports I get the following error message

Error: Failed to configure lilypond, consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_lilypond/lilypond/work/lilypond-2.18.2/config.log
Error: org.macports.configure for port lilypond returned: configure failure: command execution failed
Please see the log file for port lilypond for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_lilypond/lilypond/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port lilypond failed

[ryandesign (Ryan Carsten Schmidt)]

Please attach the main.log and the config.log so we can see what happened.

[HagenBarz]

seems to be solved, lilypond ist now installed - thanks a lot

[ryandesign (Ryan Carsten Schmidt)]

Hmm. The main.log says:

ERROR: Please install required programs:  /opt/local/bin/fontforge >= 2011-02-22 (installed: )

So although fontforge is a declared dependency of lilypond and should thus have already been installed, it was unable to determine its version. I'm not sure why that would be, nor why it would suddenly fix itself.

We did have a problem with lilypond not being able to interpret the version of fontforge, but that was resolved months ago, and that problem looked different than yours; see #49338.

[HagenBarz]

me is missing the knowledge to examine what is going on behind the scene. luckily lilypond is up and running again (an essential tool for me as a musician). this thread can be marked as closed. thanks for all the work to the people from the macports team. happy new year.

[JaSpa (Janek Spaderna)]

For anybody coming across this now: I had the exact same problem. Executing fontforge --version revealed I hadn't installed ​XQuartz. I guess in this case the configure script isn't able to determine the version of fontforge.

[nerdling (Jeremy Lavergne)]

Starting to sound like an issue with fontforge needing all of Xorg instead of the bits it has called out.

I'll entertain adding Xorg to lilypond for now (since it'll be needed in the dependency tree anyways), but I'd prefer it be in the correct place.

If it really should go to fontforge, I'd encourage another ticket asking for it to be moved there.

Patched in a7745b4.