README-builds.html 108.2 KB
Newer Older
D
duke 已提交
1 2
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
3 4 5 6 7
    <head>
        <title>OpenJDK Build README</title>
    </head>
    <body style="background-color:lightcyan">
        <!-- ====================================================== -->
8
        <table width="100%">
9 10
            <tr>
                <td align="center">
11 12 13
                    <img alt="OpenJDK" 
                         src="http://openjdk.java.net/images/openjdk.png" 
                         width=256 />
14 15 16 17 18 19 20
                </td>
            </tr>
            <tr>
                <td align=center>
                    <h1>OpenJDK Build README</h1>
                </td>
            </tr>
D
duke 已提交
21
        </table>
22 23 24
        <!-- ------------------------------------------------------ --> 
        <hr>
        <h2><a name="introduction">Introduction</a></h2>
D
duke 已提交
25 26
        <blockquote>
            <p>
27 28 29 30 31 32
                This README file contains build instructions for the
                <a href="http://openjdk.java.net"  target="_blank">OpenJDK</a>.
                Building the source code for the
                OpenJDK
                requires
                a certain degree of technical expertise.
D
duke 已提交
33
        </blockquote>
34 35 36
        <!-- ------------------------------------------------------ -->
        <hr>
        <h2><a name="contents">Contents</a></h2>
D
duke 已提交
37
        <blockquote>
38 39
            <ul>
                <li><a href="#introduction">Introduction</a></li>
40 41 42 43 44
                <li><a href="#hg">Use of Mercurial</a>
                    <ul>
                        <li><a href="#get_source">Getting the Source</a></li>
                    </ul>
                </li>
45
                <li><a href="#MBE">Minimum Build Environments</a></li>
46
                <li><a href="#SDBE">Specific Developer Build Environments</a>
47 48 49
                    <ul>
                        <li><a href="#fedora">Fedora Linux</a> </li>
                        <li><a href="#centos">CentOS Linux</a> </li>
50 51 52 53 54
                        <li><a href="#debian">Debian GNU/Linux</a></li>
                        <li><a href="#ubuntu">Ubuntu Linux</a> </li>
                        <li><a href="#opensuse">OpenSUSE</a></li>
                        <li><a href="#mandriva">Mandriva</a></li>
                        <li><a href="#opensolaris">OpenSolaris</a></li>
55
                    </ul>
56
                </li>
57 58 59 60 61
                <li><a href="#directories">Source Directory Structure</a> 
                    <ul>
                        <li><a href="#drops">Managing the Source Drops</a></li>
                    </ul>
                </li>
62 63 64 65 66 67
                <li><a href="#building">Build Information</a>
                    <ul>
                        <li><a href="#gmake">GNU Make (<tt><i>gmake</i></tt>)</a> </li>
                        <li><a href="#linux">Basic Linux System Setup</a> </li>
                        <li><a href="#solaris">Basic Solaris System Setup</a> </li>
                        <li><a href="#windows">Basic Windows System Setup</a> </li>
68 69 70 71
                        <li><a href="#dependencies">Build Dependencies</a>
                            <ul>
                                <li><a href="#bootjdk">Bootstrap JDK</a> </li>
                                <li><a href="#importjdk">Optional Import JDK</a> </li>
72
                                <li><a href="#ant">Ant 1.7.1</a> </li>
73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103
                                <li><a href="#cacerts">Certificate Authority File (cacert)</a> </li>
                                <li><a href="#compilers">Compilers</a>
                                    <ul>
                                        <li><a href="#msvc32">Microsoft Visual Studio Professional/Express for 32 bit</a> </li>
                                        <li><a href="#msvc64">Microsoft Visual Studio Professional for 64 bit</a> </li>
                                        <li><a href="#mssdk64">Microsoft Windows SDK for 64 bit</a> </li>
                                        <li><a href="#gcc">Linux gcc/binutils</a> </li>
                                        <li><a href="#studio">Sun Studio</a> </li>
                                    </ul>
                                </li>
                                <li><a href="#zip">Zip and Unzip</a> </li>
                                <li><a href="#freetype">FreeType2 Fonts</a> </li>
                                <li>Linux and Solaris:
                                    <ul>
                                        <li><a href="#cups">CUPS Include files</a> </li>
                                        <li><a href="#xrender">XRender Include files</a></li>
                                    </ul>
                                </li>
                                <li>Linux only:
                                    <ul>
                                        <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><a href="#dxsdk">DirectX 9.0 SDK</a> </li>
                                    </ul>
                                </li>
                            </ul>
                        </li>
104 105 106 107 108 109 110
                    </ul>
                </li>
                <li><a href="#creating">Creating the Build</a> </li>
                <li><a href="#testing">Testing the Build</a> </li>
                <li><a href="#variables">Environment/Make Variables</a></li>
                <li><a href="#troubleshooting">Troubleshooting</a></li>
            </ul>
D
duke 已提交
111
        </blockquote>
112 113 114 115 116 117 118 119 120

        <!-- ------------------------------------------------------ -->
        <hr>
        <h2><a name="hg">Use of Mercurial</a></h2>
        <blockquote>
            The OpenJDK sources are maintained with the revision control system
            <a href="http://mercurial.selenic.com/wiki/Mercurial">Mercurial</a>.
            If you are new to Mercurial, please see the
            <a href="http://mercurial.selenic.com/wiki/BeginnersGuides">Beginner Guides</a>
121
            or refer to the <a href="http://hgbook.red-bean.com/">Mercurial Book</a>.
122 123 124 125
            The first few chapters of the book provide an excellent overview of
            Mercurial, what it is and how it works.
            <br>
            For using Mercurial with the OpenJDK refer to the
126 127
            <a href="http://openjdk.java.net/guide/repositories.html#installConfig">
                Developer Guide: Installing and Configuring Mercurial</a>
128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152
            section for more information.
            The Forest Extension is not part of the Mercurial install,
            and is optional,
            but can be obtained with the following commands:
            <blockquote>
                <tt>
                    hg clone https://bitbucket.org/pmezard/hgforest-crew/overview/ <i>YourHgForest</i>
                </tt>
            </blockquote>
            Once you have the file <tt>forest.py</tt>, you need to add these
            lines to your <tt>${HOME}/.hgrc</tt> file:
            <blockquote>
                <tt>
                    [extensions]
                    <br>forest = <i>YourHgForest</i>/forest.py
                </tt>
            </blockquote>

            <!-- ------------------------------------------------------ -->
            <h3><a name="get_source">Getting the Source</a></h3>
            <blockquote>
                To get the entire set of OpenJDK Mercurial repositories
                using the Forest Extension:
                <blockquote>
                    <tt>
153
                        hg fclone http://hg.openjdk.java.net/jdk7/jdk7 <i>YourOpenJDK</i>
154 155 156 157 158 159
                    </tt>
                </blockquote>
                To get the entire set of OpenJDK Mercurial repositories
                without using the Forest Extension:
                <blockquote>
                    <tt>
160
                        hg clone http://hg.openjdk.java.net/jdk7/jdk7 <i>YourOpenJDK</i>
161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181
                        <br>cd <i>YourOpenJDK</i>
                        <br>sh ./get_source.sh
                    </tt>
                </blockquote>
                Once you have all the repositories, the
                script <tt>make/scripts/hgforest.sh</tt>
                can be used to repeat the same <tt>hg</tt>
                command on every repository in the forest, e.g.
                <blockquote>
                    <tt>
                        cd <i>YourOpenJDK</i>
                        <br>sh ./make/scripts/hgforest.sh pull -u
                    </tt>
                </blockquote>
                You may find this script <tt>make/scripts/hgforest.sh</tt> faster
                than the <tt>hg</tt> forest commands provided by the
                Forest Extension.
            </blockquote>

        </blockquote>

182 183 184
        <!-- ------------------------------------------------------ -->
        <hr>
        <h2><a name="MBE">Minimum Build Environments</a></h2>
D
duke 已提交
185
        <blockquote>
186
            This file often describes specific requirements for what we call the
187 188
            "minimum build environments" (MBE) for this 
	    specific release of the JDK,
189 190 191 192 193 194 195 196
            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.
            It is understood that most developers will NOT be using these 
            specific platforms, and in fact creating these specific platforms
            may be difficult due to the age of some of this software.
D
duke 已提交
197
            <p>
198 199
                The minimum OS and C/C++ compiler versions needed for building the
                OpenJDK:
D
duke 已提交
200
            <p>
201 202 203 204 205
            <table border="1">
                <thead>
                    <tr>
                        <th>Base OS and Architecture</th>
                        <th>OS</th>
206
                        <th>C/C++ Compiler</th>
207
                        <th>BOOT JDK</th>
208 209 210 211
                    </tr>
                </thead>
                <tbody>
                    <tr>
212 213
                        <td>Linux X86 (32-bit)</td>
                        <td>Fedora 9</td>
214 215
                        <td>gcc 4.3 </td>
                        <td>JDK 6u18</td>
216 217
                    </tr>
                    <tr>
218 219
                        <td>Linux X64 (64-bit)</td>
                        <td>Fedora 9</td>
220 221
                        <td>gcc 4.3 </td>
                        <td>JDK 6u18</td>
222 223
                    </tr>
                    <tr>
224
                        <td>Solaris SPARC (32-bit)</td>
225
                        <td>Solaris 10 Update 6</td>
226
                        <td>Sun Studio 12 Update 1 + patches</td>
227
                        <td>JDK 6u18</td>
228 229
                    </tr>
                    <tr>
230
                        <td>Solaris SPARCV9 (64-bit)</td>
231
                        <td>Solaris 10 Update 6</td>
232
                        <td>Sun Studio 12 Update 1 + patches</td>
233
                        <td>JDK 6u18</td>
234 235
                    </tr>
                    <tr>
236
                        <td>Solaris X86 (32-bit)</td>
237
                        <td>Solaris 10 Update 6</td>
238
                        <td>Sun Studio 12 Update 1 + patches</td>
239
                        <td>JDK 6u18</td>
240 241
                    </tr>
                    <tr>
242
                        <td>Solaris X64 (64-bit)</td>
243
                        <td>Solaris 10 Update 6</td>
244
                        <td>Sun Studio 12 Update 1 + patches</td>
245
                        <td>JDK 6u18</td>
246 247
                    </tr>
                    <tr>
248
                        <td>Windows X86 (32-bit)</td>
249
                        <td>Windows XP</td>
250
                        <td>Microsoft Visual Studio C++ 2010 Professional Edition</td>
251
                        <td>JDK 6u18</td>
252 253
                    </tr>
                    <tr>
254
                        <td>Windows X64 (64-bit)</td>
255
                        <td>Windows Server 2003 - Enterprise x64 Edition</td>
256
                        <td>Microsoft Visual Studio C++ 2010 Professional Edition</td>
257
                        <td>JDK 6u18</td>
258 259 260
                    </tr>
                </tbody>
            </table>
261
            <p>
262 263
	    These same sources do indeed build on many more systems than the
	    above older generation systems, again the above is just a minimum.
264
            <p>
265 266 267
	    Compilation problems with newer or different C/C++ compilers is a
	    common problem.
	    Similarly, compilation problems related to changes to the
268
                <tt>/usr/include</tt> or system header files is also a
269 270 271
	    common problem with newer or unreleased OS versions.
	    Please report these types of problems as bugs so that they
	    can be dealt with accordingly.
272 273 274 275 276 277 278
        </blockquote>
        <!-- ------------------------------------------------------ -->
        <hr>
        <h2><a name="SDBE">Specific Developer Build Environments</a></h2>
        <blockquote>
            We won't be listing all the possible environments, but
            we will try to provide what information we have available to us.
D
duke 已提交
279
        </blockquote>
280
        <!-- ------------------------------------------------------ -->
