Reviewed the following SCSL Instructions:
http://zonked.sfbay/java/re/jdk/1.5.0/promoted/latest/doc/build/README-SCSL.html
http://zonked.sfbay/java/re/jdk/1.5.0/promoted/latest/doc/build/build.html
http://zonked.sfbay/java/re/jdk/1.5.0/promoted/latest/doc/build/build-solaris.html
http://zonked.sfbay/java/re/jdk/1.5.0/promoted/latest/doc/build/build-linux.html
http://zonked.sfbay/java/re/jdk/1.5.0/promoted/latest/doc/build/build-windows-i586.html
http://zonked.sfbay/java/re/jdk/1.5.0/promoted/latest/doc/build/build-windows-64.html


The following items need to be addressed:

(1) The READMEs are referring to "J2SDK 1.5.0". They should be changed to "JDK 5.0" as noted in the Naming FAQ at: http://javawebsfbay/j2se/releases/tiger/NameChange/FAQ.html

(2) The copyright in the READMEs needs to be updated to 2004.

(3) Need to change pointers of 1.4x URLs to the appropriate Tiger URLs.
"See the most up-to-date version of these build notes online at" in http://zonked.sfbay/java/re/jdk/1.5.0/promoted/latest/doc/build/README-SCSL.html

"J2SE download page" in http://zonked.sfbay/java/re/jdk/1.5.0/promoted/latest/doc/build/build-solaris.html

"required and recommended patches" in http://zonked.sfbay/java/re/jdk/1.5.0/promoted/latest/doc/build/build-solaris.html

(4) The URL to "DirectX 7 SDK" in http://zonked.sfbay/java/re/jdk/1.5.0/promoted/latest/doc/build/build-windows-i586.html and in http://zonked.sfbay/java/re/jdk/1.5.0/promoted/latest/doc/build/build-windows-64.html is no longer there. Need to update: http://download.microsoft.com/download/win98SE/DXSDK/7.0a/W9X/EN-US/dx7adxf.exe

(5) In http://zonked.sfbay/java/re/jdk/1.5.0/promoted/latest/doc/build/build-solaris.html
The locations of the patches have moved. Need to update the URLs of the patches in the 3 tables.

(6) Need to correct spelling of "gigbyte":
http://zonked.sfbay/java/re/jdk/1.5.0/promoted/latest/doc/build/build-linux.html
http://zonked.sfbay/java/re/jdk/1.5.0/promoted/latest/doc/build/build-windows-64.html

(7) Try to have consistencies. Use MB, GB.



###@###.### 2004-09-27
Adding the following:

(8) In http://zonked.sfbay/java/re/jdk/1.5.0/promoted/latest/doc/build/build-solaris.html
    under "cacerts"
    2nd paragraph
    "certificate" is mispelled

(9) We don't indicate the type of user who should be doing the build.
    We're assuming that admin or root is known.
    We might want to explicit state this.

(10) In http://zonked.sfbay/java/re/jdk/1.5.0/promoted/latest/doc/build/build-windows-i586.html
      under "Mozilla Headers and Libraries"

      "Note: the Java Plug-in..."
      should be
      "Note: The Java Plug-in..."

      "Tiger" is mentioned in the 2nd paragraph.
      Should change this to JDK 5.0

(11) In http://zonked.sfbay/java/re/jdk/1.5.0/promoted/latest/doc/build/build-windows-i586.html
      and in http://zonked.sfbay/java/re/jdk/1.5.0/promoted/latest/doc/build/build-windows-64.html
      under "MS DirectX"
      "... for building j2se. ..."
      should be
      "... for building JDK. ..."

(12) In this doc: http://zonked.sfbay/java/re/jdk/1.5.0/promoted/latest/doc/build/build-windows-64.html
      "Mozilla" is mentioned as one of the variables at
      the end. But there is no section what to do about it
      in the doc. The section seemed to be missing.



###@###.### 2004-09-28
From Lichun's testing:

(13) The gnumake download website has only "make" which is gnumake
     (tested by make -version). The final command used is therefore changed to
     "make scsl ......". Should the document be modified?

(14) There is nothing under bundle dir. Should the bundle be created also?
      The document has no info about if we are building binaries and bundles
      or just binaries.

(15) need to redirect both the std err and std out into a same file
      gnumake scsl > scsl.log 2>&1
      this would redirect both the output as well as error into a same file.



###@###.### 2004-09-28

(16) In this doc:
http://zonked.sfbay/java/re/jdk/1.5.0/promoted/latest/doc/build/build-windows-64.html
      It indicates that the min hw is Itanium.
      It should be changed to Itanium2.
      Itanium2 is the min hw for Linux.

(17) In this doc:
http://zonked.sfbay/java/re/jdk/1.5.0/promoted/latest/doc/build/build-windows-64.html
      Need to install DirectX SDK
      DirectX 7 SDK is no longer available from MS.
      Download and extracted DirectX 9 SDK, but was not able to install it.
      DirectX 9 SDK can not be installed on Itanium machine.
      Error indicated that it's not a supported config by DirectX SDK.
      
      Used a workaround of setting the DirectX variables to point
      to the temporary location of the include and lib files.
 
(18) In this doc:
http://zonked.sfbay/java/re/jdk/1.5.0/promoted/latest/doc/build/build-windows-64.html
      Need to add
      ALT_MSVCRTD_DLL_PATH
      next to ALT_MSVCRT_DLL_PATH
      (under section "Windows ... Environmment Variables)

(19) cacerts
      I was able to use the cacerts that came with the 1.4.2.
      (jre/lib/security/cacerts)



###@###.### 2004-09-29

(20) It would be nice to have a table (maybe after the hw requirements)
      to summarize the sw/tools requirements. This would help ease up
      the preparation when setting up the build machine.


10/05/04:
###@###.### 2004-10-05

(21) In http://zonked.sfbay/java/re/jdk/1.5.0/promoted/latest/doc/build/build.html
      Under "Testing the Build"
      In case the user forgets that ALT_OUTPUTDIR was previously set,
      the location of the built JDK will be pointing to that directory.
      Might want to add a liner about this var setting.
###@###.### 10/5/04 19:09 GMT


(22) It would be good to document that the SCSL building
      should be done by a particular user. When SQE was doing
      the SCSL testing, we used root/administrator to do the build.
      We were informed by RE that we should use a "regular user".
      However, that info is not included in the document.
###@###.### 10/6/04 00:21 GMT


(23) In http://zonked.sfbay/java/re/jdk/1.5.0/promoted/latest/doc/build/build-windows-64.html
      We need to remove the instruction for AMD on Windows
      since the build tools for this platform are not yet available.
###@###.### 10/6/04 18:24 GMT

(24) ALSA driver (version 0.9.1) on AMD/Linux
There is a known compilation problem on v1.0.5a and older versions when
you install it on linux-amd64. We should use the latest version.
Please see a note from Heidi at
http://javaweb.sfbay/~baechul/sound/ALSA.txt
###@###.### 10/12/04 15:50 GMT