jdk-sandbox: comparison README-builds.html

equal deleted inserted replaced

-:cdaa6122185f
+:2ca7a2522cb4
 <li><a href="#alsa">ALSA files</a> </li>
 </ul>
 </li>
 <li>Windows only:
 <ul>
-<li>Unix Command Tools (<a href="#cygwin">CYGWIN</a>)</li>
+<li>Unix Command Tools (<a href="#cygwin">CYGWIN</a>) <strong>or</strong></li>
+<li>Minimalist GNU for Windows (<a href="#msys">MinGW/MSYS</a>)</li>
 <li><a href="#dxsdk">DirectX 9.0 SDK</a> </li>
 </ul>
 </li>
 </ul>
 </li>
 <hr>
 <h2><a name="MBE">Minimum Build Environments</a></h2>
 <blockquote>
 This file often describes specific requirements for what we call the
 "minimum build environments" (MBE) for this
-	    specific release of the JDK,
+specific release of the JDK,
 Building with the MBE will generate the most compatible
 bits that install on, and run correctly on, the most variations
 of the same base OS and hardware architecture.
 These usually represent what is often called the
 least common denominator platforms.
 <td>Java for OS X Lion Update 1</td>
 </tr>
 </tbody>
 </table>
 <p>
-	    These same sources do indeed build on many more systems than the
+These same sources do indeed build on many more systems than the
-	    above older generation systems, again the above is just a minimum.
+above older generation systems, again the above is just a minimum.
 <p>
-	    Compilation problems with newer or different C/C++ compilers is a
+Compilation problems with newer or different C/C++ compilers is a
-	    common problem.
+common problem.
-	    Similarly, compilation problems related to changes to the
+Similarly, compilation problems related to changes to the
 <tt>/usr/include</tt> or system header files is also a
-	    common problem with newer or unreleased OS versions.
+common problem with newer or unreleased OS versions.
-	    Please report these types of problems as bugs so that they
+Please report these types of problems as bugs so that they
-	    can be dealt with accordingly.
+can be dealt with accordingly.
 </blockquote>
 <!-- ------------------------------------------------------ -->
 <hr>
 <h2><a name="SDBE">Specific Developer Build Environments</a></h2>
 <blockquote>
 <blockquote>
 <h4>Fedora 9</h4>
 <p>
 <blockquote>
 After installing <a href="http://fedoraproject.org">Fedora</a> 9
-	      you need to install several build dependencies. The simplest
+you need to install several build dependencies. The simplest
-	      way to do it is to execute the following commands as user
+way to do it is to execute the following commands as user
 <tt>root</tt>:
 <p/>
 <code>yum-builddep java-1.6.0-openjdk</code>
 <p/>
 <code>yum install gcc gcc-c++</code>
 <p/>
-	      In addition, it's necessary to set a few environment variables for the build:
+In addition, it's necessary to set a few environment variables for the build:
 <p/>
 <code>export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-openjdk</code>
 </blockquote>
 <h4>Fedora 10</h4>
 <p>
 <blockquote>
 After installing <a href="http://fedoraproject.org">Fedora</a> 10
-	      you need to install several build dependencies. The simplest
+you need to install several build dependencies. The simplest
-	      way to do it is to execute the following commands as user
+way to do it is to execute the following commands as user
 <tt>root</tt>:
 <p/>
 <code>yum-builddep java-1.6.0-openjdk</code>
 <p/>
 <code>yum install gcc gcc-c++</code>
 <p/>
-	      In addition, it's necessary to set a few environment variables for the build:
+In addition, it's necessary to set a few environment variables for the build:
 <p/>
 <code>export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-openjdk</code>
 </blockquote>
 <h4>Fedora 11</h4>
 <p>
 <blockquote>
 After installing <a href="http://fedoraproject.org">Fedora</a> 11
-	      you need to install several build dependencies. The simplest
+you need to install several build dependencies. The simplest
-	      way to do it is to execute the following commands as user
+way to do it is to execute the following commands as user
 <tt>root</tt>:
 <p/>
 <code>yum-builddep java-1.6.0-openjdk</code>
 <p/>
 <code>yum install gcc gcc-c++</code>
 <p/>