281
        <h3><a name="fedora">Fedora</a></h3>
D
duke 已提交
282
        <blockquote>
283 284 285 286
            <h4>Fedora 9</h4>
            <p>
            <blockquote>
                After installing <a href="http://fedoraproject.org">Fedora</a> 9
287 288
	      you need to install several build dependencies. The simplest
	      way to do it is to execute the following commands as user 
289 290
                <tt>root</tt>:
                <p/>
291
                <code>yum-builddep java-1.6.0-openjdk</code>
292 293 294
                <p/>
                <code>yum install gcc gcc-c++</code>
                <p/>
295 296
	      In addition, it's necessary to set a few environment variables for the build:

297 298
                <p/>
                <code>export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-openjdk</code>
299
            </blockquote>
300 301 302 303
            <h4>Fedora 10</h4>
            <p>
            <blockquote>
                After installing <a href="http://fedoraproject.org">Fedora</a> 10
304 305
	      you need to install several build dependencies. The simplest
	      way to do it is to execute the following commands as user 
306 307 308 309 310 311
                <tt>root</tt>:
                <p/>
                <code>yum-builddep java-1.6.0-openjdk</code>
                <p/>
                <code>yum install gcc gcc-c++</code>
                <p/>
312 313
	      In addition, it's necessary to set a few environment variables for the build:

314 315
                <p/>
                <code>export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-openjdk</code>
316
            </blockquote>
317 318 319 320
            <h4>Fedora 11</h4>
            <p>
            <blockquote>
                After installing <a href="http://fedoraproject.org">Fedora</a> 11
321 322
	      you need to install several build dependencies. The simplest
	      way to do it is to execute the following commands as user 
323 324 325 326 327 328
                <tt>root</tt>:
                <p/>
                <code>yum-builddep java-1.6.0-openjdk</code>
                <p/>
                <code>yum install gcc gcc-c++</code>
                <p/>
329 330
	      In addition, it's necessary to set a few environment variables for the build:

331 332 333
                <p/>
                <code>export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-openjdk</code>
            </blockquote>
334 335
        </blockquote>
        <!-- ------------------------------------------------------ -->
336
        <h3><a name="centos">CentOS 5.5</a></h3>
337
        <blockquote>
338
            After installing
339
            <a href="http://www.centos.org/">CentOS 5.5</a>
340 341 342 343 344 345 346
            you need to make sure you have
            the following Development bundles installed:
            <blockquote>
                <ul>
                    <li>Development Libraries</li>
                    <li>Development Tools</li>
                    <li>Java Development</li>
347
                    <li>X Software Development (Including XFree86-devel)</li>
348 349 350
                </ul>
            </blockquote>
            <p>
351
                Plus the following packages:
352 353 354 355 356 357 358 359 360
            <blockquote>
                <ul>
                    <li>cups devel: Cups Development Package</li>
                    <li>alsa devel: Alsa Development Package</li>
                    <li>ant: Ant Package</li>
                    <li>Xi devel: libXi.so Development Package</li>
                </ul>
            </blockquote>
            <p>
361 362 363 364 365 366
                The freetype 2.3 packages don't seem to be available,
                but the freetype 2.3 sources can be downloaded, built,
                and installed easily enough from
                <a href="http://downloads.sourceforge.net/freetype">
                    the freetype site</a>.
                Build and install with something like:
367 368 369 370
            <blockquote>
                <tt>./configure && make && sudo -u root make install</tt>
            </blockquote>
            <p>
371 372 373
                Mercurial packages could not be found easily, but a Google
                search should find ones, and they usually include Python if
                it's needed.
374 375
        </blockquote>
        <!-- ------------------------------------------------------ -->
376
        <h3><a name="debian">Debian</a></h3>
377
        <blockquote>
378
            <h4>Debian 5.0 (Lenny)</h4>
D
duke 已提交
379
            <p>
380
            <blockquote>
381 382 383 384
		After installing <a href="http://debian.org">Debian</a> 5 
		you need to install several build dependencies. 
		The simplest way to install the build dependencies is to 
		execute the following commands as user <tt>root</tt>:
385 386 387 388 389
                <p/>
                <code>aptitude build-dep openjdk-6</code>
                <p/>
                <code>aptitude install openjdk-6-jdk libmotif-dev</code>
                <p/>
390
		In addition, it's necessary to set a few environment variables for the build:
391 392 393
                <p/>
                <code>export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-6-openjdk</code>
            </blockquote>
394 395
        </blockquote>
        <!-- ====================================================== -->
396
        <h3><a name="ubuntu">Ubuntu</a></h3>
397 398
        <blockquote>
            <h4>Ubuntu 8.04</h4>
D
duke 已提交
399
            <p>
400
            <blockquote>
401 402
		After installing <a href="http://ubuntu.org">Ubuntu</a> 8.04 
		you need to install several build dependencies. 
403
                <p/>
404 405 406 407
		First, you need to enable the universe repository in the 
		Software Sources application and reload the repository 
		information. The Software Sources application is available 
		under the System/Administration menu. 
408
                <p/>
409 410
		The simplest way to install the build dependencies is to 
		execute the following commands:
411 412 413 414 415
                <p/>
                <code>sudo aptitude build-dep openjdk-6</code>
                <p/>
                <code>sudo aptitude install openjdk-6-jdk</code>
                <p/>
416
		In addition, it's necessary to set a few environment variables for the build:
417 418 419 420
                <p/>
                <code>export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-6-openjdk</code>
            </blockquote>
            <h4>Ubuntu 8.10</h4>
D
duke 已提交
421
            <p>
422
            <blockquote>
423 424 425
		After installing <a href="http://ubuntu.org">Ubuntu</a> 8.10 
		you need to install several build dependencies. The simplest
		way to do it is to execute the following commands:
426 427 428 429 430
                <p/>
                <code>sudo aptitude build-dep openjdk-6</code>
                <p/>
                <code>sudo aptitude install openjdk-6-jdk</code>
                <p/>
431
		In addition, it's necessary to set a few environment variables for the build:
432 433 434 435
                <p/>
                <code>export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-6-openjdk</code>
            </blockquote>
            <h4>Ubuntu 9.04</h4>
D
duke 已提交
436
            <p>
437
            <blockquote>
438 439 440
		After installing <a href="http://ubuntu.org">Ubuntu</a> 9.04 
		you need to install several build dependencies. The simplest
		way to do it is to execute the following commands:
441 442 443 444 445
                <p/>
                <code>sudo aptitude build-dep openjdk-6</code>
                <p/>
                <code>sudo aptitude install openjdk-6-jdk</code>
                <p/>
446
		In addition, it's necessary to set a few environment variables for the build:
447 448 449
                <p/>
                <code>export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-6-openjdk</code>
            </blockquote>
450
        </blockquote>
451 452 453 454 455
        <!-- ====================================================== -->
        <h3><a name="opensuse">OpenSUSE</a></h3>
        <blockquote>
            <h4>OpenSUSE 11.1</h4>
            <p>
456
            <blockquote>
457 458 459 460
		After installing <a href="http://opensuse.org">OpenSUSE</a> 11.1 
		you need to install several build dependencies. 
		The simplest way to install the build dependencies is to 
		execute the following commands:
461 462 463 464 465
                <p/>
                <code>sudo zypper source-install -d java-1_6_0-openjdk</code>
                <p/>
                <code>sudo zypper install make</code>
                <p/>
466
		In addition, it is necessary to set a few environment variables for the build:
467 468 469
                <p/>
                <code>export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-1.6.0-openjdk</code>
                <p/>
470
		Finally, you need to unset the <code>JAVA_HOME</code> environment variable:
471 472 473 474
                <p/>
                <code>export -n JAVA_HOME</code>
            </blockquote>
        </blockquote>
475 476 477 478 479
        <!-- ====================================================== -->
        <h3><a name="mandriva">Mandriva</a></h3>
        <blockquote>
            <h4>Mandriva Linux One 2009 Spring</h4>
            <p>
480
            <blockquote>
481 482 483 484
		After installing <a href="http://mandriva.org">Mandriva</a> Linux One 2009 Spring 
		you need to install several build dependencies. 
		The simplest way to install the build dependencies is to 
		execute the following commands as user <tt>root</tt>:
485 486
                <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>
487 488
                <p/>
		In addition, it is necessary to set a few environment variables for the build:
489 490 491
                <p/>
                <code>export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-1.6.0-openjdk</code>
            </blockquote>
492 493 494 495 496 497
        </blockquote>
        <!-- ====================================================== -->
        <h3><a name="opensolaris">OpenSolaris</a></h3>
        <blockquote>
            <h4>OpenSolaris 2009.06</h4>
            <p>
498
            <blockquote>
499 500 501 502
		After installing <a href="http://opensolaris.org">OpenSolaris</a> 2009.06 
		you need to install several build dependencies. 
		The simplest way to install the build dependencies is to 
		execute the following commands:
503 504
                <p/>
                <code>pfexec pkg install SUNWgmake SUNWj6dev SUNWant sunstudioexpress SUNWcups SUNWzip SUNWunzip SUNWxwhl SUNWxorg-headers SUNWaudh SUNWfreetype2</code>
505 506
                <p/>
		In addition, it is necessary to set a few environment variables for the build:
507 508 509
                <p/>
                <code>export LANG=C ALT_COMPILER_PATH=/opt/SunStudioExpress/bin/ ALT_CUPS_HEADERS_PATH=/usr/include/</code>
                <p/>
510
		Finally, you need to make sure that the build process can find the Sun Studio compilers:
511 512 513
                <p/>
                <code>export PATH=$PATH:/opt/SunStudioExpress/bin/</code>
            </blockquote>
514 515
        </blockquote>
        <!-- ------------------------------------------------------ -->  
516 517 518
        <hr>
        <h2><a name="directories">Source Directory Structure</a></h2>
        <blockquote>
D
duke 已提交
519
            <p>
520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542
                The source code for the OpenJDK is delivered in a set of
                directories:
                <tt>hotspot</tt>,
                <tt>langtools</tt>,
                <tt>corba</tt>,
                <tt>jaxws</tt>,
                <tt>jaxp</tt>,
                and
                <tt>jdk</tt>.
                The <tt>hotspot</tt> directory contains the source code and make
                files for building the OpenJDK Hotspot Virtual Machine.
                The <tt>langtools</tt> directory contains the source code and make
                files for building the OpenJDK javac and language tools.
                The <tt>corba</tt> directory contains the source code and make
                files for building the OpenJDK Corba files.
                The <tt>jaxws</tt> directory contains the source code and make
                files for building the OpenJDK JAXWS files.
                The <tt>jaxp</tt> directory contains the source code and make
                files for building the OpenJDK JAXP files.
                The <tt>jdk</tt> directory contains the source code and make files for
                building the OpenJDK runtime libraries and misc files.
                The top level <tt>Makefile</tt>
                is used to build the entire OpenJDK.
