> I'm trying to do a vanilla build on Mac OS X Mavericks. (Using an old copy > of Xcode 4.) > > Configure succeeds as follows, while acknowledging that X11 is not found: > > sh configure --with-boot-jdk=$JAVA7_HOME > --with-tools-dir=/Applications/Xcode4.app/Contents/Developer/usr/bin > ... > checking what is not needed on MacOSX?... alsa pulse x11 > checking for Mac OS X Java Framework... > /System/Library/Frameworks/JavaVM.framework > checking for X... no > checking for X11/extensions/shape.h... no > ... > > Building jdk gets a compiler error, complaining about a missing X11 header: > > make all > ... > In file included from > /Users/dan/Dev/jdk/jdk8/jdk/src/share/native/sun/java2d/pipe/Region.h:34, > from > /Users/dan/Dev/jdk/jdk8/jdk/src/share/native/sun/java2d/loops/Blit.c:27: > /Users/dan/Dev/jdk/jdk8/jdk/src/solaris/native/sun/awt/utility/rect.h:31:22: > warning: X11/Xlib.h: No such file or directory > In file included from > /Users/dan/Dev/jdk/jdk8/jdk/src/share/native/sun/java2d/pipe/Region.h:34, > from > /Users/dan/Dev/jdk/jdk8/jdk/src/share/native/sun/java2d/loops/Blit.c:27: > /Users/dan/Dev/jdk/jdk8/jdk/src/solaris/native/sun/awt/utility/rect.h:32: > error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘RECT_T’ > ... > > As I understand it, all dependencies on X11 were supposed to have been > removed at the end of October. (Attempts to run configure on earlier > versions fail, telling me I need X11.)
Nope, you still need to have XQuartz installed for the dependencies. I did not have enough time to remove all traces of X11. The choice was to leave the defunct X11 toolkit and completely incorrect jawt_md.h in place (IMHO the worst option) or live with the (what should be a minor) annoyance of having X11 headers lingering, and I barely had enough bandwidth to get that done. Of course, anyone willing to take on the work of completely removing X11 dependencies is more than welcome to! There's already a JBS issue for it: https://bugs.openjdk.java.net/browse/JDK-8003900 Although I'm a bit surprised configure isn't looking for X11, that might warrant investigation. Or maybe not, since X11 is doomed anyways... -DrD-