-	      In addition, it's necessary to set a few environment variables for the build:
+In addition, it's necessary to set a few environment variables for the build:
 <p/>
 <code>export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-openjdk</code>
 </blockquote>
 </blockquote>
 <h3><a name="debian">Debian</a></h3>
 <blockquote>
 <h4>Debian 5.0 (Lenny)</h4>
 <p>
 <blockquote>
-		After installing <a href="http://debian.org">Debian</a> 5
+After installing <a href="http://debian.org">Debian</a> 5
-		you need to install several build dependencies.
+you need to install several build dependencies.
-		The simplest way to install the build dependencies is to
+The simplest way to install the build dependencies is to
-		execute the following commands as user <tt>root</tt>:
+execute the following commands as user <tt>root</tt>:
 <p/>
 <code>aptitude build-dep openjdk-6</code>
 <p/>
 <code>aptitude install openjdk-6-jdk libmotif-dev</code>
 <p/>
-		In addition, it's necessary to set a few environment variables for the build:
+In addition, it's necessary to set a few environment variables for the build:
 <p/>
 <code>export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-6-openjdk</code>
 </blockquote>
 </blockquote>
 <!-- ====================================================== -->
 <h3><a name="ubuntu">Ubuntu</a></h3>
 <blockquote>
 <h4>Ubuntu 8.04</h4>
 <p>
 <blockquote>
-		After installing <a href="http://ubuntu.org">Ubuntu</a> 8.04
+After installing <a href="http://ubuntu.org">Ubuntu</a> 8.04
-		you need to install several build dependencies.
+you need to install several build dependencies.
 <p/>
-		First, you need to enable the universe repository in the
+First, you need to enable the universe repository in the
-		Software Sources application and reload the repository
+Software Sources application and reload the repository
-		information. The Software Sources application is available
+information. The Software Sources application is available
-		under the System/Administration menu.
+under the System/Administration menu.
 <p/>
-		The simplest way to install the build dependencies is to
+The simplest way to install the build dependencies is to
-		execute the following commands:
+execute the following commands:
 <p/>
 <code>sudo aptitude build-dep openjdk-6</code>
 <p/>
 <code>sudo aptitude install openjdk-6-jdk</code>
 <p/>
-		In addition, it's necessary to set a few environment variables for the build:
+In addition, it's necessary to set a few environment variables for the build:
 <p/>
 <code>export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-6-openjdk</code>
 </blockquote>
 <h4>Ubuntu 8.10</h4>
 <p>
 <blockquote>
-		After installing <a href="http://ubuntu.org">Ubuntu</a> 8.10
+After installing <a href="http://ubuntu.org">Ubuntu</a> 8.10
-		you need to install several build dependencies. The simplest
+you need to install several build dependencies. The simplest
-		way to do it is to execute the following commands:
+way to do it is to execute the following commands:
 <p/>
 <code>sudo aptitude build-dep openjdk-6</code>
 <p/>
 <code>sudo aptitude install openjdk-6-jdk</code>
 <p/>
-		In addition, it's necessary to set a few environment variables for the build:
+In addition, it's necessary to set a few environment variables for the build:
 <p/>
 <code>export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-6-openjdk</code>
 </blockquote>
 <h4>Ubuntu 9.04</h4>
 <p>
 <blockquote>
-		After installing <a href="http://ubuntu.org">Ubuntu</a> 9.04
+After installing <a href="http://ubuntu.org">Ubuntu</a> 9.04
-		you need to install several build dependencies. The simplest
+you need to install several build dependencies. The simplest
-		way to do it is to execute the following commands:
+way to do it is to execute the following commands:
 <p/>
 <code>sudo aptitude build-dep openjdk-6</code>
 <p/>
 <code>sudo aptitude install openjdk-6-jdk</code>
 <p/>
