-
Bug
-
Resolution: Not an Issue
-
P4
-
7
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2179391 | 7-pool | Unassigned | P4 | Closed | Won't Fix | |
| JDK-2179392 | 6-pool | Unassigned | P4 | Closed | Won't Fix |
This is a hotspot build issue, not a runtime issue.
The hotspot makefiles seem to be sensitive to the JAVA_HOME env variable and in my opinion this is a mistake. On some Linux systems this env variable is defined to refer to non Sun jdks, and users often have to set it to run specific java apps. The hotspot makefiles picking it up from the environment seems wrong. The documented VM used to build the hotspot repository/workspace is ALT_BOOTDIR or BOOTDIR and it seems like the hotspot Makefiles should explcitly set JAVA_HOME when it runs it's ./test_gamma, e.g.
JAVA_HOME=$(BOOTDIR) ./test_gamma
This is an issue in jdk5, jdk6, and jdk7.
The hotspot makefiles seem to be sensitive to the JAVA_HOME env variable and in my opinion this is a mistake. On some Linux systems this env variable is defined to refer to non Sun jdks, and users often have to set it to run specific java apps. The hotspot makefiles picking it up from the environment seems wrong. The documented VM used to build the hotspot repository/workspace is ALT_BOOTDIR or BOOTDIR and it seems like the hotspot Makefiles should explcitly set JAVA_HOME when it runs it's ./test_gamma, e.g.
JAVA_HOME=$(BOOTDIR) ./test_gamma
This is an issue in jdk5, jdk6, and jdk7.
- backported by
-
JDK-2179391 Hotspot makefiles are sensitive to JAVA_HOME env variable
-
- Closed
-
-
-
- Closed
-