ports/185542: x11/xlockmore compile failure due to update of print/freetype2

[Tom Russo]

>Number:         185542
>Category:       ports
>Synopsis:       x11/xlockmore compile failure due to update of print/freetype2
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Jan 07 00:20:00 UTC 2014
>Closed-Date:
>Last-Modified:
>Originator:     Tom Russo
>Release:        9.2-stable
>Organization:
>Environment:
FreeBSD goldstein.sandia.gov 9.2-STABLE FreeBSD 9.2-STABLE #1 r260373: Mon Jan  6 10:26:00 MST 2014     tvrusso at xxxxxxxxx.xxxxxx.xxx:/usr/obj/usr/src/sys/GOLDSTEIN  amd64
>Description:
Xlockmore, when built with the "MESAGL" option turned on, will no longer compile.

In file included from ./text3d2.cc:85:
/usr/local/include/FTGL/FTGLExtrdFont.h:29:5: warning: #warning This header is deprecated. Please use <FTGL/ftgl.h> from now.
In file included from /usr/local/include/FTGL/FTGLExtrdFont.h:30,
                 from ./text3d2.cc:85:
/usr/local/include/FTGL/ftgl.h:32:22: error: ft2build.h: No such file or directory
/usr/local/include/FTGL/ftgl.h:33:10: error: #include expects "FILENAME" or <FILENAME>
/usr/local/include/FTGL/ftgl.h:34:10: error: #include expects "FILENAME" or <FILENAME>
/usr/local/include/FTGL/ftgl.h:35:10: error: #include expects "FILENAME" or <FILENAME>
In file included from /usr/local/include/FTGL/ftgl.h:110,
                 from /usr/local/include/FTGL/FTGLExtrdFont.h:30,
                 from ./text3d2.cc:85:
/usr/local/include/FTGL/FTPoint.h:75: error: expected ',' or '...' before '&' token


and so on, and so on, and so on.

print/freetype2 was updated on 24 December 2113 (http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/184587) and that caused a large number of freetype-dependent builds to be updated.  Since xlockmore only depends on FTGL if MESAGL is selected, and it defaults to "off," this port probably got overlooked.

This may actually be an FTGL issue rather than an xlockmore issue, but I discovered it trying to update xlockmore.  

>How-To-Repeat:
Attempt to build xlockmore 5.43 after December 24, 2013, with the MESAGL option turned on.
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted: