On 2018-04-03 19:55, Martin Buchholz wrote:
It's some kind of weird race.
Weird. I can't help you out here, since I cannot reproduce.
I can tell you what I did to find the strange a.out file for solaris --
I opened one terminal with a "while true; do ls -l a.out; done", and one
running
It's some kind of weird race.
$ rm -f a.out; bash configure --with-toolchain-type=clang
--with-toolchain-path=/usr/lib/llvm-3.9/bin >&/dev/null; ls -l a.out; file
a.out
bash configure --with-toolchain-type=clang >&/dev/null 5.04s user 3.81s
system 94% cpu 9.323 total
-rw-r--r-- 1 martin martin
Actually, the clang issue is different. The fix for JDK-8200267 is
solstudio only.
Martin: I cannot reproduce the behaviour with "bash configure
--with-toolchain-type=clang
--with-toolchain-path=/usr/lib/llvm-3.9/bin". No a.out file for me. Is
this repeatable? Are you sure you didn't
https://bugs.openjdk.java.net/browse/JDK-8200267
On 2018-03-27 12:35, Martin Buchholz wrote:
I notice that running bash ./configure ... leaves an a.out file in the root
directory of the jdk, but only after adding configure flags
--with-toolchain-type=clang
I notice that running bash ./configure ... leaves an a.out file in the root
directory of the jdk, but only after adding configure flags
--with-toolchain-type=clang --with-toolchain-path=/usr/lib/llvm-3.9/bin
(i.e. not when building with default gcc)
Probably there's a test compilation whose
