lilypond 2.18.2 config doesn't identify fontforge version correctly

[rlhamil]

build OS / compiler / MacPorts version:
Mac OS X 10.11 15A284 (El Capitan)
Xcode 7.0.1 7A1001
MacPorts Version: 2.3.4

:info:configure ERROR: Please install required programs:  /opt/local/bin/fontforge >= 20110222 (installed: 2015-10-17 02:29:06.158 osascript[83576:14837586)
:info:configure 
:info:configure See INSTALL.txt for more information on how to build LilyPond
:info:configure Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_lilypond/lilypond/work/lilypond-2.18.2" && ./configure --prefix=/opt/local --with-ncsb-dir=/opt/local/share/fonts/urw-fonts --enable-documentation 

lapple root# port installed and fontforge
The following ports are currently installed:
  fontforge @20120731_3 (active)

03:10:57[325]lapple:/Users/rlhamil> fontforge --version
Copyright (c) 2000-2012 by George Williams.
 Executable based on sources from 14:57 GMT 31-Jul-2012-ML-NoPython.
 Library based on sources from 14:57 GMT 31-Jul-2012.
fontforge 20120731
libfontforge 20120731-ML

[rlhamil]

config.log

[rlhamil]

main.log

[ryandesign (Ryan Carsten Schmidt)]

I can try to compare your log with mine to see why yours is getting an applescript (osascript) error determining the fontforge version, when mine is not.

[rlhamil]

I got this to build after noticing that fontforge --version spits out extra lines of garbage if run with "su -" in effect, but not as a regular user, nor with just plain "su"; i.e., some difference in the environment causes problems.

However, if one does

fontforge --version 2>/dev/null the output is the same regardless:

begin output

fontforge 20120731 libfontforge 20120731-ML

end output

(not including the delimiter lines, obviously)

If the config test were modified accordingly, perhaps it would become immune to this.

[mojca (Mojca Miklavec)]

Cc Me!

[mojca (Mojca Miklavec)]

lilypond-devel uses

# help fontforge date calculation
reinplace s|20110222|2011-02-22|g ${worksrcpath}/configure

and its installation succeeds. I guess that lilypond could do the same.

[LenoreHorner]

Cc Me!

[nerdling (Jeremy Lavergne)]

Patched in r151453.