-		In addition, it's necessary to set a few environment variables for the build:
+In addition, it's necessary to set a few environment variables for the build:
 <p/>
 <code>export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-6-openjdk</code>
 </blockquote>
 </blockquote>
 <!-- ====================================================== -->
 <h3><a name="opensuse">OpenSUSE</a></h3>
 <blockquote>
 <h4>OpenSUSE 11.1</h4>
 <p>
 <blockquote>
-		After installing <a href="http://opensuse.org">OpenSUSE</a> 11.1
+After installing <a href="http://opensuse.org">OpenSUSE</a> 11.1
-		you need to install several build dependencies.
+you need to install several build dependencies.
-		The simplest way to install the build dependencies is to
+The simplest way to install the build dependencies is to
-		execute the following commands:
+execute the following commands:
 <p/>
 <code>sudo zypper source-install -d java-1_6_0-openjdk</code>
 <p/>
 <code>sudo zypper install make</code>
 <p/>
-		In addition, it is necessary to set a few environment variables for the build:
+In addition, it is necessary to set a few environment variables for the build:
 <p/>
 <code>export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-1.6.0-openjdk</code>
 <p/>
-		Finally, you need to unset the <code>JAVA_HOME</code> environment variable:
+Finally, you need to unset the <code>JAVA_HOME</code> environment variable:
 <p/>
 <code>export -n JAVA_HOME</code>
 </blockquote>
 </blockquote>
 <!-- ====================================================== -->
 <h3><a name="mandriva">Mandriva</a></h3>
 <blockquote>
 <h4>Mandriva Linux One 2009 Spring</h4>
 <p>
 <blockquote>
-		After installing <a href="http://mandriva.org">Mandriva</a> Linux One 2009 Spring
+After installing <a href="http://mandriva.org">Mandriva</a> Linux One 2009 Spring
-		you need to install several build dependencies.
+you need to install several build dependencies.
-		The simplest way to install the build dependencies is to
+The simplest way to install the build dependencies is to
-		execute the following commands as user <tt>root</tt>:
+execute the following commands as user <tt>root</tt>:
 <p/>
 <code>urpmi java-1.6.0-openjdk-devel ant make gcc gcc-c++ freetype-devel zip unzip libcups2-devel libxrender1-devel libalsa2-devel libstc++-static-devel libxtst6-devel libxi-devel</code>
 <p/>
-		In addition, it is necessary to set a few environment variables for the build:
+In addition, it is necessary to set a few environment variables for the build:
 <p/>
 <code>export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-1.6.0-openjdk</code>
 </blockquote>
 </blockquote>
 <!-- ====================================================== -->
 <h3><a name="opensolaris">OpenSolaris</a></h3>
 <blockquote>
 <h4>OpenSolaris 2009.06</h4>
 <p>
 <blockquote>
-		After installing <a href="http://opensolaris.org">OpenSolaris</a> 2009.06
+After installing <a href="http://opensolaris.org">OpenSolaris</a> 2009.06
-		you need to install several build dependencies.
+you need to install several build dependencies.
-		The simplest way to install the build dependencies is to
+The simplest way to install the build dependencies is to
-		execute the following commands:
+execute the following commands:
 <p/>
 <code>pfexec pkg install SUNWgmake SUNWj6dev SUNWant sunstudioexpress SUNWcups SUNWzip SUNWunzip SUNWxwhl SUNWxorg-headers SUNWaudh SUNWfreetype2</code>
 <p/>
-		In addition, it is necessary to set a few environment variables for the build:
+In addition, it is necessary to set a few environment variables for the build:
 <p/>
 <code>export LANG=C ALT_COMPILER_PATH=/opt/SunStudioExpress/bin/ ALT_CUPS_HEADERS_PATH=/usr/include/</code>
 <p/>
-		Finally, you need to make sure that the build process can find the Sun Studio compilers:
+Finally, you need to make sure that the build process can find the Sun Studio compilers:
 <p/>
 <code>export PATH=$PATH:/opt/SunStudioExpress/bin/</code>
 </blockquote>
 </blockquote>
 <!-- ------------------------------------------------------ -->
 could be 3.80, you need 3.81, in which case,
 see the <a href="#buildgmake">"Building GNU make"</a> section.
 </li>
 <li>
 <strong>Windows:</strong>