543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632

            <h3><a name="drops">Managing the Source Drops</a></h3>
            <blockquote>
                <p>
                    The repositories <tt>jaxp</tt> and <tt>jaxws</tt> actually
                    do not contain the sources for JAXP or JAX-WS.
                    These products have their own open source procedures at their
                    <a href="http://jaxp.java.net/">JAXP</a> and
                    <a href="http://jax-ws.java.net/">JAX-WS</a> home pages.
                    The OpenJDK project does need access to these sources to build
                    a complete JDK image because JAXP and JAX-WS are part of the JDK.
                    The current process for delivery of the JAXP and JAX-WS sources
                    involves so called "source drop bundles" downloaded from a public
                    website.
                    There are many reasons for this current mechanism, and it is
                    understood that this is not ideal for the open source community.
                    It is possible this process could change in the future.
                    <br>
                    <b>NOTE:</b> The <a href="http://download.java.net/openjdk/jdk7/">
                        Complete OpenJDK Source Bundles</a> <u>will</u> contain the JAXP and
                    JAX-WS sources.
                </p>

                <h4><a name="dropcreation">Creation of New Source Drop Bundles</a></h4>
                <blockquote>
                    <ol>
                        <li>
                            The JAXP or JAX-WS team prepares a new zip bundle,
                            places a copy in a public download area on java.net,
                            sends us a link and a list of CRs (Change Request Numbers).
                            The older download bundles should not be deleted.
                            It is the responsibility of the JAXP and JAX-WS team to
                            place the proper GPL legal notices on the sources
                            and do any filtering or java re-packaging for the
                            OpenJDK instances of these classes.
                        </li>
                        <li>
                            The OpenJDK team copies this new bundle into shared
                            area (e.g. <tt>/java/devtools/share/jdk7-drops</tt>).
                            Older bundles are never deleted so we retain the history.
                        </li>
                        <li>
                            The OpenJDK team edits the ant property file
                            <tt>jaxp/jaxp.properties</tt> or
                            <tt>jaxws/jaxws.properties</tt> to update the
                            base URL, the zip bundle name, and the MD5 checksum
                            of the zip bundle
                            (on Solaris: <tt>sum -c md5 <i>bundlename</i></tt>)
                        </li>
                        <li>
                            OpenJDK team reviews and commits those changes with the
                            given CRs.
                        </li>
                    </ol>
                </blockquote>

                <h4><a name="dropusage">Using Source Drop Bundles</a></h4>
                <blockquote>
                    <p>
                        The ant scripts that build <tt>jaxp</tt> and <tt>jaxws</tt>
                        will attempt to locate these zip bundles from the directory
                        in the environment variable
                        <tt><a href="#ALT_DROPS_DIR">ALT_DROPS_DIR</a></tt>.
                        The checksums protect from getting the wrong, corrupted, or
                        improperly modified sources.
                        Once the sources are made available, the population will not
                        happen again unless a <tt>make clobber</tt> is requested
                        or the <tt>jaxp/drop/</tt> or <tt>jaxws/drop/</tt>
                        directory is explicitly deleted.
                        <br>
                        <b>NOTE:</b> The default Makefile and ant script behavior
                        is to NOT download these bundles from the public http site.
                        In general, doing downloads
                        during the build process is not advised, it creates too much
                        unpredictability in the build process.
                        However, you can use <tt>make ALLOW_DOWNLOADS=true</tt> to
                        tell the ant script that the download of the zip bundle is
                        acceptable.
                    </p>
                    <p>
                        The recommended procedure for keeping a cache of these
                        source bundles would be to download them once, place them
                        in a directory outside the repositories, and then set
                        <tt><a href="#ALT_DROPS_DIR">ALT_DROPS_DIR</a></tt> to refer
                        to that directory.
                        These drop bundles do change occasionally, so the newer
                        bundles may need to be added to this area from time to time.
                    </p>
                </blockquote>
            </blockquote>
633 634 635 636 637 638
        </blockquote>
        <!-- ------------------------------------------------------ -->
        <hr>
        <h2><a name="building">Build Information</a></h2>
        <blockquote>
            Building the OpenJDK
639 640 641
            is done with a <a href="#gmake">GNU <tt>make</tt></a> command line
            and various
            environment or make variable settings that direct the makefile rules
642 643 644 645 646 647 648 649
            to where various components have been installed.
            Where possible the makefiles will attempt to located the various
            components in the default locations or any component specific 
            variable settings.
            When the normal defaults fail or components cannot be found,
            the various
            <tt>ALT_*</tt> variables (alternates)
            can be used to help the makefiles locate components.
D
duke 已提交
650
            <p>
651 652 653 654
                Refer to the bash/sh/ksh setup file
                <tt>jdk/make/jdk_generic_profile.sh</tt>
                if you need help in setting up your environment variables.
                A build could be as simple as:
D
duke 已提交
655
            <blockquote>
656 657 658
                <pre><tt>
                bash
                . jdk/make/jdk_generic_profile.sh
659
                <a href="#gmake"><tt>make</tt></a> sanity &amp;&amp; <a href="#gmake"><tt>make</tt></a>
660
                </tt></pre>
D
duke 已提交
661
            </blockquote>
662
            <p>
663 664 665 666 667 668
                Of course ksh or sh would work too.
                But some customization will probably be necessary.
                The <tt>sanity</tt> rule will make some basic checks on build
                dependencies and generate appropriate warning messages
                regarding missing, out of date, or newer than expected components
                found on your system.
D
duke 已提交
669
        </blockquote>
670 671 672
        <!-- ------------------------------------------------------ -->
        <hr>
        <h3><a name="gmake">GNU make (<tt><i>gmake</i></tt>)</a></h3>
D
duke 已提交
673
        <blockquote>
674 675 676 677 678 679
            The Makefiles in the OpenJDK are only valid when used with the 
            GNU version of the utility command <tt>make</tt>
            (<tt><i>gmake</i></tt>).
            A few notes about using GNU make:
            <ul>
                <li>
680
                    You need GNU make version 3.81 or newer.
681 682 683 684 685 686
                </li>
                <li>
                    Place the location of the GNU make binary in the <tt>PATH</tt>. 
                </li>
                <li>
                    <strong>Linux:</strong>
687 688 689 690
                    The <tt>/usr/bin/make</tt> should be 3.81 or newer
                    and should work fine for you.
                    If this version is not 3.81 or newer,
                    see the <a href="#buildgmake">"Building GNU make"</a> section.
691 692 693 694 695 696
                </li>
                <li>
                    <strong>Solaris:</strong>
                    Do NOT use <tt>/usr/bin/make</tt> on Solaris.
                    If your Solaris system has the software
                    from the Solaris Companion CD installed, 
697
                    you should try and use <tt>gmake</tt>
698 699
                    which will be located in either the <tt>/opt/sfw/bin</tt> or 
                    <tt>/usr/sfw/bin</tt> directory.
700 701 702 703 704
                    In more recent versions of Solaris GNU make might be found
                    at <tt>/usr/bin/gmake</tt>.<br>
                    <b>NOTE:</b> It is very likely that this <tt>gmake</tt>
                    could be 3.80, you need 3.81, in which case,
                    see the <a href="#buildgmake">"Building GNU make"</a> section.
705 706 707
                </li>
                <li>
                    <strong>Windows:</strong>
708 709 710 711 712
                    Make sure you start your build inside a bash/sh/ksh shell
                    and are using a <tt>make.exe</tt> utility built for that
                    environment (a cygwin <tt>make.exe</tt> is not the same
                    as a <tt>make.exe</tt> built for something like
                    <a href="http://www.mkssoftware.com/">MKS</a>). 
713
                    <br>
714
                    <b>WARNING:</b> Watch out on some make 3.81 versions, it may
715 716 717
                    not work due to a lack of support for MS-DOS drive letter paths
                    like <tt>C:/</tt> or <tt>C:\</tt>.
                    <br>
718
                    You may be able to use the information at the
719
                    <a href="http://developer.mozilla.org/en/docs/Windows_build_prerequisites_using_cygwin#make" target="_blank">
720
                        mozilla developer center</a>
721
                    on this topic.
722 723 724
                    <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.
725 726
                    <br>
                    It may be possible to download the version at
727
                    <a href="http://www.cmake.org/files/cygwin/make.exe">
728 729 730 731 732
                        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.
733 734 735
                </li>
            </ul>
            <p>
736 737 738 739 740 741 742 743
                Information on GNU make, and access to ftp download sites, are
                available on the
                <a href="http://www.gnu.org/software/make/make.html" target="_blank">
                    GNU make web site
                </a>.
                The latest source to GNU make is available at
                <a href="http://ftp.gnu.org/pub/gnu/make/" target="_blank">
                    ftp.gnu.org/pub/gnu/make/</a>.
744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771
            </p>
            <!-- ------------------------------------------------------ -->
            <h4><a name="buildgmake">Building GNU make</a></h4>
            <blockquote>
                First step is to get the GNU make 3.81 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>Linux:</strong>
                        <tt>./configure && make</tt>
                    </li>
                    <li>
                        <strong>Solaris:</strong>
                        <tt>./configure && gmake CC=gcc</tt>
                    </li>
                    <li>
                        <strong>Windows for CYGWIN:</strong>
                        <tt>./configure && make</tt>
                    </li>
                    <li>
                        <strong>Windows for MKS: (CYGWIN is recommended)</strong>
                        <tt>./configure && make -f Makefile.win32</tt>
                    </li>
                </ul>
            </blockquote>
772 773 774 775 776 777 778 779 780 781
        </blockquote>
        <!-- ------------------------------------------------------ -->
        <hr>
        <h3><a name="linux">Basic Linux System Setup</a></h3>
        <blockquote>
            <strong>i586 only:</strong>
            The minimum recommended hardware for building the Linux version
            is a Pentium class processor or better, at least 256 MB of RAM, and
            approximately 1.5 GB of free disk space.
            <p> 
782 783 784 785
                <strong>X64 only:</strong>
                The minimum recommended hardware for building the Linux
                version is an AMD Opteron class processor, at least 512 MB of RAM, and
                approximately 4 GB of free disk space.
786
            <p> 
787 788 789 790 791 792
                The build will use the tools contained in
                <tt>/bin</tt> and
                <tt>/usr/bin</tt>
                of a standard installation of the Linux operating environment.
                You should ensure that these directories are in your
                <tt>PATH</tt>.
D
duke 已提交
793
            <p>
794 795 796 797 798 799 800 801 802
                Note that some Linux systems have a habit of pre-populating
                your environment variables for you, for example <tt>JAVA_HOME</tt>
                might get pre-defined for you to refer to the JDK installed on
                your Linux system.
                You will need to unset <tt>JAVA_HOME</tt>.
                It's a good idea to run <tt>env</tt> and verify the
                environment variables you are getting from the default system
                settings make sense for building the
                OpenJDK.
D
duke 已提交
803
        </blockquote>
804 805 806 807 808 809 810 811 812 813 814 815 816 817 818
        <!-- ------------------------------------------------------ -->
        <h4><a name="linux_checklist">Basic Linux Check List</a></h4>
        <blockquote>
            <ol>
                <li>
                    Install the
                    <a href="#bootjdk">Bootstrap JDK</a>, set
                    <tt><a href="#ALT_BOOTDIR">ALT_BOOTDIR</a></tt>.
                </li>
                <li>
                    <a href="#importjdk">Optional Import JDK</a>, set
                    <tt><a href="#ALT_JDK_IMPORT_PATH">ALT_JDK_IMPORT_PATH</a></tt>.
                </li>
                <li>
                    Install or upgrade the <a href="#freetype">FreeType development
819
                        package</a>.
820
                </li>
821 822
                <li>
                    Install
823
                    <a href="#ant">Ant 1.7.1 or newer</a>,
824
                    make sure it is in your PATH.
825
                </li>
826 827 828 829 830 831 832 833 834 835 836 837 838
            </ol>
        </blockquote>
        <!-- ------------------------------------------------------ -->
        <hr>
        <h3><a name="solaris">Basic Solaris System Setup</a></h3>
        <blockquote>
            The minimum recommended hardware for building the
            Solaris SPARC version is an UltraSPARC with 512 MB of RAM. 
            For building
            the Solaris x86 version, a Pentium class processor or better and at
            least 512 MB of RAM are recommended. 
            Approximately 1.4 GB of free disk
            space is needed for a 32-bit build.
D
duke 已提交
839
            <p>
840 841 842 843 844 845
                If you are building the 64-bit version, you should
                run the command "isainfo -v" to verify that you have a
                64-bit installation, it should say <tt>sparcv9</tt> or
                <tt>amd64</tt>.
                An additional 7 GB of free disk space is needed
                for a 64-bit build.
