JDK-8194142 : Solaris 10 no longer working after 8190308
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 10
  • Priority: P3
  • Status: Closed
  • Resolution: Won't Fix
  • OS: solaris_10
  • CPU: sparc
  • Submitted: 2017-12-23
  • Updated: 2018-01-02
  • Resolved: 2018-01-02
Related Reports
Relates :  
JDK-8192871 - Solaris: TestAllocateHeapAt fails
Relates :  
JDK-8190308 - Implementation: JEP 316: Heap Allocation on Alternative Memory Devices
Description
It looks like 8190308 has resulted in JDK 10 no longer working on Solaris 10. Now the following error is seen on startup:

===
-bash-3.2$ bin/java -version
Error: dl failure on line 597
Error: failed /tmp/buck/b37/jdk-10/lib/server/libjvm.so, because ld.so.1: java: fatal: relocation error: file /tmp/buck/b37/jdk-10/lib/server/libjvm.so: symbol posix_fallocate: referenced symbol not found
===

I understand that Solaris 10 is no longer an officially supported platform. But I wanted to make sure that the impact of this change is understood. Is it possible that we might want to reconsider this fix and try to provide a Solaris 10-friendly solution somehow?
Comments
Solaris 10 is no longer supported. We have no plans to verify that current changes work correctly on Solaris 10. Closing as WNF.
02-01-2018
Given the tests for JEP 316 continually fail on Solaris sparc I think this support needs to be conditionally built-in only for platforms known to support it. From what I've read it is not really an OS API but a filesystem API so you can't say for sure whether a particular OS supports it! See for example: http://austingroupbugs.net/view.php?id=684&nbn=10
23-12-2017