-Make sure you start your build inside a bash/sh/ksh shell
+Make sure you start your build inside a bash/sh/ksh shell and are
-and are using a <tt>make.exe</tt> utility built for that
+using a <tt>make.exe</tt> utility built for that environment.<br/>
-environment (a cygwin <tt>make.exe</tt> is not the same
+<strong>MKS</strong> builds need a native Windows version of GNU make
-as a <tt>make.exe</tt> built for something like
+(see <a href="#buildgmake">Building GNU make</a>).<br/>
-<a href="http://www.mkssoftware.com/">MKS</a>).
+<strong>Cygwin</strong> builds need
-<br>
+a make version which was specially compiled for the Cygwin environment
-<b>WARNING:</b> Watch out on some make 3.81 versions, it may
+(see <a href="#buildgmake">Building GNU make</a>). <strong>WARNING:</strong>
-not work due to a lack of support for MS-DOS drive letter paths
+the OpenJDK build with the make utility provided by Cygwin will <strong>not</strong>
-like <tt>C:/</tt> or <tt>C:\</tt>.
+work because it does not support drive letters in paths. Make sure that
-<br>
+your version of make will be found before the Cygwins default make by
-You may be able to use the information at the
+setting an appropriate <tt>PATH</tt> environment variable or by removing
-<a href="http://developer.mozilla.org/en/docs/Windows_build_prerequisites_using_cygwin#make" target="_blank">
+Cygwin's make after you built your own make version.<br/>
-mozilla developer center</a>
+<strong>MinGW/MSYS</strong> builds can use the default make which
-on this topic.
+comes with the environment.
-<br>
-It's hoped that when make 3.82 starts shipping in a future cygwin
-release that this MS-DOS path issue will be fixed.
-<br>
-It may be possible to download the version at
-<a href="http://www.cmake.org/files/cygwin/make.exe">
-www.cmake.org make.exe</a>.
-<br>
-It might be necessary for you to build your own GNU make 3.81,
-see the <a href="#buildgmake">"Building GNU make"</a> section
-in that case.
 </li>
 </ul>
 <p>
 Information on GNU make, and access to ftp download sites, are
 available on the
 ftp.gnu.org/pub/gnu/make/</a>.
 </p>
 <!-- ------------------------------------------------------ -->
 <h4><a name="buildgmake">Building GNU make</a></h4>
 <blockquote>
-First step is to get the GNU make 3.81 source from
+First step is to get the GNU make 3.81 (or newer) source from
 <a href="http://ftp.gnu.org/pub/gnu/make/" target="_blank">
 ftp.gnu.org/pub/gnu/make/</a>.
 Building is a little different depending on the OS and unix toolset
 on Windows:
 <ul>
 <li>
 <strong>Solaris:</strong>
 <tt>./configure && gmake CC=gcc</tt>
 </li>
 <li>
-<strong>Windows for CYGWIN:</strong>
+<strong>Windows for CYGWIN:</strong><br/>
-<tt>./configure && make</tt>
+<tt>./configure</tt><br/>
+Add the line <tt>#define HAVE_CYGWIN_SHELL 1</tt> to the end of <tt>config.h</tt><br/>
+<tt>make</tt><br/>
+<br/>
+This should produce <tt>make.exe</tt> in the current directory.
 </li>
 <li>
-<strong>Windows for MKS: (CYGWIN is recommended)</strong>
+<strong>Windows for MKS:</strong><br/>
-<tt>./configure && make -f Makefile.win32</tt>
+Edit <tt>config.h.W32</tt> and uncomment the line <tt>#define HAVE_MKS_SHELL 1</tt><br/>
+Set the environment for your native compiler (e.g. by calling:<br/>
+<tt>"C:\Program Files\Microsoft SDKs\Windows\v7.1\Bin\SetEnv.cmd" /Release /xp /x64)</tt>
+<tt>nmake -f NMakefile.win32</tt>
+<br/>
+This should produce <tt>WinDebug/make.exe</tt> and <tt>WinRel/make.exe</tt>
+<br/>
+If you get the error: <tt>NMAKE : fatal error U1045: spawn failed : Permission denied</tt>
+you have to set the <tt>Read &amp; execute</tt> permission for the file <tt>subproc.bat</tt>.
 </li>
 </ul>
 </blockquote>
 </blockquote>
 <!-- ------------------------------------------------------ -->
 </blockquote>
 <!-- ------------------------------------------------------ -->
 <h4><a name="paths">Windows Paths</a></h4>
 <blockquote>
 <strong>Windows:</strong>