846
            <p> 
847 848 849
                The build uses the tools contained in <tt>/usr/ccs/bin</tt>
                and <tt>/usr/bin</tt> of a standard developer or full installation of
                the Solaris operating environment.
850
            <p> 
851 852 853 854 855 856
                Solaris patches specific to the JDK can be downloaded from the
                <a href="http://sunsolve.sun.com/show.do?target=patches/JavaSE" target="_blank">
                    SunSolve JDK Solaris patches download page</a>.
                You should ensure that the latest patch cluster for
                your version of the Solaris operating environment has also
                been installed.
857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880
        </blockquote>
        <!-- ------------------------------------------------------ -->
        <h4><a name="solaris_checklist">Basic Solaris Check List</a></h4>
        <blockquote>
            <ol>
                <li>
                    Install the
                    <a href="#bootjdk">Bootstrap JDK</a>, set
                    <tt><a href="#ALT_BOOTDIR">ALT_BOOTDIR</a></tt>.
                </li>
                <li>
                    <a href="#importjdk">Optional Import JDK</a>, set
                    <tt><a href="#ALT_JDK_IMPORT_PATH">ALT_JDK_IMPORT_PATH</a></tt>.
                </li>
                <li>
                    Install the
                    <a href="#studio">Sun Studio Compilers</a>, set
                    <a href="#ALT_COMPILER_PATH"><tt>ALT_COMPILER_PATH</tt></a>.
                </li>
                <li>
                    Install the
                    <a href="#cups">CUPS Include files</a>, set
                    <tt><a href="#ALT_CUPS_HEADERS_PATH">ALT_CUPS_HEADERS_PATH</a></tt>.
                </li>
881 882 883
                <li>
                    Install the <a href="#xrender">XRender Include files</a>.
                </li>
884 885
                <li>
                    Install
886
                    <a href="#ant">Ant 1.7.1 or newer</a>,
887
                    make sure it is in your PATH.
888
                </li>
889 890 891 892 893 894
            </ol>
        </blockquote>
        <!-- ------------------------------------------------------ -->
        <hr>
        <h3><a name="windows">Basic Windows System Setup</a></h3>
        <blockquote> 
D
duke 已提交
895
            <strong>i586 only:</strong>
896
            The minimum recommended hardware for building the 32-bit or X86
897 898 899
            Windows version is an Pentium class processor or better, at least
            512 MB of RAM, and approximately 600 MB of free disk space.
            <strong>
900
                NOTE: The Windows build machines need to use the
901 902 903 904
                file system NTFS. 
                Build machines formatted to FAT32 will not work 
                because FAT32 doesn't support case-sensitivity in file names.
            </strong>
D
duke 已提交
905
            <p> 
906 907 908 909
                <strong>X64 only:</strong>
                The minimum recommended hardware for building
                the Windows X64 version is an AMD Opteron class processor, at least 1
                GB of RAM, and approximately 10 GB of free disk space.
D
duke 已提交
910
        </blockquote>
911 912
        <!-- ------------------------------------------------------ -->
        <h4><a name="paths">Windows Paths</a></h4>
D
duke 已提交
913
        <blockquote>
914 915 916 917 918 919 920 921 922 923 924 925 926
            <strong>Windows:</strong>
            Note that GNU make is a historic utility and is based very
            heavily on shell scripting, so it does 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
            there is always a 'short' pathname without spaces for any path that 
            contains spaces.
            Unfortunately, this short pathname can be somewhat dynamic and the
            formula is difficult to explain.
            You can use <tt>cygpath</tt> utility to map pathnames with spaces
            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>.
D
duke 已提交
927
            <p>
928 929
                The makefiles will try to translate any pathnames supplied
                to it into the <tt>C:/</tt> style automatically.
930
            <p>
931 932 933 934 935 936 937 938 939
                Note that 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 ":").
                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.
D
duke 已提交
940
        </blockquote>
941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959
        <!-- ------------------------------------------------------ -->
        <h4><a name="windows_checklist">Basic Windows Check List</a></h4>
        <blockquote>
            <ol>
                <li>
                    Install the
                    <a href="#cygwin">CYGWIN product</a>. 
                </li>
                <li>
                    Install the 
                    <a href="#bootjdk">Bootstrap JDK</a>, set
                    <tt><a href="#ALT_BOOTDIR">ALT_BOOTDIR</a></tt>.
                </li>
                <li>
                    <a href="#importjdk">Optional Import JDK</a>, set
                    <tt><a href="#ALT_JDK_IMPORT_PATH">ALT_JDK_IMPORT_PATH</a></tt>.
                </li>
                <li>
                    Install the
960
                    <a href="#msvc32">Microsoft Visual Studio Compilers</a>).
961 962 963
                </li>
                <li>
                    Setup all environment variables for compilers 
964
                    (see <a href="#msvc32">compilers</a>).
965 966 967 968 969
                </li>
                <li>
                    Install 
                    <a href="#dxsdk">Microsoft DirectX SDK</a>.
                </li>
970 971
                <li>
                    Install
972
                    <a href="#ant">Ant 1.7.1 or newer</a>,
973
                    make sure it is in your PATH and set
974 975
                    <tt><a href="#ANT_HOME">ANT_HOME</a></tt>.
                </li>
976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992
            </ol>
        </blockquote>
        <!-- ------------------------------------------------------ -->
        <hr>
        <h3><a name="dependencies">Build Dependencies</a></h3>
        <blockquote>
            Depending on the platform, the OpenJDK build process has some basic
            dependencies on components not part of the OpenJDK sources.
            Some of these are specific to a platform, some even specific to
            an architecture.
            Each dependency will have a set of ALT variables that can be set
            to tell the makefiles where to locate the component.
            In most cases setting these ALT variables may not be necessary
            and the makefiles will find defaults on the system in standard
            install locations or through component specific variables.
            <!-- ------------------------------------------------------ -->
            <h4><a name="bootjdk">Bootstrap JDK</a></h4>
D
duke 已提交
993
            <blockquote>
994 995 996
                All OpenJDK builds require access to the previously released 
                JDK 6, this is often called a bootstrap JDK.
                The JDK 6 binaries can be downloaded from Sun's 
997
                <a href="http://java.sun.com/javase/downloads/index.jsp"
998
                   target="_blank">JDK 6 download site</a>.
999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010
                For build performance reasons
                is very important that this bootstrap JDK be made available on the
                local disk of the machine doing the build.
                You should always set 
                <tt><a href="#ALT_BOOTDIR">ALT_BOOTDIR</a></tt>
                to point to the location of
                the bootstrap JDK installation, this is the directory pathname
                that contains a <tt>bin, lib, and include</tt>
                It's also a good idea to also place its <tt>bin</tt> directory
                in the <tt>PATH</tt> environment variable, although it's
                not required.
                <p>
1011 1012 1013 1014 1015 1016
                    <strong>Solaris:</strong>
                    Some pre-installed JDK images may be available to you in the
                    directory <tt>/usr/jdk/instances</tt>.
                    If you don't set
                    <tt><a href="#ALT_BOOTDIR">ALT_BOOTDIR</a></tt>
                    the makefiles will look in that location for a JDK it can use.
D
duke 已提交
1017
            </blockquote>
1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028
            <!-- ------------------------------------------------------ -->
            <h4><a name="importjdk">Optional Import JDK</a></h4>
            <blockquote>
                The <tt><a href="#ALT_JDK_IMPORT_PATH">ALT_JDK_IMPORT_PATH</a></tt>
                setting is only needed if you are not building the entire
                JDK. For example, if you have built the entire JDK once, and
                wanted to avoid repeatedly building the Hotspot VM, you could
                set this to the location of the previous JDK install image
                and the build will copy the needed files from this import area.
            </blockquote>
            <!-- ------------------------------------------------------ -->
1029 1030
            <h4><a name="ant">Ant</a></h4>
            <blockquote>
1031
                All OpenJDK builds require access to least Ant 1.7.1.
1032
                The Ant tool is available from the 
1033 1034
                <a href="http://archive.apache.org/dist/ant/binaries/apache-ant-1.7.1-bin.zip" target="_blank">
                    Ant 1.7.1 archive download site</a>.
1035 1036
                You should always make sure <tt>ant</tt> is in your PATH, and
                on Windows you may also need to set 
1037 1038 1039 1040
                <tt><a href="#ANT_HOME">ANT_HOME</a></tt>
                to point to the location of
                the Ant installation, this is the directory pathname
                that contains a <tt>bin and lib</tt>.
1041 1042 1043 1044 1045 1046
                <br>
                <b>WARNING:</b> Ant versions used from IDE tools like NetBeans
                or installed via system packages may not operate the same
                as the one obtained from the Ant download bundles.
                These system and IDE installers sometimes choose to change
                the ant installation enough to cause differences.
1047 1048
            </blockquote>
            <!-- ------------------------------------------------------ -->
1049 1050 1051
            <h4><a name="cacerts">Certificate Authority File (cacert)</a></h4>
            <blockquote>
                See <a href="http://en.wikipedia.org/wiki/Certificate_Authority" target="_blank">
1052
                    http://en.wikipedia.org/wiki/Certificate_Authority</a>
1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074
                for a better understanding of the Certificate Authority (CA).
                A certificates file named "cacerts"
                represents a system-wide keystore with CA certificates. 
                In JDK and JRE
                binary bundles, the "cacerts" file contains root CA certificates from
                several public CAs (e.g., VeriSign, Thawte, and Baltimore).
                The source contain a cacerts file
                without CA root certificates. 
                Formal JDK builders will need to secure
                permission from each public CA and include the certificates into their
                own custom cacerts file. 
                Failure to provide a populated cacerts file
                will result in verification errors of a certificate chain during runtime.
                The variable 
                <tt><a href="#ALT_CACERTS_FILE">ALT_CACERTS_FILE</a></tt>
                can be used to override the default location of the
                cacerts file that will get placed in your build.
                By default an empty cacerts file is provided and that should be
                fine for most JDK developers.
            </blockquote>
            <!-- ------------------------------------------------------ -->
            <h4><a name="compilers">Compilers</a></h4>
D
duke 已提交
1075
            <blockquote>
1076 1077
                <strong><a name="gcc">Linux gcc/binutils</a></strong>
                <blockquote>
1078
                    The GNU gcc compiler version should be 4.3 or newer.
1079 1080 1081 1082 1083 1084
                    The compiler used should be the default compiler installed
                    in <tt>/usr/bin</tt>.
                </blockquote>
                <strong><a name="studio">Solaris: Sun Studio</a></strong>
                <blockquote>
                    At a minimum, the
1085
                    <a href="http://www.oracle.com/technetwork/server-storage/solarisstudio/downloads/index.htm" target="_blank">
1086
                        Sun Studio 12 Update 1 Compilers</a>
1087 1088
                    (containing version 5.10 of the C and C++ compilers) is required,
		    including specific patches.
1089
                    <p>
1090
		    The Solaris SPARC patch list is:
1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121
                    <ul>
                        <li>
                            118683-05: SunOS 5.10: Patch for profiling libraries and assembler
                        </li>
                        <li>
                            119963-21: SunOS 5.10: Shared library patch for C++
                        </li>
                        <li>
                            120753-08: SunOS 5.10: Microtasking libraries (libmtsk) patch
                        </li>
                        <li>
                            128228-09: Sun Studio 12 Update 1: Patch for Sun C++ Compiler
                        </li>
                        <li>
                            141860-03: Sun Studio 12 Update 1: Patch for Compiler Common patch for Sun C C++ F77 F95
                        </li>
                        <li>
                            141861-05: Sun Studio 12 Update 1: Patch for Sun C Compiler
                        </li>
                        <li>
                            142371-01: Sun Studio 12.1 Update 1: Patch for dbx
                        </li>
                        <li>
                            143384-02: Sun Studio 12 Update 1: Patch for debuginfo handling
                        </li>
                        <li>
                            143385-02: Sun Studio 12 Update 1: Patch for Compiler Common patch for Sun C C++ F77 F95
                        </li>
                        <li>
                            142369-01: Sun Studio 12.1: Patch for Performance Analyzer Tools
                        </li>
