On 04/30/2014 12:42 AM, Erik Joelsson wrote:
On 2014-04-30 00:51, Dan Smith wrote:
Thanks Henry, that will force it to choose my referenced compiler.
Still not clear whether this is intended behavior or not: is the
default toolchain-type (clang, apparently) supposed to trump an
explicit tools-dir? I.e., is this a bug, or just surprising but
intentional?
I think this is intentional, but it could certainly still be discussed.
I'm surprised clang is already picked as default however. Perhaps there
is something else that's not working as intended causing this.
We use 'xcodebuild -version' to determine xcode version, and choose
clang as default after 5.0.
http://hg.openjdk.java.net/jdk9/jdk9/rev/77c150b417d8
--with-tools-dir specify where to find the toolchain, in this case, we
would hope it can correctly identify it's xcode 4, but it's not.
Cheers,
Henry
/Erik
—Dan
On Apr 25, 2014, at 1:43 PM, Henry Jen <henry....@oracle.com> wrote:
For JDK9, try to specify toolchain using --with-toolchain-type=gcc
Cheers,
Henry
On 04/25/2014 10:41 AM, Dan Smith wrote:
I'm using --with-tools-dir on OS X Mavericks to point to an old copy
of Xcode 4. I configure jdk9 as follows:
make dist-clean
hg update -d "<2014-03-17"
sh configure --with-boot-jdk=$JAVA8_HOME
--with-tools-dir=/Applications/Xcode4.app/Contents/Developer/usr/bin
Running generated-configure.sh
...
Tools summary:
* Boot JDK: java version "1.8.0" Java(TM) SE Runtime
Environment (build 1.8.0-b132) Java HotSpot(TM) 64-Bit Server VM
(build 25.0-b70, mixed mode) (at
/Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home)
* Toolchain: gcc (GNU Compiler Collection)
* C Compiler: Version 4.2.1 (at
/Applications/Xcode4.app/Contents/Developer/usr/bin/gcc)
* C++ Compiler: Version 4.2.1 (at
/Applications/Xcode4.app/Contents/Developer/usr/bin/g++)
...
As of March 18, this no longer works.
make dist-clean
hg update -d "<2014-03-18"
sh configure --with-boot-jdk=$JAVA8_HOME
--with-tools-dir=/Applications/Xcode4.app/Contents/Developer/usr/bin
Running generated-configure.sh
...
Tools summary:
* Boot JDK: java version "1.8.0" Java(TM) SE Runtime
Environment (build 1.8.0-b132) Java HotSpot(TM) 64-Bit Server VM
(build 25.0-b70, mixed mode) (at
/Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home)
* Toolchain: clang (clang/LLVM)
* C Compiler: Version Apple LLVM version 5.1 (clang-503.0.40)
(based on LLVM 3.4svn) Target: x86_64-apple-darwin13.1.0 Thread
model: posix (at /usr/bin/clang)
* C++ Compiler: Version Apple LLVM version 5.1 (clang-503.0.40)
(based on LLVM 3.4svn) Target: x86_64-apple-darwin13.1.0 Thread
model: posix (at /usr/bin/clang++)
...
I appreciate the effort to get clang to work, but I should still be
able to pick my compiler using --with-tools-dir.
Should I report a bug?
(Note on my motivation: I'm getting build errors due to
-Wformat-nonliteral. I've heard this is a known issue, but I'd like
to be able to work around it in the mean time.)
—Dan