-Note that GNU make is a historic utility and is based very
+Note that GNU make, the shell and other Unix-tools required during the build
-heavily on shell scripting, so it does not tolerate the Windows habit
+do not tolerate the Windows habit
 of having spaces in pathnames or the use of the <tt>\</tt>characters in pathnames.
-Luckily on most Windows systems, you can use <tt>/</tt>instead of \, and
+Luckily on most Windows systems, you can use <tt>/</tt>instead of <tt>\</tt>, and
-there is always a 'short' pathname without spaces for any path that
+there is always a short <a href="http://en.wikipedia.org/wiki/8.3_filename">
-contains spaces.
+	    "8.3" pathname</a> without spaces for any path that contains spaces.
-Unfortunately, this short pathname can be somewhat dynamic and the
+Unfortunately, this short pathname is somewhat dynamic (i.e. dependant on the
-formula is difficult to explain.
+other files and directories inside a given directory) and can not be
-You can use <tt>cygpath</tt> utility to map pathnames with spaces
+algorithmicly calculated by only looking at a specific path name.
-or the <tt>\</tt>character into the <tt>C:/</tt> style of pathname
-(called 'mixed'), e.g.
-<tt>cygpath -s -m "<i>path</i>"</tt>.
 <p>
 The makefiles will try to translate any pathnames supplied
 to it into the <tt>C:/</tt> style automatically.
-<p>
+</p>
-Note that use of CYGWIN creates a unique problem with regards to
+<p>
+Special care has to be taken if native Windows applications
+like <tt>nmake</tt> or <tt>cl</tt> are called with file arguments processed
+by Unix-tools like <tt>make</tt> or <tt>sh</tt>!
+</p>
+</blockquote>
+<!-- ------------------------------------------------------ -->
+<h4><a name="paths">Windows build environments</a></h4>
+<blockquote>
+Building on Windows requires a Unix-like environment, notably a Unix-like shell.
+There are several such environments available of which
+<a href="http://www.mkssoftware.com/products/tk/ds_tkdev.asp">MKS</a>,
+<a href="http://www.cygwin.com/">Cygwin</a> and
+<a href="http://www.mingw.org/wiki/MSYS">MinGW/MSYS</a> are currently supported for
+the OpenJDK build. One of the differences of these three systems is the way
+they handle Windows path names, particularly path names which contain
+spaces, backslashes as path separators and possibly drive letters. Depending
+on the use case and the specifics of each environment these path problems can
+be solved by a combination of quoting whole paths, translating backslashes to
+forward slashes, escaping backslashes with additional backslashes and
+translating the path names to their <a href="http://en.wikipedia.org/wiki/8.3_filename">
+	    "8.3" version</a>.
+<p>
+As of this writing (MKS ver. 9.4, Cygwin ver. 1.7.9, MinGW/MSYS 1.0.17),
+MKS builds are known to be the fastest Windows builds while MingGW/MSYS
+builds are slightly slower (about 10%) than MKS builds and Cygwin builds
+require nearly twice the time (about 180%) of MKS builds (e.g. on a
+DualCore i7 notebook with 8GB of RAM, HDD and 64-bit Windows 7 operating system
+the complete OpenJDK 8 product build takes about 49min with MKS, 54min with
+MinGW/MSYS and 88min with Cygwin).
+</p>
+<p>
+Mixing tools from the different Unix emulation environments is not a good
+idea and will probably not work!
+</p>
+<p>
+<strong>MKS:</strong> is a commercial product which includes
+all the Unix utilities which are required to build the OpenJDK except GNU
+make. In pre-OpenJDK times it was the only supported build environment on
+Windows. The MKS tools support Windows paths with drive letters and
+forward slashes as path separator. Paths in environment variables like (for
+example) <tt>PATH</tt> are separated by semicolon '<tt>;</tt>'.
+</p>
+<p>
+Recent versions of MKS provide the <tt>dosname</tt> utility to convert paths
+with spaces to short (8.3) path names,e .g.
+<tt>dosname -s "<i>path</i>"</tt>.
+</p>
+<p>
+If you are using the MKS environment, you need a native Windows version
+of Gnu make <a href="#buildgmake">which you can easily build yourself</a>.
+</p>
+<p>
+<strong>Cygwin:</strong>
+is an open source, Linux-like environment which tries to emulate
+a complete POSIX layer on Windows. It tries to be smart about path names
+and can usually handle all kinds of paths if they are correctly quoted
+or escaped although internally it maps drive letters <tt>&lt;drive&gt;:</tt>
+to a virtual directory <tt>/cygdrive/&lt;drive&gt;</tt>.
+</p>
+<p>
+You can always use the <tt>cygpath</tt> utility to map pathnames with spaces
+or the backslash character into the <tt>C:/</tt> style of pathname
+(called 'mixed'), e.g. <tt>cygpath -s -m "<i>path</i>"</tt>.
+</p>
+<p>
+Note that the use of CYGWIN creates a unique problem with regards to
 setting <a href="#path"><tt>PATH</tt></a>. Normally on Windows
 the <tt>PATH</tt> variable contains directories