1122 1123
                    </ul>
                    <p>
1124
                        The Solaris X86 patch list is:
1125
                    <ul>
1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146
                        <li>
                            119961-07: SunOS 5.10_x86, x64, Patch for profiling libraries and assembler
                        </li>
                        <li>
                            119964-21: SunOS 5.10_x86: Shared library patch for C++_x86
                        </li>
                        <li>
                            120754-08: SunOS 5.10_x86: Microtasking libraries (libmtsk) patch
                        </li>
                        <li>
                            141858-06: Sun Studio 12 Update 1_x86: Sun Compiler Common patch for x86 backend
                        </li>
                        <li>
                            128229-09: Sun Studio 12 Update 1_x86: Patch for C++ Compiler
                        </li>
                        <li>
                            142363-05: Sun Studio 12 Update 1_x86: Patch for C Compiler
                        </li>
                        <li>
                            142368-01: Sun Studio 12.1_x86: Patch for Performance Analyzer Tools
                        </li>
1147
                    </ul>
1148
                    <p> 
1149 1150 1151 1152
                        Set
                        <a href="#ALT_COMPILER_PATH"><tt>ALT_COMPILER_PATH</tt></a>
                        to point to the location of
                        the compiler binaries, and place this location in the <tt>PATH</tt>.
1153
                    <p>
1154 1155 1156 1157 1158
                        The Oracle Solaris Studio Express compilers at:
                        <a href="http://developers.sun.com/sunstudio/downloads/express.jsp" target="_blank">
                            Oracle Solaris Studio Express Download site</a>
                        are also an option, although these compilers have not
                        been extensively used yet.
1159
                </blockquote>
1160
                <strong><a name="msvc32">Windows i586: Microsoft Visual Studio 2010 Compilers</a></strong>
1161
                <blockquote>
1162
                    <p>
1163 1164 1165
                        <b>BEGIN WARNING</b>: JDK 7 has transitioned to
                        use the newest VS2010 Microsoft compilers.
                        No other compilers are known to build the entire JDK,
1166 1167 1168
                        including non-open portions.
                        Visual Studio 2010 Express compilers are now able to build all the
                        open source repositories, but this is 32 bit only. To build 64 bit
1169 1170
                        Windows binaries use the the 7.1 Windows SDK.
                        <b>END WARNING.</b>
1171
                    <p>
1172
                        The 32-bit OpenJDK Windows build requires
1173 1174 1175 1176 1177 1178
                        Microsoft Visual Studio C++ 2010 (VS2010) Professional
                        Edition or Express compiler.
                        The compiler and other tools are expected to reside
                        in the location defined by the variable
                        <tt>VS100COMNTOOLS</tt> which
                        is set by the Microsoft Visual Studio installer.
1179
                    <p> 
1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190
                        Once the compiler is installed,
                        it is recommended that you run <tt>VCVARS32.BAT</tt>
                        to set the compiler environment variables
                        <tt>INCLUDE</tt>,
                        <tt>LIB</tt>, and
                        <tt>PATH</tt>
                        prior to building the
                        OpenJDK.
                        The above environment variables <b>MUST</b> be set.
                        This compiler also contains the Windows SDK v 7.0a,
                        which is an update to the Windows 7 SDK.
1191
                    <p>
1192 1193 1194 1195
                        <b>WARNING:</b> Make sure you check out the
                        <a href="#cygwin">CYGWIN link.exe WARNING</a>.
                        The path <tt>/usr/bin</tt> must be after the path to the
                        Visual Studio product.
1196
                </blockquote>
1197
                <strong><a name="msvc64">Windows x64: Microsoft Visual Studio 2010 Professional Compiler</a></strong>
1198
                <blockquote>
1199
                    For <b>X64</b>, the set up is much the same as 32 bit
1200 1201
                    except that you run <tt>amd64\VCVARS64.BAT</tt>
                    to set the compiler environment variables.
1202
                    Previously 64 bit builds had to use the 64 bit compiler in
1203 1204
                    an unbundled Windows SDK but this is no longer necessary if
                    you have VS2010 Professional.
1205
                </blockquote>
1206
                <strong><a name="mssdk64">Windows x64: Microsoft Windows 7.1 SDK 64 bit compilers.</a></strong>
1207 1208 1209
                For a free alternative for 64 bit builds, use the 7.1 SDK.
                Microsoft say that to set up your paths for this run
                <pre>
1210
    c:\Program Files\Microsoft SDKs\Windows\v7.1\bin\setenv.cmd /x64.
1211 1212 1213 1214 1215 1216
                </pre>
                What was tested is just directly setting up LIB, INCLUDE,
                PATH and based on the installation directories using the
                DOS short name appropriate for the system, (you will
                need to set them for yours, not just blindly copy this) eg :
                <pre>
1217 1218 1219 1220 1221
    set VSINSTALLDIR=c:\PROGRA~2\MICROS~1.0
    set WindowsSdkDir=c:\PROGRA~1\MICROS~1\Windows\v7.1
    set PATH=%VSINSTALLDIR%\vc\bin\amd64;%VSINSTALLDIR%\Common7\IDE;%WindowsSdkDir%\bin;%PATH%
    set INCLUDE=%VSINSTALLDIR%\vc\include;%WindowsSdkDir%\include
    set LIB=%VSINSTALLDIR%\vc\lib\amd64;%WindowsSdkDir%\lib\x64
1222
                </pre>
1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246
            </blockquote>
            <!-- ------------------------------------------------------ --> 
            <h4><a name="zip">Zip and Unzip</a></h4>
            <blockquote>
                Version 2.2 (November 3rd 1997) or newer of the zip utility 
                and version 5.12 or newer of the unzip utility is needed 
                to build the JDK.
                With Solaris, Linux, and Windows CYGWIN, the zip and unzip
                utilities installed on the system should be fine.
                Information and the source code for
                ZIP.EXE and UNZIP.EXE is available on the
                <a href="http://www.info-zip.org" 
                   target="_blank">info-zip web site</a>.
            </blockquote>
            <!-- ------------------------------------------------------ -->
            <h4><a name="cups">Common UNIX Printing System (CUPS) Headers (Solaris &amp; Linux)</a></h4>
            <blockquote>
                <strong>Solaris:</strong>
                CUPS header files are required for building the 
                OpenJDK on Solaris.
                The Solaris header files can be obtained by installing 
                the package <strong>SFWcups</strong> from the Solaris Software
                Companion CD/DVD, these often will be installed into 
                <tt>/opt/sfw/cups</tt>.
D
duke 已提交
1247
                <p>
1248 1249 1250 1251 1252 1253 1254
                    <strong>Linux:</strong>
                    CUPS header files are required for building the
                    OpenJDK on Linux.
                    The Linux header files are usually available from a "cups"
                    development package, it's recommended that you try and use
                    the package provided by the particular version of Linux that
                    you are using.
D
duke 已提交
1255
                <p>
1256 1257 1258 1259 1260 1261
                    The CUPS header files can always be downloaded from
                    <a href="http://www.cups.org" target="_blank">www.cups.org</a>.
                    The variable
                    <tt><a href="#ALT_CUPS_HEADERS_PATH">ALT_CUPS_HEADERS_PATH</a></tt>
                    can be used to override the default location of the
                    CUPS Header files.
1262 1263
            </blockquote>
            <!-- ------------------------------------------------------ -->
1264 1265 1266
            <h4><a name="xrender">XRender Extension Headers (Solaris &amp; Linux)</a></h4>
            <blockquote>
                <p>
1267 1268 1269 1270 1271 1272 1273
                    <strong>Solaris:</strong>
                    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>
1274
                </p><p>
1275 1276 1277 1278 1279 1280 1281 1282
                    <strong>Linux:</strong>
                    XRender header files are required for building the
                    OpenJDK on Linux.
                    The Linux header files are usually available from a "Xrender"
                    development package, it's recommended that you try and use
                    the package provided by the particular distribution of Linux that
                    you are using.
                </p>
1283 1284
            </blockquote>
            <!-- ------------------------------------------------------ -->
1285 1286 1287 1288 1289 1290 1291
            <h4><a name="freetype">FreeType 2</a></h4>
            <blockquote>
                Version 2.3 or newer of FreeType is required for building the OpenJDK.
                On Unix systems required files can be available as part of your
                distribution (while you still may need to upgrade them).
                Note that you need development version of package that 
                includes both FreeType library and header files.
D
duke 已提交
1292
                <p>
1293 1294
                    You can always download latest FreeType version from the
                    <a href="http://www.freetype.org" target="_blank">FreeType website</a>.
D
duke 已提交
1295
                <p>
1296 1297 1298 1299 1300 1301 1302
                    Makefiles will try to pick FreeType from /usr/lib and /usr/include.
                    In case it is installed elsewhere you will need to set environment
                    variables
                    <tt><a href="#ALT_FREETYPE_LIB_PATH">ALT_FREETYPE_LIB_PATH</a></tt>
                    and
                    <tt><a href="#ALT_FREETYPE_HEADERS_PATH">ALT_FREETYPE_HEADERS_PATH</a></tt>
                    to refer to place where library and header files are installed.
1303
                <p>
1304 1305 1306 1307
                    Building the freetype 2 libraries from scratch is also possible,
                    however on Windows refer to the
                    <a href="http://freetype.freedesktop.org/wiki/FreeType_DLL">
                        Windows FreeType DLL build instructions</a>.
1308
                <p>
1309 1310 1311 1312 1313 1314 1315 1316 1317
                    Note that by default FreeType is built with byte code hinting
                    support disabled due to licensing restrictions.
                    In this case, text appearance and metrics are expected to
                    differ from Sun's official JDK build.
                    See
                    <a href="http://freetype.sourceforge.net/freetype2/index.html">
                        the SourceForge FreeType2 Home Page
                    </a>
                    for more information.
1318 1319 1320
            </blockquote>    
            <!-- ------------------------------------------------------ -->
            <h4><a name="alsa">Advanced Linux Sound Architecture (ALSA) (Linux only)</a></h4>
D
duke 已提交
1321
            <blockquote>
1322 1323 1324 1325 1326 1327 1328 1329 1330 1331
                <strong>Linux only:</strong>
                Version 0.9.1 or newer of the ALSA files are
                required for building the OpenJDK on Linux.
                These Linux files are usually available from an "alsa"
                of "libasound"
                development package, it's highly recommended that you try and use
                the package provided by the particular version of Linux that
                you are using.
                The makefiles will check this emit a sanity error if it is
                missing or the wrong version.
D
duke 已提交
1332
                <p>
1333 1334 1335 1336 1337 1338
                    In particular, older Linux systems will likely not have the
                    right version of ALSA installed, for example
                    Redhat AS 2.1 U2 and SuSE 8.1 do not include a sufficiently
                    recent ALSA distribution.
                    On rpm-based systems, you can see if ALSA is installed by
                    running this command:
1339 1340 1341 1342 1343
                <pre>
                    <tt>rpm -qa | grep alsa</tt>
                </pre>
                Both <tt>alsa</tt> and <tt>alsa-devel</tt> packages are needed.
                <p> 
1344 1345 1346 1347 1348 1349 1350 1351
                    If your distribution does not come with ALSA, and you can't
                    find ALSA packages built for your particular system,
                    you can try to install the pre-built ALSA rpm packages from
                    <a href="http://www.freshrpms.net/" target="_blank">
                        <tt>www.freshrpms.net</tt></a>.
                    Note that installing a newer ALSA could
                    break sound output if an older version of ALSA was previously
                    installed on the system, but it will enable JDK compilation.
