JDK-6526456 : Make it easier to bootstrap a hotspot build on linux
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 7
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: linux
  • CPU: generic
  • Submitted: 2007-02-19
  • Updated: 2012-10-13
  • Resolved: 2007-03-15
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6 JDK 7 Other
6u4Fixed 7Fixed hs10Fixed
It's a pain to bootstrap a hotspot build on a linux system where no jdk exists.
Naive attempts to build hotspot will just fail.  Historically, we've hacked
a bootstrap build when doing a port.  That's no longer adequate now that people
outside Sun want to do ports.


SUGGESTED FIX In the linux makefiles, prefix every bootstrap jdk command (i.e., java, javac, javah, etc.) with '$(REMOTE)', where REMOTE is defined to be the remote execution method of the builders choice. So, for example, we could issue the following 'make' command. make REMOTE="rsh <linux-i586-machine-name>" product where <linux-i586-machine-name> is the name of an x86 or x64 box running linux. One still must set one of ALT_BOOTDIR, BOOTDIR or JAVA_HOME to point to the full pathname of a bootstrap jdk that's executable on <linux-i586-machine-name>.