-separated with the ";" character (Solaris and Linux uses ":").
+separated with the ";" character (Solaris and Linux use ":").
 With CYGWIN, it uses ":", but that means that paths like "C:/path"
 cannot be placed in the CYGWIN version  of <tt>PATH</tt> and
 instead CYGWIN uses something like <tt>/cygdrive/c/path</tt>
 which CYGWIN understands, but only CYGWIN understands.
-So be careful with paths on Windows.
+</p>
+<p>
+If you are using the Cygwin environment, you need to
+<a href="#buildgmake">compile your own version</a>
+of GNU make because the default Cygwin make can not handle drive letters in paths.
+</p>
+<p>
+<strong>MinGW/MSYS:</strong>
+MinGW ("Minimalist GNU for Windows") is a collection of free Windows
+specific header files and import libraries combined with GNU toolsets that
+allow one to produce native Windows programs that do not rely on any
+3rd-party C runtime DLLs. MSYS is a supplement to MinGW which allows building
+applications and programs which rely on traditional UNIX tools to
+be present. Among others this includes tools like <tt>bash</tt> and <tt>make</tt>.
+</p>
+<p>
+Like Cygwin, MinGW/MSYS can handle different types of path formats. They
+are internally converted to paths with forward slashes and drive letters
+<tt>&lt;drive&gt;:</tt> replaced by a virtual
+directory <tt>/&lt;drive&gt;</tt>.  Additionally, MSYS automatically
+detects binaries compiled for the MSYS environment and feeds them with the
+internal, Unix-style path names. If native Windows applications are called
+from within MSYS programs their path arguments are automatically converted
+back to Windows style path names with drive letters and backslashes as
+path separators. This may cause problems for Windows applications which
+use forward slashes as parameter separator (e.g. <tt>cl /nologo /I</tt>)
+because MSYS may wrongly <a href="http://mingw.org/wiki/Posix_path_conversion">
+replace such parameters by drive letters</a>.
+</p>
+<p>
+If you are using the MinGW/MSYS system you can use the default make
+version supplied by the environment.
+</p>
 </blockquote>
 <!-- ------------------------------------------------------ -->
 <h4><a name="windows_checklist">Basic Windows Check List</a></h4>
 <blockquote>
 <ol>
 <li>
