You seem to have gotten a mismatch due to several versions of freetype
installed.
The output from the build is:
In file included from
/Users/dr2chase/work/jdk9/jdk/src/share/native/sun/font/freetypeScaler.c:34:
/usr/X11/include/ft2build.h:56:38: warning: freetype/config/ftheader.h: No such
file or directory
which indicates that you are using freetype from /usr/X11/include. This
is likely what configure will autodetect. If you check the configure
output, what does it say about freetype?
I think the root cause of what I see here is a change in MacPorts freetype2.
From my backup disk:
ls -l /Volumes/TBackup/opt/local/include/freetype2/freetype/config/ftheader.h
-rw-r--r-- 1 root admin 26118 Jun 20 2013
/Volumes/TBackup/opt/local/include/freetype2/freetype/config/ftheader.h
From my current disk:
ls -l /opt/local/include/freetype2/freetype/config/ftheader.h
ls: /opt/local/include/freetype2/freetype/config/ftheader.h: No such file or
directory
ls /opt/local/include/freetype2
config ftbdf.h ftcid.h ftgzip.h ftmac.h
ftpfr.h ftsystem.h t1tables.h
freetype.h ftbitmap.h fterrdef.h ftimage.h ftmm.h
ftrender.h fttrigon.h ttnameid.h
ft2build.h ftbzip2.h fterrors.h ftincrem.h ftmodapi.h
ftsizes.h ftttdrv.h tttables.h
ftadvanc.h ftcache.h ftgasp.h ftlcdfil.h ftmoderr.h
ftsnames.h fttypes.h tttags.h
ftautoh.h ftcffdrv.h ftglyph.h ftlist.h ftotval.h
ftstroke.h ftwinfnt.h ttunpat.h
ftbbox.h ftchapters.h ftgxval.h ftlzw.h ftoutln.h
ftsynth.h ftxf86.h
Apparently configure picked up the MacPorts freetype2, but that changed in a
recent update.
That seems unlikely that it should have picked that up by itself. Did
you set --with-freetype at any point? Do you have any configure logs
from the old build?
=================
I considered my options, and decided that what I was sure I could do and test
quickly was to install a symbolic link
from /opt/local/include/freetype2/freetype to ../freetype2.
Another option might have been to try setting
--with-freetype-include specify directory for the freetype include files
Using the --with-freetype option is the preferred mode, instead of
modifying system files.
Nevertheless, I'm curious if configure really did pick up freetype
automatically in the /opt/local system before, but not now. It might be
due to pkg-config.
Can you try running "pkg-config --cflags freetype2" and post the output?
If you have access to a machine without this change in packaging, can
you try the same command there?
/Magnus
to the freetype include directory for /usr/X11/include/??? (there's a
freetype2/freetype there, too)
but I was unsure if I also needed to change the library, or if such a changed
library existed.
Suggestions are welcome.
David
