Can you build with LOG=trace to try and see the actual command that is
failing?
David
On 9/05/2018 11:39 AM, Yasumasa Suenaga wrote:
Hi,
2018-05-09 0:27 GMT+09:00 Erik Joelsson <erik.joels...@oracle.com>:
Hello,
Your assessment is looks correct so far. At this point, one would have to
start debugging the image to figure out what's wrong with it. Are you able
to run the exploded image in
./build/linux-x86_64-normal-server-fastdebug/jdk/bin/java?
It works. So I wonder why invalid image was built.
```
$ ./build/linux-x86_64-normal-server-fastdebug/jdk/bin/java --version
openjdk 11-internal 2018-09-25
OpenJDK Runtime Environment (fastdebug build 11-internal+0-adhoc.ysuenaga.jdk)
OpenJDK 64-Bit Server VM (fastdebug build
11-internal+0-adhoc.ysuenaga.jdk, mixed mode)
```
I'm waiting for Severin's evaluation :-)
Thanks,
Yasumasa
Has anyone at Redhat built successfully on Fedora 28 yet?
/Erik
On 2018-05-08 06:42, Yasumasa Suenaga wrote:
Hi all,
I tried to build OpenJDK (jdk/jdk) on Fedora 28 x64, but it failed as
following:
```
[ysuenaga@fc28 jdk]$ make images
Building target 'images' in configuration
'linux-x86_64-normal-server-fastdebug'
gmake[3]: *** [GenerateLinkOptData.gmk:64:
/home/ysuenaga/OpenJDK/jdk/build/linux-x86_64-normal-server-fastdebug/support/link_opt/classlist]
Error 1
gmake[2]: *** [make/Main.gmk:448: generate-link-opt-data] Error 2
ERROR: Build failed for target 'images' in configuration
'linux-x86_64-normal-server-fastdebug' (exit code 2)
No indication of failed target found.
Hint: Try searching the build log for '] Error'.
Hint: See doc/building.html#troubleshooting for assistance.
make[1]: *** [/home/ysuenaga/OpenJDK/jdk/make/Init.gmk:305: main] Error 2
make: *** [/home/ysuenaga/OpenJDK/jdk/make/Init.gmk:186: images] Error 2
```
It seems "interim-image" is not valid:
```
[ysuenaga@fc28 jdk]$
./build/linux-x86_64-normal-server-fastdebug/support/interim-image/bin/java
--version
Error occurred during initialization of VM
java/lang/NoClassDefFoundError: java/lang/Object
```
It can succeed on Fedora 27. So I think it causes by OS.
I've disabled SELinux, and warnings / errors are nothing in `journalctl
-a`.
Do you have any idea to resolve this issue?
Thanks,
Yasumasa