-Install the
+Install one of the
-<a href="#cygwin">CYGWIN product</a>.
+<a href="#cygwin">CYGWIN</a>, <a href="#msys">MinGW/MSYS</a> or
+<a href="http://www.mkssoftware.com/products/tk/ds_tkdev.asp">MKS</a> environments.
 </li>
 <li>
 Install the
 <a href="#bootjdk">Bootstrap JDK</a>, set
 <tt><a href="#ALT_BOOTDIR">ALT_BOOTDIR</a></tt>.
 <blockquote>
 At a minimum, the
 <a href="http://www.oracle.com/technetwork/server-storage/solarisstudio/downloads/index.htm" target="_blank">
 Sun Studio 12 Update 1 Compilers</a>
 (containing version 5.10 of the C and C++ compilers) is required,
-		    including specific patches.
+including specific patches.
 <p>
-		    The Solaris SPARC patch list is:
+The Solaris SPARC patch list is:
 <ul>
 <li>
 118683-05: SunOS 5.10: Patch for profiling libraries and assembler
 </li>
 <li>
 XRender header files are required for building the
 OpenJDK on Solaris.
 The XRender header file is included with the other X11 header files
 in the package <strong>SFWxwinc</strong> on new enough versions of
 Solaris and will be installed in
-<tt>/usr/X11/include/X11/extensions/Xrender.h</tt>
+<tt>/usr/X11/include/X11/extensions/Xrender.h</tt> or
+<tt>/usr/openwin/share/include/X11/extensions/Xrender.h</tt>
 </p><p>
 <strong>Linux:</strong>
 XRender header files are required for building the
 OpenJDK on Linux.
 The Linux header files are usually available from a "Xrender"
 <tr>
 <td>make.exe</td>
 <td>Devel</td>
 <td>make</td>
 <td>The GNU version of the 'make' utility built for CYGWIN.<br>
-<b>NOTE</b>: See <a href="#gmake">the GNU make section</a></td>
+<b>NOTE</b>: the Cygwin make can not be used to build the
+OpenJDK.  You only need it to build your own version of make
+(see <a href="#gmake">the GNU make section</a>)</td>
 </tr>
 <tr>
 <td>m4.exe</td>
 <td>Interpreters</td>
 <td>m4</td>
 Be very careful with <b><tt>link.exe</tt></b>, it will conflict
 with the Visual Studio version. You need the Visual Studio
 version of <tt>link.exe</tt>, not the CYGWIN one.
 So it's important that the Visual Studio paths in PATH preceed
 the CYGWIN path <tt>/usr/bin</tt>.
+</blockquote>
+<strong> Minimalist GNU for Windows (<a name="msys">MinGW/MSYS</a>)</strong>
+<blockquote>
+Alternatively, the set of unix command tools for the OpenJDK build on
+Windows can be supplied by
+<a href="http://www.mingw.org/wiki/MSYS" target="_blank">MinGW/MSYS</a>.
+<p>
+In addition to the tools which will be installed by default, you have
+to manually install the <tt>msys-zip</tt> and <tt>msys-unzip</tt> packages.
+This can be easily done with the MinGW command line installer:<br/>
+<tt><br/>
+mingw-get.exe install msys-zip<br/>
+mingw-get.exe install msys-unzip<br/>
+</tt>
+</p>
 </blockquote>
 <strong><a name="dxsdk">Microsoft DirectX 9.0 SDK header files and libraries</a></strong>
 <blockquote>
 Microsoft DirectX 9.0 SDK (Summer 2004)
 headers are required for building
 Where each of these directories contain the import JDK image
 for that platform.
 </dd>
 <dt><a name="ALT_OPENWIN_HOME"><tt>ALT_OPENWIN_HOME</tt></a></dt>
 <dd>
-		    The top-level directory of the libraries and include files for the platform's
+The top-level directory of the libraries and include files for the platform's
-		    graphical programming environment. The default location is platform specific.
+graphical programming environment. The default location is platform specific.
-		    For example, on Linux it defaults to <tt>/usr/X11R6/</tt>.
+For example, on Linux it defaults to <tt>/usr/X11R6/</tt>.
-		</dd>
+</dd>
 <dt><strong>Windows specific:</strong></dt>
 <dd>
 <dl>
 <dt><a name="ALT_WINDOWSSDKDIR"><tt>ALT_WINDOWSSDKDIR</tt></a> </dt>
 <dd>
 The location of the
 Microsoft Windows SDK where some tools will be