D
duke 已提交
1352
                <blockquote>
1353 1354 1355 1356 1357 1358 1359 1360 1361 1362
                    Installation: execute as root<br>
                    [i586]: <code>rpm -Uv --force alsa-lib-devel-0.9.1-rh61.i386.rpm</code><br>
                    [x64]: <code>rpm -Uv --force alsa-lib-devel-0.9.8-amd64.x86_64.rpm</code><br>
                    Uninstallation:<br>
                    [i586]: <code>rpm -ev alsa-lib-devel-0.9.1-rh61</code><br>
                    [x64]:<code>rpm -ev alsa-lib-devel-0.9.8-amd64</code><br>
                    Make sure that you do not link to the static library
                    (<tt>libasound.a</tt>),
                    by verifying that the dynamic library (<tt>libasound.so</tt>) is
                    correctly installed in <tt>/usr/lib</tt>.
D
duke 已提交
1363
                </blockquote>
1364 1365
                As a last resort you can go to the
                <a href="http://www.alsa-project.org" target="_blank">
1366
                    Advanced Linux Sound Architecture Site</a> and build it from
1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392
                source.
                <blockquote>
                    Download driver and library
                    source tarballs from 
                    <a href="http://www.alsa-project.org" target="_blank">ALSA's homepage</a>. 
                    As root, execute the following
                    commands (you may need to adapt the version number):
                    <pre>
                        <tt>
                            $ tar xjf alsa-driver-0.9.1.tar.bz2
                            $ cd alsa-driver-0.9.1
                            $ ./configure
                            $ make install
                            $ cd ..
                            $ tar xjf alsa-lib-0.9.1.tar.bz2
                            $ cd alsa-lib-0.9.1
                            $ ./configure
                            $ make install
                        </tt>
                    </pre>
                    Should one of the above steps fail, refer to the documentation on
                    ALSA's home page.
                </blockquote>
                Note that this is a minimum install that enables
                building the JDK platform. To actually use ALSA sound drivers, more
                steps are necessary as outlined in the documentation on ALSA's homepage.
D
duke 已提交
1393
                <p>
1394 1395 1396
                    ALSA can be uninstalled by executing <tt>make uninstall</tt> first in
                    the <tt>alsa-lib-0.9.1</tt> directory and then in
                    <tt>alsa-driver-0.9.1</tt>.
D
duke 已提交
1397
            </blockquote>
1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410
            There are no ALT* variables to change the assumed locations of ALSA,
            the makefiles will expect to find the ALSA include files and library at:
            <tt>/usr/include/alsa</tt> and <tt>/usr/lib/libasound.so</tt>.
        </blockquote>
        <!-- ------------------------------------------------------ -->
        <h4>Windows Specific Dependencies</h4>
        <blockquote>
            <strong>Unix Command Tools (<a name="cygwin">CYGWIN</a>)</strong>
            <blockquote> 
                The OpenJDK requires access to a set of unix command tools
                on Windows which can be supplied by 
                <a href="http://www.cygwin.com" target="_blank">CYGWIN</a>. 
                <p>
1411 1412 1413 1414
                    The OpenJDK build requires CYGWIN version 1.5.12 or newer.
                    Information about CYGWIN can
                    be obtained from the CYGWIN website at
                    <a href="http://www.cygwin.com" target="_blank">www.cygwin.com</a>.
1415
                <p>
1416 1417 1418 1419
                    By default CYGWIN doesn't install all the tools required for building
                    the OpenJDK.
                    Along with the default installation, you need to install
                    the following tools.
1420 1421 1422 1423 1424
                <blockquote>
                    <table border="1">
                        <thead>
                            <tr>
                                <td>Binary Name</td>
1425
                                <td>Category</td>
1426 1427 1428 1429 1430 1431 1432 1433
                                <td>Package</td>
                                <td>Description</td>
                            </tr>
                        </thead>
                        <tbody>
                            <tr>
                                <td>ar.exe</td>
                                <td>Devel</td>
1434 1435
                                <td>binutils</td>
                                <td>The GNU assembler, linker and binary
1436
                                    utilities</td>
1437 1438 1439 1440
                            </tr>
                            <tr>
                                <td>make.exe</td>
                                <td>Devel</td>
1441 1442
                                <td>make</td>
                                <td>The GNU version of the 'make' utility built for CYGWIN.<br>
1443
                                    <b>NOTE</b>: See <a href="#gmake">the GNU make section</a></td>
1444 1445 1446 1447
                            </tr>
                            <tr>
                                <td>m4.exe</td>
                                <td>Interpreters</td>
1448 1449
                                <td>m4</td>
                                <td>GNU implementation of the traditional Unix macro
1450
                                    processor</td>
1451 1452 1453 1454
                            </tr>
                            <tr>
                                <td>cpio.exe</td>
                                <td>Utils</td>
1455 1456
                                <td>cpio</td>
                                <td>A program to manage archives of files</td>
1457 1458
                            </tr>
                            <tr>
1459
                                <td>gawk.exe</td>
1460
                                <td>Utils</td>
1461 1462
                                <td>awk</td>
                                <td>Pattern-directed scanning and processing language</td>
1463 1464 1465 1466
                            </tr>
                            <tr>
                                <td>file.exe</td>
                                <td>Utils</td>
1467 1468
                                <td>file</td>
                                <td>Determines file type using 'magic' numbers</td>
1469 1470 1471
                            </tr>
                            <tr>
                                <td>zip.exe</td>
1472
                                <td>Archive</td>
1473 1474
                                <td>zip</td>
                                <td>Package and compress (archive) files</td>
1475 1476 1477
                            </tr>
                            <tr>
                                <td>unzip.exe</td>
1478
                                <td>Archive</td>
1479 1480
                                <td>unzip</td>
                                <td>Extract compressed files in a ZIP archive</td>
1481 1482 1483
                            </tr>
                            <tr>
                                <td>free.exe</td>
1484 1485 1486
                                <td>System</td>
                                <td>procps</td>
                                <td>Display amount of free and used memory in the system</td>
1487 1488 1489 1490
                            </tr>
                        </tbody>
                    </table>
                </blockquote>
D
duke 已提交
1491
                <p>
1492 1493 1494 1495 1496 1497 1498 1499
                    Note that the CYGWIN software can conflict with other non-CYGWIN
                    software on your Windows system.
                    CYGWIN provides a
                    <a href="http://cygwin.com/faq/faq.using.html" target="_blank">FAQ</a> for
                    known issues and problems, of particular interest is the
                    section on
                    <a href="http://cygwin.com/faq/faq.using.html#faq.using.bloda" target="_blank">
                        BLODA (applications that interfere with CYGWIN)</a>.
1500
                <p>
1501 1502 1503 1504 1505 1506
                    <b>WARNING:</b>
                    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>.
D
duke 已提交
1507
            </blockquote>
1508
            <strong><a name="dxsdk">Microsoft DirectX 9.0 SDK header files and libraries</a></strong>
D
duke 已提交
1509
            <blockquote>
1510 1511 1512 1513 1514
                Microsoft DirectX 9.0 SDK (Summer 2004)
                headers are required for building
                OpenJDK.
                This SDK can be downloaded from 
                <a href="http://www.microsoft.com/downloads/details.aspx?FamilyId=FD044A42-9912-42A3-9A9E-D857199F888E&amp;displaylang=en" target="_blank">
1515
                    Microsoft DirectX 9.0 SDK (Summer 2004)</a>.
1516 1517 1518 1519 1520 1521 1522
                If the link above becomes obsolete, the SDK can be found from 
                <a href="http://download.microsoft.com" target="_blank">the Microsoft Download Site</a>
                (search with "DirectX 9.0 SDK Update Summer 2004"). 
                The location of this SDK can be set with 
                <tt><a href="#ALT_DXSDK_PATH">ALT_DXSDK_PATH</a></tt>
                but it's normally found via the DirectX environment variable
                <tt>DXSDK_DIR</tt>.
D
duke 已提交
1523
            </blockquote>
1524
            <strong><a name="msvcrNN"><tt>MSVCR100.DLL</tt></a></strong>
1525
            <blockquote> 
1526 1527 1528 1529 1530
                The OpenJDK build requires access to a redistributable
                <tt>MSVCR100.DLL</tt>.
                This is usually picked up automatically from the redist
                directories of Visual Studio 2010.
                If this cannot be found set the 
1531
                <a href="#ALT_MSVCRNN_DLL_PATH"><tt>ALT_MSVCRNN_DLL_PATH</tt></a>
1532
                variable to the location of this file.
1533
                <p> 
D
duke 已提交
1534
            </blockquote>
1535 1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568
        </blockquote>
        <!-- ------------------------------------------------------ -->
        <hr>
        <h2><a name="creating">Creating the Build</a></h2>
        <blockquote>
            Once a machine is setup to build the OpenJDK,
            the steps to create the build are fairly simple.
            The various ALT settings can either be made into  variables
            or can be supplied on the 
            <a href="#gmake"><tt><i>gmake</i></tt></a> 
            command.
            <ol>
                <li>Use the sanity rule to double check all the ALT settings:
                    <blockquote>
                        <tt>
                            <i>gmake</i> 
                            sanity
                            [ARCH_DATA_MODEL=<i>32 or 64</i>]
                            [other "ALT_" overrides]
                        </tt>
                    </blockquote>
                </li>
                <li>Start the build with the command:
                    <blockquote>
                        <tt>
                            <i>gmake</i> 
                            [ARCH_DATA_MODEL=<i>32 or 64</i>]
                            [ALT_OUTPUTDIR=<i>output_directory</i>] 
                            [other "ALT_" overrides] 
                        </tt>
                    </blockquote>
                </li>
            </ol>
            <p>
1569 1570 1571 1572 1573 1574 1575 1576
                <strong>Solaris:</strong>
                Note that ARCH_DATA_MODEL is really only needed on Solaris to
                indicate you want to built the 64-bit version.
                And before the Solaris 64-bit binaries can be used, they
                must be merged with the binaries from a separate 32-bit build.
                The merged binaries may then be used in either 32-bit or 64-bit mode, with
                the selection occurring at runtime
                with the <tt>-d32</tt> or <tt>-d64</tt> options.
1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587
        </blockquote>
        <!-- ------------------------------------------------------ -->
        <hr>
        <h2><a name="testing">Testing the Build</a></h2>
        <blockquote>
            When the build is completed, you should see the generated
            binaries and associated files in the <tt>j2sdk-image</tt> 
            directory in the output directory. 
            The default output directory is
            <tt>build/<i>platform</i></tt>,
            where <tt><i>platform</i></tt> is one of
1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599
            <blockquote>
                <ul>
                    <li><tt>solaris-sparc</tt></li>
                    <li><tt>solaris-sparcv9</tt></li>
                    <li><tt>solaris-i586</tt></li>
                    <li><tt>solaris-amd64</tt></li>
                    <li><tt>linux-i586</tt></li>
                    <li><tt>linux-amd64</tt></li>
                    <li><tt>windows-i586</tt></li>
                    <li><tt>windows-amd64</tt></li>
                </ul>
            </blockquote>
1600 1601 1602 1603 1604
            In particular, the 
            <tt>build/<i>platform</i>/j2sdk-image/bin</tt>
            directory should contain executables for the 
            OpenJDK tools and utilities.
            <p>
1605 1606 1607 1608
                You can test that the build completed properly by using the build
                to run the various demos that you will find in the
                <tt>build/<i>platform</i>/j2sdk-image/demo</tt>
                directory.
1609
            <p>
1610 1611 1612
                The provided regression tests can be run with the <tt>jtreg</tt>
                utility from
                <a href="http://openjdk.java.net/jtreg/" target="_blank">the jtreg site</a>.
