mx version check question with openjdk build JDK
Bernhard Urban
bernhard.urban at jku.at
Wed Jul 16 21:44:30 UTC 2014
Sorry, I introduced this regression while I fixed the problem around the
.hotspot_compiler file. Pushing a fix now, you can find the patch here in
the meanwhile:
http://lafo.ssw.uni-linz.ac.at/lewurm/mx-java-version-fix.patch
Thanks,
-Bernhard
On Wed, Jul 16, 2014 at 11:14 PM, Eric Caspole <eric.caspole at amd.com> wrote:
> After meging up, "mx clean" does not work with my Sumatra JDK. It works OK
> if JAVA_HOME is JAVA_HOME=/opt/jdk1.8.0_05
>
> In my mx/env it is:
> JAVA_HOME=/home/ecaspole/views/sumatra-dev/build/linux-
> x86_64-normal-server-fastdebug/images/j2sdk-image/
>
>
> $ ./mx.sh clean
> Traceback (most recent call last):
> File "/home/ecaspole/views/graal-default/graal/mxtool/mx.py", line
> 4921, in <module>
> main()
> File "/home/ecaspole/views/graal-default/graal/mxtool/mx.py", line
> 4858, in main
> defaultJdk = JavaConfig(opts.java_home, opts.java_dbg_port)
> File "/home/ecaspole/views/graal-default/graal/mxtool/mx.py", line
> 1750, in __init__
> self.version = VersionSpec(version.split()[2].strip('"'))
> AttributeError: 'NoneType' object has no attribute 'split'
>
>
> So -version is different in my build compared to a release:
>
> $ /home/ecaspole/views/sumatra-dev/build/linux-x86_64-normal-
> server-fastdebug/images/j2sdk-image/bin/java -version
> openjdk version "1.8.0-internal-fastdebug"
> OpenJDK Runtime Environment (build 1.8.0-internal-fastdebug-
> ecaspole_2014_06_04_10_32-b00)
> OpenJDK 64-Bit Server VM (build 25.0-b70-fastdebug, mixed mode)
>
> $ /opt/jdk1.8.0_05/bin/java -version
> java version "1.8.0_05"
> Java(TM) SE Runtime Environment (build 1.8.0_05-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.5-b02, mixed mode)
>
>
> I am not sure that is the exact problem here. Is it "java version" vs
> "openjdk version" ?
> Thanks,
> Eric
>
>
More information about the graal-dev
mailing list