-			    located.
+located.
-			    The default is whatever WINDOWSSDKDIR is set to
+The default is whatever WINDOWSSDKDIR is set to
-			    (or WindowsSdkDir) or the path
+(or WindowsSdkDir) or the path
 <br>
 <tt>c:\Program Files\Microsoft SDKs\Windows\v7.0a</tt>
 </dd>
 <dt><tt><a name="ALT_DXSDK_PATH">ALT_DXSDK_PATH</a></tt> </dt>
 <dd>
 Set to the target architecture of a cross-compilation build. If set, this
 variable is used to signify that we are cross-compiling. The expectation
 is that <a href="#ALT_COMPILER_PATH"><tt>ALT_COMPILER_PATH</tt></a> is set
 to point to the cross-compiler and that any cross-compilation specific flags
 are passed using <a href="#EXTRA_CFLAGS"><tt>EXTRA_CFLAGS</tt></a>.
-			    The <a href="#ALT_OPENWIN_HOME"><tt>ALT_OPENWIN_HOME</tt></a> variable should
+The <a href="#ALT_OPENWIN_HOME"><tt>ALT_OPENWIN_HOME</tt></a> variable should
-			    also be set to point to the graphical header files (e.g. X11) provided with
+also be set to point to the graphical header files (e.g. X11) provided with
-			    the cross-compiler.
+the cross-compiler.
 When cross-compiling we skip execution of any demos etc that may be built, and
 also skip binary-file verification.
 </dd>
 <dt><tt><a name="EXTRA_CFLAGS">EXTRA_CFLAGS</a></tt> </dt>
 <dd>
-			   Used to pass cross-compilation options to the cross-compiler.
+Used to pass cross-compilation options to the cross-compiler.
 These are added to the <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> variables.
-			</dd>
+</dd>
 <dt><tt><a name="USE_ONLY_BOOTDIR_TOOLS">USE_ONLY_BOOTDIR_TOOLS</a></tt> </dt>
 <dd>
 Used primarily for cross-compilation builds (and always set in that case)
 this variable indicates that tools from the boot JDK should be used during
 the build process, not the tools (<tt>javac</tt>, <tt>javah</tt>, <tt>jar</tt>)
 generate a sanity warning as 64-bit client builds are not directly supported.
 </dd>
 <dt><tt><a name="BUILD_HEADLESS_ONLY"></a>BUILD_HEADLESS_ONLY</tt> </dt>
 <dd>
 Used when the build environment has no graphical capabilities at all. This
-			    excludes building anything that requires graphical libraries to be available.
+excludes building anything that requires graphical libraries to be available.
 </dd>
 <dt><tt><a name="JAVASE_EMBEDDED"></a>JAVASE_EMBEDDED</tt> </dt>
 <dd>
-			    Used to indicate this is a build of the Oracle Java SE Embedded product.
+Used to indicate this is a build of the Oracle Java SE Embedded product.
-			    This will enable the directives included in the SE-Embedded specific build
+This will enable the directives included in the SE-Embedded specific build
-			    files.
+files.
 </dd>
 <dt><tt><a name="LIBZIP_CAN_USE_MMAP">LIBZIP_CAN_USE_MMAP</a></tt> </dt>
 <dd>
-			    If set to false, disables the use of mmap by the zip utility. Otherwise,
+If set to false, disables the use of mmap by the zip utility. Otherwise,
-	                    mmap will be used.
+mmap will be used.
 </dd>
 <dt><tt><a name="COMPRESS_JARS"></a>COMPRESS_JARS</tt> </dt>
 <dd>
-			  If set to true, causes certain jar files that would otherwise be built without
+If set to true, causes certain jar files that would otherwise be built without
-			  compression, to use compression.
+compression, to use compression.
 </dd>
 </dl>
 </dd>
 </dl>
 </blockquote>

changeset 14069	2ca7a2522cb4
parent 12801	948f8ad66ee7
child 15787	496cd89abcc5