1613 1614 1615 1616 1617
        </blockquote>
        <!-- ------------------------------------------------------ -->
        <hr>
        <h2><a name="variables">Environment/Make Variables</a></h2>
        <p>
1618 1619 1620
            Some of the
            environment or make variables (just called <b>variables</b> in this
            document) that can impact the build are:
1621 1622
        <blockquote>
            <dl>
1623 1624 1625 1626 1627
                <dt><a name="path"><tt>PATH</tt></a> </dt>
                <dd>Typically you want to set the <tt>PATH</tt> to include:
                    <ul>
                        <li>The location of the GNU make binary</li>
                        <li>The location of the Bootstrap JDK <tt>java</tt> 
1628
                            (see <a href="#bootjdk">Bootstrap JDK</a>)</li>
1629
                        <li>The location of the C/C++ compilers 
1630
                            (see <a href="#compilers"><tt>compilers</tt></a>)</li>
1631
                        <li>The location or locations for the Unix command utilities
1632
                            (e.g. <tt>/usr/bin</tt>)</li>
1633 1634 1635
                    </ul>
                </dd>
                <dt><tt>MILESTONE</tt> </dt>
1636
                <dd>
1637 1638 1639 1640 1641 1642 1643 1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654
                    The milestone name for the build (<i>e.g.</i>"beta"). 
                    The default value is "internal".
                </dd>
                <dt><tt>BUILD_NUMBER</tt> </dt>
                <dd>
                    The build number for the build (<i>e.g.</i> "b27"). 
                    The default value is "b00".
                </dd>
                <dt><a name="arch_data_model"><tt>ARCH_DATA_MODEL</tt></a></dt>
                <dd>The <tt>ARCH_DATA_MODEL</tt> variable
                    is used to specify whether the build is to generate 32-bit or 64-bit
                    binaries. 
                    The Solaris build supports either 32-bit or 64-bit builds, but
                    Windows and Linux will support only one, depending on the specific
                    OS being used.
                    Normally, setting this variable is only necessary on Solaris.
                    Set <tt>ARCH_DATA_MODEL</tt> to <tt>32</tt> for generating 32-bit binaries, 
                    or to <tt>64</tt> for generating 64-bit binaries.
1655
                </dd>
1656
                <dt><a name="ALT_BOOTDIR"><tt>ALT_BOOTDIR</tt></a></dt>
1657
                <dd>
1658 1659 1660 1661
                    The location of the bootstrap JDK installation. 
                    See <a href="#bootjdk">Bootstrap JDK</a> for more information.
                    You should always install your own local Bootstrap JDK and
                    always set <tt>ALT_BOOTDIR</tt> explicitly.
1662
                </dd>
1663
                <dt><a name="ALT_JDK_IMPORT_PATH"><tt>ALT_JDK_IMPORT_PATH</tt></a></dt>
1664
                <dd>
1665 1666
                    The location of a previously built JDK installation. 
                    See <a href="#importjdk">Optional Import JDK</a> for more information.
1667
                </dd>
1668
                <dt><a name="ALT_OUTPUTDIR"><tt>ALT_OUTPUTDIR</tt></a> </dt>
1669
                <dd>
1670 1671 1672
                    An override for specifying the (absolute) path of where the
                    build output is to go.
                    The default output directory will be build/<i>platform</i>.
1673
                </dd>
1674 1675 1676 1677 1678
                <dt><a name="ALT_COMPILER_PATH"><tt>ALT_COMPILER_PATH</tt></a> </dt>
                <dd>
                    The location of the C/C++ compiler.
                    The default varies depending on the platform. 
                </dd>
1679 1680 1681 1682 1683 1684
                <dt><tt><a name="ALT_CACERTS_FILE">ALT_CACERTS_FILE</a></tt></dt>
                <dd>
                    The location of the <a href="#cacerts">cacerts</a> file.
                    The default will refer to 
                    <tt>jdk/src/share/lib/security/cacerts</tt>.
                </dd>
1685 1686 1687 1688 1689 1690 1691
                <dt><a name="ALT_CUPS_HEADERS_PATH"><tt>ALT_CUPS_HEADERS_PATH</tt></a> </dt>
                <dd>
                    The location of the CUPS header files.
                    See <a href="#cups">CUPS information</a> for more information.
                    If this path does not exist the fallback path is 
                    <tt>/usr/include</tt>.
                </dd>
1692 1693 1694 1695 1696 1697 1698 1699 1700 1701 1702 1703 1704 1705 1706 1707
                <dt><a name="ALT_FREETYPE_LIB_PATH"><tt>ALT_FREETYPE_LIB_PATH</tt></a></dt>
                <dd>
                    The location of the FreeType shared library. 
                    See <a href="#freetype">FreeType information</a> for details. 
                </dd>
                <dt><a name="ALT_FREETYPE_HEADERS_PATH"><tt>ALT_FREETYPE_HEADERS_PATH</tt></a></dt>
                <dd>
                    The location of the FreeType header files.
                    See <a href="#freetype">FreeType information</a> for details. 
                </dd>
                <dt><a name="ALT_JDK_DEVTOOLS_PATH"><tt>ALT_JDK_DEVTOOLS_PATH</tt></a></dt>
                <dd>
                    The default root location of the devtools.
                    The default value is 
                    <tt>$(ALT_SLASH_JAVA)/devtools</tt>.
                </dd>
1708 1709 1710 1711 1712 1713 1714 1715 1716 1717 1718 1719 1720 1721 1722 1723
                <dt><tt><a name="ALT_DEVTOOLS_PATH">ALT_DEVTOOLS_PATH</a></tt> </dt>
                <dd>
                    The location of tools like the 
                    <a href="#zip"><tt>zip</tt> and <tt>unzip</tt></a>
                    binaries, but might also contain the GNU make utility
                    (<tt><i>gmake</i></tt>).
                    So this area is a bit of a grab bag, especially on Windows.
                    The default value depends on the platform and
                    Unix Commands being used.
                    On Linux the default will be 
                    <tt>$(ALT_JDK_DEVTOOLS_PATH)/linux/bin</tt>, 
                    on Solaris
                    <tt>$(ALT_JDK_DEVTOOLS_PATH)/<i>{sparc,i386}</i>/bin</tt>, 
                    and on Windows with CYGWIN
                    <tt>/usr/bin</tt>.
                </dd>
1724 1725 1726 1727 1728 1729 1730
                <dt><tt><a name="ALT_DROPS_DIR">ALT_DROPS_DIR</a></tt> </dt>
                <dd>
                    The location of any source drop bundles
                    (see <a href="#drops">Managing the Source Drops</a>).
                    The default will be
                    <tt>$(ALT_JDK_DEVTOOLS_PATH)/share/jdk7-drops</tt>.
                </dd>
1731
                <dt><a name="ALT_UNIXCCS_PATH"><tt>ALT_UNIXCCS_PATH</tt></a></dt>
1732
                <dd>
1733 1734 1735 1736
                    <strong>Solaris only:</strong>
                    An override for specifying where the Unix CCS
                    command set are located.
                    The default location is <tt>/usr/ccs/bin</tt> 
1737
                </dd>
1738
                <dt><a name="ALT_SLASH_JAVA"><tt>ALT_SLASH_JAVA</tt></a></dt>
1739 1740 1741 1742 1743 1744
                <dd>
                    The default root location for many of the ALT path locations
                    of the following ALT variables.
                    The default value is 
                    <tt>"/java"</tt> on Solaris and Linux, 
                    <tt>"J:"</tt> on Windows.
1745
                </dd>
1746
                <dt><a name="ALT_BUILD_JDK_IMPORT_PATH"><tt>ALT_BUILD_JDK_IMPORT_PATH</tt></a></dt>
1747
                <dd>
1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764
                    These are useful in managing builds on multiple platforms.
                    The default network location for all of the import JDK images
                    for all platforms. 
                    If <tt><a href="#ALT_JDK_IMPORT_PATH">ALT_JDK_IMPORT_PATH</a></tt>
                    is not set, this directory will be used and should contain 
                    the following directories:
                    <tt>solaris-sparc</tt>,
                    <tt>solaris-i586</tt>,
                    <tt>solaris-sparcv9</tt>,
                    <tt>solaris-amd64</tt>,
                    <tt>linux-i586</tt>,
                    <tt>linux-amd64</tt>,
                    <tt>windows-i586</tt>,
                    and
                    <tt>windows-amd64</tt>.
                    Where each of these directories contain the import JDK image
                    for that platform.
1765
                </dd>
1766 1767 1768 1769 1770 1771
                <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 
		    graphical programming environment. The default location is platform specific. 
		    For example, on Linux it defaults to <tt>/usr/X11R6/</tt>.
		</dd>
1772
                <dt><strong>Windows specific:</strong></dt>
1773
                <dd>
1774
                    <dl>
1775
                        <dt><a name="ALT_WINDOWSSDKDIR"><tt>ALT_WINDOWSSDKDIR</tt></a> </dt>
1776 1777
                        <dd>
                            The location of the 
1778 1779 1780 1781
                            Microsoft Windows SDK where some tools will be
			    located.
			    The default is whatever WINDOWSSDKDIR is set to
			    (or WindowsSdkDir) or the path
1782 1783
                            <br>
                            <tt>c:\Program Files\Microsoft SDKs\Windows\v7.0a</tt>
1784 1785 1786 1787 1788 1789 1790 1791 1792
                        </dd>
                        <dt><tt><a name="ALT_DXSDK_PATH">ALT_DXSDK_PATH</a></tt> </dt>
                        <dd>
                            The location of the 
                            <a href="#dxsdk">Microsoft DirectX 9 SDK</a>.
                            The default will be to try and use the DirectX environment
                            variable <tt>DXSDK_DIR</tt>,
                            failing that, look in <tt>C:/DXSDK</tt>.
                        </dd>
1793
                        <dt><tt><a name="ALT_MSVCRNN_DLL_PATH">ALT_MSVCRNN_DLL_PATH</a></tt> </dt>
1794 1795
                        <dd>
                            The location of the 
1796
                            <a href="#msvcrNN"><tt>MSVCR100.DLL</tt></a>. 
1797 1798
                        </dd>
                    </dl>
1799
                </dd>
