Build failures on OS X 10.9.3

[Magnus Ihse Bursie]

Hi,

I suspect it'll be easier to just install gcc on your mac. The last time I
checked openjdk 8 didn't compile correctly with clang, so you might also
have to patch the source code as well as the autoconf scripts.

So Apple are now shipping a compiler by default, but it's clang, which
they've aliased to gcc, despite the fact that the binaries differ?
So all the standard hacks from earlier OS versions where you test for
the presence of certain binaries to see whether devtools are installed
are now bust?
Well, isn't that ... lovely?
I'd be intruigued to know whether OpenJDK 9 will build with Clang, as
the autoconf seems happy with the behaviour of "gcc". I might install
the TrueType headers and see how far that gets.

OpenJDK 9 is supposed to compile properly with clang on macosx.
Configure will auto-select clang if your Xcode version is >= N, for some
number of N (I suspect 5, but I'm not sure).

As for the freetype issue, I'm not sure I understand the problem. Do you
believe there is a regression? Freetype is and has always been a build
requirement for OpenJDK. Is the problem that OpenJDK 9 suddenly cannot
locate freetype automatically, when this has worked before?

In general, if you find issues with the build system, the best and
quickest responses are often received if you post the issues to
build-dev at openjdk.java.net.

/Magnus

[David DeHaven]

I suspect it'll be easier to just install gcc on your mac. The last time I
checked openjdk 8 didn't compile correctly with clang, so you might also
have to patch the source code as well as the autoconf scripts.

So Apple are now shipping a compiler by default, but it's clang, which
they've aliased to gcc, despite the fact that the binaries differ?
So all the standard hacks from earlier OS versions where you test for
the presence of certain binaries to see whether devtools are installed
are now bust?
Well, isn't that ... lovely?
I'd be intruigued to know whether OpenJDK 9 will build with Clang, as
the autoconf seems happy with the behaviour of "gcc". I might install
the TrueType headers and see how far that gets.

OpenJDK 9 is supposed to compile properly with clang on macosx. Configure will auto-select clang if your Xcode version is >= N, for some number of N (I suspect 5, but I'm not sure).

Correct, Xcode >= 5 will select clang as the compiler.

Does Freetype detection use pkg-config? I've never had an issue building OpenJDK with MacPorts' Freetype installed.

-DrD-

[Bernhard Urban]

On Thu, Sep 25, 2014 at 1:15 AM, David DeHaven <david.dehaven at oracle.com>

Post by Magnus Ihse Bursie

I suspect it'll be easier to just install gcc on your mac. The last

time I

Post by Magnus Ihse Bursie

checked openjdk 8 didn't compile correctly with clang, so you might

also

Post by Magnus Ihse Bursie

have to patch the source code as well as the autoconf scripts.

So Apple are now shipping a compiler by default, but it's clang, which
they've aliased to gcc, despite the fact that the binaries differ?
So all the standard hacks from earlier OS versions where you test for
the presence of certain binaries to see whether devtools are installed
are now bust?
Well, isn't that ... lovely?
I'd be intruigued to know whether OpenJDK 9 will build with Clang, as
the autoconf seems happy with the behaviour of "gcc". I might install
the TrueType headers and see how far that gets.

OpenJDK 9 is supposed to compile properly with clang on macosx.

Configure will auto-select clang if your Xcode version is >= N, for some
number of N (I suspect 5, but I'm not sure).
Correct, Xcode >= 5 will select clang as the compiler.
Does Freetype detection use pkg-config? I've never had an issue building
OpenJDK with MacPorts' Freetype installed.
-DrD-

it looks like the configure script of OpenJDK 8 doesn't detect newer
versions of freetype. I had problems with xquartz 2.7.6 (that contains
freetype 2.5.3), but xquartz 2.7.5 (containing freetype 2.5.0.1) it worked
for me.

From a quick look into the config.log it looks like that the directory

organization of the header files changed, and the OpenJDK8 configure script
is not aware of it.

-Bernhard

[Martijn Verburg]

Hi all,

FYI - I have a similar problem on Mac OS X 10.9.5 with the latest XCode 6 &
XQuartz 2.7.7.

Cheers,
Martijn

Post by Bernhard Urban
On Thu, Sep 25, 2014 at 1:15 AM, David DeHaven <david.dehaven at oracle.com>

Post by Magnus Ihse Bursie

I suspect it'll be easier to just install gcc on your mac. The last

time I

Post by Magnus Ihse Bursie

checked openjdk 8 didn't compile correctly with clang, so you might

also

Post by Magnus Ihse Bursie

have to patch the source code as well as the autoconf scripts.

So Apple are now shipping a compiler by default, but it's clang, which
they've aliased to gcc, despite the fact that the binaries differ?
So all the standard hacks from earlier OS versions where you test for
the presence of certain binaries to see whether devtools are installed
are now bust?
Well, isn't that ... lovely?
I'd be intruigued to know whether OpenJDK 9 will build with Clang, as
the autoconf seems happy with the behaviour of "gcc". I might install
the TrueType headers and see how far that gets.

OpenJDK 9 is supposed to compile properly with clang on macosx.

Configure will auto-select clang if your Xcode version is >= N, for some
number of N (I suspect 5, but I'm not sure).
Correct, Xcode >= 5 will select clang as the compiler.
Does Freetype detection use pkg-config? I've never had an issue building
OpenJDK with MacPorts' Freetype installed.
-DrD-

it looks like the configure script of OpenJDK 8 doesn't detect newer
versions of freetype. I had problems with xquartz 2.7.6 (that contains
freetype 2.5.3), but xquartz 2.7.5 (containing freetype 2.5.0.1) it worked
for me.
From a quick look into the config.log it looks like that the directory
organization of the header files changed, and the OpenJDK8 configure script
is not aware of it.
-Bernhard