1800 1801 1802 1803 1804 1805 1806 1807 1808 1809 1810 1811 1812 1813 1814 1815 1816 1817 1818 1819 1820 1821 1822 1823 1824 1825 1826 1827 1828 1829 1830 1831 1832 1833 1834 1835 1836 1837 1838 1839 1840 1841 1842 1843 1844 1845 1846 1847 1848 1849 1850 1851 1852 1853 1854 1855 1856 1857 1858 1859 1860 1861 1862 1863 1864 1865 1866 1867 1868 1869 1870 1871 1872 1873 1874
                <dt><strong>Cross-Compilation Support:</strong></dt>
                <dd>
                    <dl>
                        <dt><a name="CROSS_COMPILE_ARCH"><tt>CROSS_COMPILE_ARCH</tt></a> </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 
			    also be set to point to the graphical header files (e.g. X11) provided with 
			    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.
                           These are added to the <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> variables. 
			</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>)
                            just built (which can't execute on the build host).
                        </dd>
                        <dt><tt><a name="HOST_CC">HOST_CC</a></tt> </dt>
                        <dd>
                            The location of the C compiler to generate programs to run on the build host.
                            Some parts of the build generate programs that are then compiled and executed
                            to produce other parts of the build. Normally the primary C compiler is used
                            to do this, but when cross-compiling that would be the cross-compiler and the
                            resulting program could not be executed. 
                            On Linux this defaults to <tt>/usr/bin/gcc</tt>; on other platforms it must be
                            set explicitly.
                        </dd>
                    </dl>
                <dt><strong>Specialized Build Options:</strong></dt>
                <dd>
                  Some build variables exist to support specialized build environments and/or specialized
                  build products. Their use is only supported in those contexts:
                    <dl>
                        <dt><tt><a name="BUILD_CLIENT_ONLY">BUILD_CLIENT_ONLY</a></tt> </dt>
                        <dd>
                            Indicates this build will only contain the Hotspot client VM. In addition to
                            controlling the Hotspot build target, it ensures that we don't try to copy
                            any server VM files/directories, and defines a default <tt>jvm.cfg</tt> file
                            suitable for a client-only environment. Using this in a 64-bit build will
                            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.
                        </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. 
			    This will enable the directives included in the SE-Embedded specific build 
			    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,
	                    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
			  compression, to use compression.
                        </dd>
                    </dl>
                </dd>
1875 1876 1877 1878
            </dl>
        </blockquote>
        <!-- ------------------------------------------------------ -->
        <hr>
1879 1880 1881 1882 1883 1884 1885 1886 1887 1888 1889 1890 1891 1892 1893 1894 1895 1896 1897 1898 1899 1900 1901 1902 1903 1904 1905 1906 1907 1908 1909 1910 1911 1912 1913 1914 1915 1916 1917 1918 1919 1920 1921 1922 1923 1924 1925 1926 1927 1928 1929 1930 1931 1932 1933 1934 1935 1936 1937 1938 1939 1940 1941 1942 1943 1944 1945 1946 1947 1948 1949 1950 1951 1952 1953
        <h2><a name="hints">Hints and Tips</a></h2>
        <blockquote>
            You don't have to use all these hints and tips, and in fact people do actually
            build with systems that contradict these, but they might prove to be
            helpful to some.
            <ul>
                <li>
                    If <tt>make sanity</tt> does not work, find out why, fix that
                    before going any further. Or at least understand what the
                    complaints are from it.
                </li>
                <li>
                    JDK: Keep in mind that you are building a JDK, but you need
                    a JDK (BOOTDIR JDK) to build this JDK.
                </li>
                <li>
                    Ant: The ant utility is a java application and besides having
                    ant available to you, it's important that ant finds the right
                    java to run with. Make sure you can type <tt>ant -version</tt>
                    and get clean results with no error messages.
                </li>
                <li>
                    Linux: Try and favor the system packages over building your own
                    or getting packages from other areas.
                    Most Linux builds should be possible with the system's
                    available packages.
                </li>
                <li>
                    Solaris: Typically you will need to get compilers on your systems
                    and occasionally GNU make 3.81 if a gmake binary is not available.
                    The gmake binary might not be 3.81, be careful.
                </li>
                <li>
                    Windows VS2010:
                    <ul>
                        <li>
                            Only the C++ part of VS2010 is needed.
                            Try to let the installation go to the default install directory.
                            Always reboot your system after installing VS2010.
                            The system environment variable VS100COMNTOOLS should be
                            set in your environment.
                        </li>
                        <li>
                            Make sure that TMP and TEMP are also set in the environment
                            and refer to Windows paths that exist, like <tt>C:\temp</tt>,
                            not <tt>/tmp</tt>, not <tt>/cygdrive/c/temp</tt>, and not <tt>C:/temp</tt>.
                            <tt>C:\temp</tt> is just an example, it is assumed that this area is
                            private to the user, so by default after installs you should
                            see a unique user path in these variables.
                        </li>
                        <li>
                            You need to use vsvars32.bat or vsvars64.bat to get the
                            PATH, INCLUDE, LIB, LIBPATH, and WINDOWSSDKDIR
                            variables set in your shell environment.
                            These bat files are not easy to use from a shell environment.
                            However, there is a script placed in the root jdk7 repository called
                            vsvars.sh that can help, it should only be done once in a shell
                            that will be doing the build, e.g.<br>
                            <tt>sh ./make/scripts/vsvars.sh -v10 > settings<br>
                                eval `cat settings`</tt><br>
                            Or just <tt>eval `sh ./make/scripts/vsvars.sh -v10`</tt>.
                        </li>
                    </ul>
                </li>
                <li>
                    Windows: PATH order is critical, see the
                    <a href="#paths">paths</a> section for more information.
                </li>
                <li>
                    Windows 64bit builds: Use ARCH_DATA_MODEL=64.
                </li>
            </ul>
        </blockquote>
        <!-- ------------------------------------------------------ -->
        <hr>
1954 1955 1956 1957 1958 1959 1960 1961 1962 1963 1964 1965
        <h2><a name="troubleshooting">Troubleshooting</a></h2>
        <blockquote>
            A build can fail for any number of reasons. 
            Most failures
            are a result of trying to build in an environment in which all the
            pre-build requirements have not been met. 
            The first step in
            troubleshooting a build failure is to recheck that you have satisfied
            all the pre-build requirements for your platform.
            Look for the check list of the platform you are building on in the
            <a href="#contents">Table of Contents</a>.
            <p>
1966 1967 1968 1969 1970 1971 1972 1973
                You can validate your build environment by using the <tt>sanity</tt>
                target.
                Any errors listed
                will stop the build from starting, and any warnings may result in
                a flawed product build.
                We strongly encourage you to evaluate every
                sanity check warning and fix it if required, before you proceed
                further with your build.
1974
            <p>
1975 1976
                Some of the more common problems with builds are briefly described
                below, with suggestions for remedies.
1977
            <ul>
1978 1979 1980 1981 1982 1983 1984 1985 1986 1987 1988 1989 1990
                <li>
                    <b>Corrupted Bundles on Windows:</b>
                    <blockquote>
                        Some virus scanning software has been known to corrupt the
                        downloading of zip bundles.
                        It may be necessary to disable the 'on access' or 'real time'
                        virus scanning features to prevent this corruption.
                        This type of "real time" virus scanning can also slow down the
                        build process significantly.
                        Temporarily disabling the feature, or excluding the build
                        output directory may be necessary to get correct and faster builds.
                    </blockquote>
                </li>
1991 1992 1993 1994 1995 1996 1997 1998 1999
                <li>
                    <b>Slow Builds:</b>
                    <blockquote>
                        If your build machine seems to be overloaded from too many
                        simultaneous C++ compiles, try setting the <tt>HOTSPOT_BUILD_JOBS</tt>
                        variable to <tt>1</tt> (if you're using a multiple CPU
                        machine, setting it to more than the the number of CPUs is probably
                        not a good idea).
                        <p>
2000 2001
                            Creating the javadocs can be very slow, if you are running
                            javadoc, consider skipping that step.
2002
                        <p>
2003 2004 2005
                            Faster hardware and more RAM always helps too.
                            The VM build tends to be CPU intensive (many C++ compiles),
                            and the rest of the JDK will often be disk intensive.
2006
                        <p>
2007 2008
                            Faster compiles are possible using a tool called
                            <a href="http://ccache.samba.org/" target="_blank">ccache</a>.
2009 2010 2011 2012 2013 2014 2015 2016
                    </blockquote>
                </li>
                <li>
                    <b>File time issues:</b>
                    <blockquote>
                        If you see warnings that refer to file time stamps, e.g.
                        <blockquote>
                            <i>Warning message:</i><tt> File `xxx' has modification time in
2017
                                the future.</tt>
2018 2019
                            <br>
                            <i>Warning message:</i> <tt> Clock skew detected. Your build may
2020
                                be incomplete.</tt>
2021 2022 2023 2024 2025 2026 2027 2028 2029 2030 2031
                        </blockquote>
                        These warnings can occur when the clock on the build machine is out of
                        sync with the timestamps on the source files. Other errors, apparently
                        unrelated but in fact caused by the clock skew, can occur along with
                        the clock skew warnings. These secondary errors may tend to obscure the
                        fact that the true root cause of the problem is an out-of-sync clock.
                        For example, an out-of-sync clock has been known to cause an old
                        version of javac to be used to compile some files, resulting in errors
                        when the pre-1.4 compiler ran across the new <tt>assert</tt> keyword
                        in the 1.4 source code.
                        <p>
2032 2033 2034
                            If you see these warnings, reset the clock on the build
                            machine, run "<tt><i>gmake</i> clobber</tt>" or delete the directory
                            containing the build output, and restart the build from the beginning.
2035 2036 2037 2038 2039 2040 2041 2042 2043 2044 2045 2046 2047 2048
                    </blockquote>
                </li>
                <li>
                    <b>Error message: <tt>Trouble writing out table to disk</tt></b>
                    <blockquote>
                        Increase the amount of swap space on your build machine.
                    </blockquote>
                </li>
                <li>
                    <b>Error Message: <tt>libstdc++ not found:</tt></b>
                    <blockquote>
                        This is caused by a missing libstdc++.a library.
                        This is installed as part of a specific package
                        (e.g. libstdc++.so.devel.386).
2049 2050
                        By default some 64-bit Linux versions (e.g. Fedora)
                        only install the 64-bit version of the libstdc++ package.
2051 2052 2053 2054 2055 2056 2057 2058 2059 2060
                        Various parts of the JDK build require a static
                        link of the C++ runtime libraries to allow for maximum
                        portability of the built images.
                    </blockquote>
                </li>
                <li>
                    <b>Error Message: <tt>cannot restore segment prot after reloc</tt></b>
                    <blockquote>
                        This is probably an issue with SELinux (See
                        <a href="http://en.wikipedia.org/wiki/SELinux" target="_blank">
2061
                            http://en.wikipedia.org/wiki/SELinux</a>).
2062 2063 2064
                        Parts of the VM is built without the <tt>-fPIC</tt> for
                        performance reasons.
                        <p>
2065 2066 2067 2068 2069 2070 2071
                            To completely disable SELinux:
                        <ol>
                            <li><tt>$ su root</tt></li>
                            <li><tt># system-config-securitylevel</tt></li>
                            <li><tt>In the window that appears, select the SELinux tab</tt></li>
                            <li><tt>Disable SELinux</tt></li>
                        </ol>
2072
                        <p>
2073 2074 2075 2076 2077
                            Alternatively, instead of completely disabling it you could
                            disable just this one check.
                        <ol>
                            <li>Select System->Administration->SELinux Management</li>
                            <li>In the SELinux Management Tool which appears,
2078
                                select "Boolean" from the menu on the left</li>
2079 2080
                            <li>Expand the "Memory Protection" group</li>
                            <li>Check the first item, labeled
2081
                                "Allow all unconfined executables to use libraries requiring text relocation ..."</li>
2082
                        </ol>
2083 2084 2085
                    </blockquote>
                </li>
                <li>
2086 2087 2088 2089 2090
                    <b>Windows Error Messages:</b><br>
                    <tt>*** fatal error - couldn't allocate heap, ... </tt><br>
                    <tt>rm fails with "Directory not empty"</tt><br>
                    <tt>unzip fails with "cannot create ... Permission denied"</tt><br>
                    <tt>unzip fails with "cannot create ... Error 50"</tt><br>
2091 2092 2093 2094
                    <blockquote>
                        The CYGWIN software can conflict with other non-CYGWIN
                        software. See the CYGWIN FAQ section on
                        <a href="http://cygwin.com/faq/faq.using.html#faq.using.bloda" target="_blank">
2095
                            BLODA (applications that interfere with CYGWIN)</a>.
2096 2097 2098
                    </blockquote>
                </li>
                <li>
2099
                    <b>Windows Error Message: <tt>spawn failed</tt></b>
2100
                    <blockquote>
2101 2102 2103
                        Try rebooting the system, or there could be some kind of
                        issue with the disk or disk partition being used.
                        Sometimes it comes with a "Permission Denied" message.
2104 2105 2106 2107 2108 2109 2110
                    </blockquote>
                </li>
            </ul>
        </blockquote>
        <hr>
    </body>
</html>