Wed, 22 Dec 2010 12:25:52 -0800

Wed, 22 Dec 2010 12:25:52 -0800
changeset 276
parent 262
child 277

7003845: README-builds document proper location of forest extension, provide alternatives
Reviewed-by: robilad

duke@2 1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
duke@2 2 <html>
ohair@13 3 <head>
ohair@13 4 <title>OpenJDK Build README</title>
ohair@13 5 </head>
ohair@13 6 <body style="background-color:lightcyan">
ohair@13 7 <!-- ====================================================== -->
ohair@41 8 <table width="100%">
ohair@13 9 <tr>
ohair@13 10 <td align="center">
ohair@25 11 <img alt="OpenJDK"
ohair@25 12 src=""
ohair@25 13 width=256 />
ohair@13 14 </td>
ohair@13 15 </tr>
ohair@13 16 <tr>
ohair@13 17 <td align=center>
ohair@13 18 <h1>OpenJDK Build README</h1>
ohair@13 19 </td>
ohair@13 20 </tr>
ohair@13 21 </table>
ohair@13 22 <!-- ------------------------------------------------------ -->
ohair@13 23 <hr>
ohair@13 24 <h2><a name="introduction">Introduction</a></h2>
ohair@13 25 <blockquote>
ohair@13 26 <p>
ohair@276 27 This README file contains build instructions for the
ohair@276 28 <a href="" target="_blank">OpenJDK</a>.
ohair@276 29 Building the source code for the
ohair@276 30 OpenJDK
ohair@276 31 requires
ohair@276 32 a certain degree of technical expertise.
ohair@13 33 </blockquote>
ohair@13 34 <!-- ------------------------------------------------------ -->
ohair@13 35 <hr>
ohair@13 36 <h2><a name="contents">Contents</a></h2>
ohair@13 37 <blockquote>
ohair@13 38 <ul>
ohair@13 39 <li><a href="#introduction">Introduction</a></li>
ohair@276 40 <li><a href="#hg">Use of Mercurial</a>
ohair@276 41 <ul>
ohair@276 42 <li><a href="#get_source">Getting the Source</a></li>
ohair@276 43 </ul>
ohair@276 44 </li>
ohair@13 45 <li><a href="#MBE">Minimum Build Environments</a></li>
robilad@132 46 <li><a href="#SDBE">Specific Developer Build Environments</a>
ohair@41 47 <ul>
ohair@41 48 <li><a href="#fedora">Fedora Linux</a> </li>
ohair@41 49 <li><a href="#centos">CentOS Linux</a> </li>
ohair@276 50 <li><a href="#debian">Debian GNU/Linux</a></li>
ohair@276 51 <li><a href="#ubuntu">Ubuntu Linux</a> </li>
ohair@276 52 <li><a href="#opensuse">OpenSUSE</a></li>
ohair@276 53 <li><a href="#mandriva">Mandriva</a></li>
ohair@276 54 <li><a href="#opensolaris">OpenSolaris</a></li>
ohair@41 55 </ul>
ohair@276 56 </li>
ohair@13 57 <li><a href="#directories">Source Directory Structure</a> </li>
ohair@13 58 <li><a href="#building">Build Information</a>
ohair@13 59 <ul>
ohair@13 60 <li><a href="#gmake">GNU Make (<tt><i>gmake</i></tt>)</a> </li>
ohair@13 61 <li><a href="#linux">Basic Linux System Setup</a> </li>
ohair@13 62 <li><a href="#solaris">Basic Solaris System Setup</a> </li>
ohair@13 63 <li><a href="#windows">Basic Windows System Setup</a> </li>
ohair@276 64 <li><a href="#dependencies">Build Dependencies</a>
ohair@276 65 <ul>
ohair@276 66 <li><a href="#bootjdk">Bootstrap JDK</a> </li>
ohair@276 67 <li><a href="#binaryplugs">Binary Plugs</a> </li>
ohair@276 68 <li><a href="#importjdk">Optional Import JDK</a> </li>
ohair@276 69 <li><a href="#ant">Ant</a> </li>
ohair@276 70 <li><a href="#cacerts">Certificate Authority File (cacert)</a> </li>
ohair@276 71 <li><a href="#compilers">Compilers</a>
ohair@276 72 <ul>
ohair@276 73 <li><a href="#msvc32">Microsoft Visual Studio Professional/Express for 32 bit</a> </li>
ohair@276 74 <li><a href="#msvc64">Microsoft Visual Studio Professional for 64 bit</a> </li>
ohair@276 75 <li><a href="#mssdk64">Microsoft Windows SDK for 64 bit</a> </li>
ohair@276 76 <li><a href="#gcc">Linux gcc/binutils</a> </li>
ohair@276 77 <li><a href="#studio">Sun Studio</a> </li>
ohair@276 78 </ul>
ohair@276 79 </li>
ohair@276 80 <li><a href="#zip">Zip and Unzip</a> </li>
ohair@276 81 <li><a href="#freetype">FreeType2 Fonts</a> </li>
ohair@276 82 <li>Linux and Solaris:
ohair@276 83 <ul>
ohair@276 84 <li><a href="#cups">CUPS Include files</a> </li>
ohair@276 85 <li><a href="#xrender">XRender Include files</a></li>
ohair@276 86 </ul>
ohair@276 87 </li>
ohair@276 88 <li>Linux only:
ohair@276 89 <ul>
ohair@276 90 <li><a href="#alsa">ALSA files</a> </li>
ohair@276 91 </ul>
ohair@276 92 </li>
ohair@276 93 <li>Windows only:
ohair@276 94 <ul>
ohair@276 95 <li>Unix Command Tools (<a href="#cygwin">CYGWIN</a>)</li>
ohair@276 96 <li><a href="#dxsdk">DirectX 9.0 SDK</a> </li>
ohair@276 97 </ul>
ohair@276 98 </li>
ohair@276 99 </ul>
ohair@276 100 </li>
ohair@13 101 </ul>
ohair@13 102 </li>
ohair@13 103 <li><a href="#creating">Creating the Build</a> </li>
ohair@13 104 <li><a href="#testing">Testing the Build</a> </li>
ohair@13 105 <li><a href="#variables">Environment/Make Variables</a></li>
ohair@13 106 <li><a href="#troubleshooting">Troubleshooting</a></li>
ohair@13 107 </ul>
ohair@13 108 </blockquote>
ohair@276 109
ohair@276 110 <!-- ------------------------------------------------------ -->
ohair@276 111 <hr>
ohair@276 112 <h2><a name="hg">Use of Mercurial</a></h2>
ohair@276 113 <blockquote>
ohair@276 114 The OpenJDK sources are maintained with the revision control system
ohair@276 115 <a href="">Mercurial</a>.
ohair@276 116 If you are new to Mercurial, please see the
ohair@276 117 <a href="">Beginner Guides</a>
ohair@276 118 or refer to the <a href=""">Mercurial Book</a>.
ohair@276 119 The first few chapters of the book provide an excellent overview of
ohair@276 120 Mercurial, what it is and how it works.
ohair@276 121 <br>
ohair@276 122 For using Mercurial with the OpenJDK refer to the
ohair@276 123 <a href=""">
ohair@276 124 Developer Guide: Installing and Configuring Mercurial</a>
ohair@276 125 section for more information.
ohair@276 126 The Forest Extension is not part of the Mercurial install,
ohair@276 127 and is optional,
ohair@276 128 but can be obtained with the following commands:
ohair@276 129 <blockquote>
ohair@276 130 <tt>
ohair@276 131 hg clone <i>YourHgForest</i>
ohair@276 132 </tt>
ohair@276 133 </blockquote>
ohair@276 134 Once you have the file <tt></tt>, you need to add these
ohair@276 135 lines to your <tt>${HOME}/.hgrc</tt> file:
ohair@276 136 <blockquote>
ohair@276 137 <tt>
ohair@276 138 [extensions]
ohair@276 139 <br>forest = <i>YourHgForest</i>/
ohair@276 140 </tt>
ohair@276 141 </blockquote>
ohair@276 142
ohair@276 143 <!-- ------------------------------------------------------ -->
ohair@276 144 <h3><a name="get_source">Getting the Source</a></h3>
ohair@276 145 <blockquote>
ohair@276 146 To get the entire set of OpenJDK Mercurial repositories
ohair@276 147 using the Forest Extension:
ohair@276 148 <blockquote>
ohair@276 149 <tt>
ohair@276 150 hg fclone <i>YourOpenJDK</i>
ohair@276 151 </tt>
ohair@276 152 </blockquote>
ohair@276 153 To get the entire set of OpenJDK Mercurial repositories
ohair@276 154 without using the Forest Extension:
ohair@276 155 <blockquote>
ohair@276 156 <tt>
ohair@276 157 hg clone <i>YourOpenJDK</i>
ohair@276 158 <br>cd <i>YourOpenJDK</i>
ohair@276 159 <br>sh ./
ohair@276 160 </tt>
ohair@276 161 </blockquote>
ohair@276 162 Once you have all the repositories, the
ohair@276 163 script <tt>make/scripts/</tt>
ohair@276 164 can be used to repeat the same <tt>hg</tt>
ohair@276 165 command on every repository in the forest, e.g.
ohair@276 166 <blockquote>
ohair@276 167 <tt>
ohair@276 168 cd <i>YourOpenJDK</i>
ohair@276 169 <br>sh ./make/scripts/ pull -u
ohair@276 170 </tt>
ohair@276 171 </blockquote>
ohair@276 172 You may find this script <tt>make/scripts/</tt> faster
ohair@276 173 than the <tt>hg</tt> forest commands provided by the
ohair@276 174 Forest Extension.
ohair@276 175 </blockquote>
ohair@276 176
ohair@276 177 </blockquote>
ohair@276 178
ohair@13 179 <!-- ------------------------------------------------------ -->
ohair@13 180 <hr>
ohair@13 181 <h2><a name="MBE">Minimum Build Environments</a></h2>
ohair@13 182 <blockquote>
ohair@13 183 This file often describes specific requirements for what we call the
ohair@49 184 "minimum build environments" (MBE) for this
ohair@49 185 specific release of the JDK,
ohair@13 186 Building with the MBE will generate the most compatible
ohair@13 187 bits that install on, and run correctly on, the most variations
ohair@13 188 of the same base OS and hardware architecture.
ohair@13 189 These usually represent what is often called the
ohair@13 190 least common denominator platforms.
ohair@13 191 It is understood that most developers will NOT be using these
ohair@13 192 specific platforms, and in fact creating these specific platforms
ohair@13 193 may be difficult due to the age of some of this software.
ohair@13 194 <p>
ohair@276 195 The minimum OS and C/C++ compiler versions needed for building the
ohair@276 196 OpenJDK:
ohair@13 197 <p>
ohair@13 198 <table border="1">
ohair@13 199 <thead>
ohair@13 200 <tr>
ohair@13 201 <th>Base OS and Architecture</th>
ohair@13 202 <th>OS</th>
ohair@49 203 <th>C/C++ Compiler</th>
xdono@105 204 <th>BOOT JDK</th>
ohair@13 205 </tr>
ohair@13 206 </thead>
ohair@13 207 <tbody>
ohair@13 208 <tr>
ohair@49 209 <td>Linux X86 (32-bit)</td>
ohair@49 210 <td>Fedora 9</td>
ohair@13 211 <td>gcc 4 </td>
xdono@105 212 <td>JDK 6u14 FCS </td>
ohair@13 213 </tr>
ohair@13 214 <tr>
ohair@49 215 <td>Linux X64 (64-bit)</td>
ohair@49 216 <td>Fedora 9</td>
ohair@13 217 <td>gcc 4 </td>
xdono@105 218 <td>JDK 6u14 FCS </td>
ohair@13 219 </tr>
ohair@13 220 <tr>
ohair@49 221 <td>Solaris SPARC (32-bit)</td>
xdono@105 222 <td>Solaris 10u2 + patches
ohair@13 223 <br>
ohair@13 224 See <a href="" target="_blank">
ohair@276 225 SunSolve</a> for patch downloads.
ohair@13 226 </td>
ohair@211 227 <td>Sun Studio 12 Update 1 + patches</td>
xdono@105 228 <td>JDK 6u14 FCS </td>
ohair@13 229 </tr>
ohair@13 230 <tr>
ohair@49 231 <td>Solaris SPARCV9 (64-bit)</td>
xdono@105 232 <td>Solaris 10u2 + patches
ohair@13 233 <br>
ohair@13 234 See <a href="" target="_blank">
ohair@276 235 SunSolve</a> for patch downloads.
ohair@13 236 </td>
ohair@211 237 <td>Sun Studio 12 Update 1 + patches</td>
xdono@105 238 <td>JDK 6u14 FCS </td>
ohair@13 239 </tr>
ohair@13 240 <tr>
ohair@49 241 <td>Solaris X86 (32-bit)</td>
xdono@105 242 <td>Solaris 10u2 + patches
ohair@13 243 <br>
ohair@13 244 See <a href="" target="_blank">
ohair@276 245 SunSolve</a> for patch downloads.
ohair@13 246 </td>
ohair@211 247 <td>Sun Studio 12 Update 1 + patches</td>
xdono@105 248 <td>JDK 6u14 FCS </td>
ohair@13 249 </tr>
ohair@13 250 <tr>
ohair@49 251 <td>Solaris X64 (64-bit)</td>
xdono@105 252 <td>Solaris 10u2 + patches
ohair@13 253 <br>
ohair@13 254 See <a href="" target="_blank">
ohair@276 255 SunSolve</a> for patch downloads.
ohair@13 256 </td>
ohair@211 257 <td>Sun Studio 12 Update 1 + patches</td>
xdono@105 258 <td>JDK 6u14 FCS </td>
ohair@13 259 </tr>
ohair@13 260 <tr>
ohair@49 261 <td>Windows X86 (32-bit)</td>
ohair@13 262 <td>Windows XP</td>
prr@175 263 <td>Microsoft Visual Studio C++ 2010 Professional Edition</td>
xdono@105 264 <td>JDK 6u14 FCS </td>
ohair@13 265 </tr>
ohair@13 266 <tr>
ohair@49 267 <td>Windows X64 (64-bit)</td>
ohair@13 268 <td>Windows Server 2003 - Enterprise x64 Edition</td>
prr@175 269 <td>Microsoft Visual Studio C++ 2010 Professional Edition</td>
xdono@105 270 <td>JDK 6u14 FCS </td>
ohair@13 271 </tr>
ohair@13 272 </tbody>
ohair@13 273 </table>
ohair@276 274 <p>
ohair@49 275 These same sources do indeed build on many more systems than the
ohair@49 276 above older generation systems, again the above is just a minimum.
ohair@276 277 <p>
ohair@49 278 Compilation problems with newer or different C/C++ compilers is a
ohair@49 279 common problem.
ohair@49 280 Similarly, compilation problems related to changes to the
ohair@276 281 <tt>/usr/include</tt> or system header files is also a
ohair@49 282 common problem with newer or unreleased OS versions.
ohair@49 283 Please report these types of problems as bugs so that they
ohair@49 284 can be dealt with accordingly.
ohair@13 285 </blockquote>
ohair@13 286 <!-- ------------------------------------------------------ -->
ohair@13 287 <hr>
ohair@13 288 <h2><a name="SDBE">Specific Developer Build Environments</a></h2>
ohair@13 289 <blockquote>
ohair@13 290 We won't be listing all the possible environments, but
ohair@13 291 we will try to provide what information we have available to us.
ohair@13 292 </blockquote>
ohair@13 293 <!-- ------------------------------------------------------ -->
robilad@132 294 <h3><a name="fedora">Fedora</a></h3>
ohair@13 295 <blockquote>
ohair@276 296 <h4>Fedora 9</h4>
ohair@276 297 <p>
ohair@276 298 <blockquote>
ohair@276 299 After installing <a href="">Fedora</a> 9
robilad@132 300 you need to install several build dependencies. The simplest
robilad@132 301 way to do it is to execute the following commands as user
ohair@276 302 <tt>root</tt>:
ohair@276 303 <p/>
ohair@276 304 <code>yum-builddep java-openjdk</code>
ohair@276 305 <p/>
ohair@276 306 <code>yum install gcc gcc-c++</code>
ohair@276 307 <p/>
robilad@132 308 In addition, it's necessary to set a few environment variables for the build:
robilad@132 309
ohair@276 310 <p/>
ohair@276 311 <code>export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-openjdk</code>
ohair@41 312 </blockquote>
ohair@276 313 <h4>Fedora 10</h4>
ohair@276 314 <p>
ohair@276 315 <blockquote>
ohair@276 316 After installing <a href="">Fedora</a> 10
robilad@132 317 you need to install several build dependencies. The simplest
robilad@132 318 way to do it is to execute the following commands as user
ohair@276 319 <tt>root</tt>:
ohair@276 320 <p/>
ohair@276 321 <code>yum-builddep java-1.6.0-openjdk</code>
ohair@276 322 <p/>
ohair@276 323 <code>yum install gcc gcc-c++</code>
ohair@276 324 <p/>
robilad@132 325 In addition, it's necessary to set a few environment variables for the build:
robilad@132 326
ohair@276 327 <p/>
ohair@276 328 <code>export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-openjdk</code>
robilad@132 329 </blockquote>
ohair@276 330 <h4>Fedora 11</h4>
ohair@276 331 <p>
ohair@276 332 <blockquote>
ohair@276 333 After installing <a href="">Fedora</a> 11
robilad@132 334 you need to install several build dependencies. The simplest
robilad@132 335 way to do it is to execute the following commands as user
ohair@276 336 <tt>root</tt>:
ohair@276 337 <p/>
ohair@276 338 <code>yum-builddep java-1.6.0-openjdk</code>
ohair@276 339 <p/>
ohair@276 340 <code>yum install gcc gcc-c++</code>
ohair@276 341 <p/>
robilad@132 342 In addition, it's necessary to set a few environment variables for the build:
robilad@132 343
ohair@276 344 <p/>
ohair@276 345 <code>export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-openjdk</code>
ohair@276 346 </blockquote>
ohair@13 347 </blockquote>
ohair@13 348 <!-- ------------------------------------------------------ -->
ohair@41 349 <h3><a name="centos">CentOS 5.2</a></h3>
ohair@13 350 <blockquote>
ohair@41 351 After installing
ohair@41 352 <a href="">CentOS 5.2</a>
ohair@41 353 you need to make sure you have
ohair@41 354 the following Development bundles installed:
ohair@41 355 <blockquote>
ohair@41 356 <ul>
ohair@41 357 <li>Development Libraries</li>
ohair@41 358 <li>Development Tools</li>
ohair@41 359 <li>Java Development</li>
ohair@41 360 <li>X Software Development</li>
ohair@41 361 </ul>
ohair@41 362 </blockquote>
ohair@41 363 <p>
ohair@276 364 Plus the following packages:
ohair@41 365 <blockquote>
ohair@41 366 <ul>
ohair@41 367 <li>cups devel: Cups Development Package</li>
ohair@41 368 <li>alsa devel: Alsa Development Package</li>
ohair@41 369 <li>ant: Ant Package</li>
ohair@41 370 <li>Xi devel: Development Package</li>
ohair@41 371 </ul>
ohair@41 372 </blockquote>
ohair@41 373 <p>
ohair@276 374 The freetype 2.3 packages don't seem to be available,
ohair@276 375 but the freetype 2.3 sources can be downloaded, built,
ohair@276 376 and installed easily enough from
ohair@276 377 <a href="">
ohair@276 378 the freetype site</a>.
ohair@276 379 Build and install with something like:
ohair@41 380 <blockquote>
ohair@41 381 <tt>./configure && make && sudo -u root make install</tt>
ohair@41 382 </blockquote>
ohair@41 383 <p>
ohair@276 384 Mercurial packages could not be found easily, but a Google
ohair@276 385 search should find ones, and they usually include Python if
ohair@276 386 it's needed.
ohair@13 387 </blockquote>
ohair@13 388 <!-- ------------------------------------------------------ -->
robilad@132 389 <h3><a name="debian">Debian</a></h3>
ohair@13 390 <blockquote>
robilad@132 391 <h4>Debian 5.0 (Lenny)</h4>
ohair@13 392 <p>
ohair@276 393 <blockquote>
robilad@132 394 After installing <a href="">Debian</a> 5
robilad@132 395 you need to install several build dependencies.
robilad@132 396 The simplest way to install the build dependencies is to
robilad@132 397 execute the following commands as user <tt>root</tt>:
ohair@276 398 <p/>
ohair@276 399 <code>aptitude build-dep openjdk-6</code>
ohair@276 400 <p/>
ohair@276 401 <code>aptitude install openjdk-6-jdk libmotif-dev</code>
ohair@276 402 <p/>
robilad@132 403 In addition, it's necessary to set a few environment variables for the build:
ohair@276 404 <p/>
ohair@276 405 <code>export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-6-openjdk</code>
ohair@276 406 </blockquote>
robilad@132 407 </blockquote>
robilad@132 408 <!-- ====================================================== -->
ohair@276 409 <h3><a name="ubuntu">Ubuntu</a></h3>
robilad@132 410 <blockquote>
robilad@132 411 <h4>Ubuntu 8.04</h4>
ohair@13 412 <p>
ohair@276 413 <blockquote>
robilad@132 414 After installing <a href="">Ubuntu</a> 8.04
robilad@132 415 you need to install several build dependencies.
ohair@276 416 <p/>
robilad@132 417 First, you need to enable the universe repository in the
robilad@132 418 Software Sources application and reload the repository
robilad@132 419 information. The Software Sources application is available
robilad@132 420 under the System/Administration menu.
ohair@276 421 <p/>
robilad@132 422 The simplest way to install the build dependencies is to
robilad@132 423 execute the following commands:
ohair@276 424 <p/>
ohair@276 425 <code>sudo aptitude build-dep openjdk-6</code>
ohair@276 426 <p/>
ohair@276 427 <code>sudo aptitude install openjdk-6-jdk</code>
ohair@276 428 <p/>
robilad@132 429 In addition, it's necessary to set a few environment variables for the build:
ohair@276 430 <p/>
ohair@276 431 <code>export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-6-openjdk</code>
ohair@276 432 </blockquote>
ohair@276 433 <h4>Ubuntu 8.10</h4>
ohair@13 434 <p>
ohair@276 435 <blockquote>
robilad@132 436 After installing <a href="">Ubuntu</a> 8.10
robilad@132 437 you need to install several build dependencies. The simplest
robilad@132 438 way to do it is to execute the following commands:
ohair@276 439 <p/>
ohair@276 440 <code>sudo aptitude build-dep openjdk-6</code>
ohair@276 441 <p/>
ohair@276 442 <code>sudo aptitude install openjdk-6-jdk</code>
ohair@276 443 <p/>
robilad@132 444 In addition, it's necessary to set a few environment variables for the build:
ohair@276 445 <p/>
ohair@276 446 <code>export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-6-openjdk</code>
ohair@276 447 </blockquote>
ohair@276 448 <h4>Ubuntu 9.04</h4>
ohair@13 449 <p>
ohair@276 450 <blockquote>
robilad@132 451 After installing <a href="">Ubuntu</a> 9.04
robilad@132 452 you need to install several build dependencies. The simplest
robilad@132 453 way to do it is to execute the following commands:
ohair@276 454 <p/>
ohair@276 455 <code>sudo aptitude build-dep openjdk-6</code>
ohair@276 456 <p/>
ohair@276 457 <code>sudo aptitude install openjdk-6-jdk</code>
ohair@276 458 <p/>
robilad@132 459 In addition, it's necessary to set a few environment variables for the build:
ohair@276 460 <p/>
ohair@276 461 <code>export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-6-openjdk</code>
ohair@276 462 </blockquote>
ohair@13 463 </blockquote>
robilad@132 464 <!-- ====================================================== -->
robilad@132 465 <h3><a name="opensuse">OpenSUSE</a></h3>
robilad@132 466 <blockquote>
robilad@132 467 <h4>OpenSUSE 11.1</h4>
robilad@132 468 <p>
ohair@276 469 <blockquote>
robilad@132 470 After installing <a href="">OpenSUSE</a> 11.1
robilad@132 471 you need to install several build dependencies.
robilad@132 472 The simplest way to install the build dependencies is to
robilad@132 473 execute the following commands:
ohair@276 474 <p/>
ohair@276 475 <code>sudo zypper source-install -d java-1_6_0-openjdk</code>
ohair@276 476 <p/>
ohair@276 477 <code>sudo zypper install make</code>
ohair@276 478 <p/>
robilad@132 479 In addition, it is necessary to set a few environment variables for the build:
ohair@276 480 <p/>
ohair@276 481 <code>export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-1.6.0-openjdk</code>
ohair@276 482 <p/>
robilad@132 483 Finally, you need to unset the <code>JAVA_HOME</code> environment variable:
ohair@276 484 <p/>
ohair@276 485 <code>export -n JAVA_HOME</code>
ohair@276 486 </blockquote>
ohair@276 487 </blockquote>
robilad@132 488 <!-- ====================================================== -->
robilad@132 489 <h3><a name="mandriva">Mandriva</a></h3>
robilad@132 490 <blockquote>
robilad@132 491 <h4>Mandriva Linux One 2009 Spring</h4>
robilad@132 492 <p>
ohair@276 493 <blockquote>
robilad@132 494 After installing <a href="">Mandriva</a> Linux One 2009 Spring
robilad@132 495 you need to install several build dependencies.
robilad@132 496 The simplest way to install the build dependencies is to
robilad@132 497 execute the following commands as user <tt>root</tt>:
ohair@276 498 <p/>
ohair@276 499 <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>
robilad@132 500 <p/>
robilad@132 501 In addition, it is necessary to set a few environment variables for the build:
ohair@276 502 <p/>
ohair@276 503 <code>export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-1.6.0-openjdk</code>
ohair@276 504 </blockquote>
robilad@132 505 </blockquote>
robilad@132 506 <!-- ====================================================== -->
robilad@132 507 <h3><a name="opensolaris">OpenSolaris</a></h3>
robilad@132 508 <blockquote>
robilad@132 509 <h4>OpenSolaris 2009.06</h4>
robilad@132 510 <p>
ohair@276 511 <blockquote>
robilad@132 512 After installing <a href="">OpenSolaris</a> 2009.06
robilad@132 513 you need to install several build dependencies.
robilad@132 514 The simplest way to install the build dependencies is to
robilad@132 515 execute the following commands:
ohair@276 516 <p/>
ohair@276 517 <code>pfexec pkg install SUNWgmake SUNWj6dev SUNWant sunstudioexpress SUNWcups SUNWzip SUNWunzip SUNWxwhl SUNWxorg-headers SUNWaudh SUNWfreetype2</code>
robilad@132 518 <p/>
robilad@132 519 In addition, it is necessary to set a few environment variables for the build:
ohair@276 520 <p/>
ohair@276 521 <code>export LANG=C ALT_COMPILER_PATH=/opt/SunStudioExpress/bin/ ALT_CUPS_HEADERS_PATH=/usr/include/</code>
ohair@276 522 <p/>
robilad@132 523 Finally, you need to make sure that the build process can find the Sun Studio compilers:
ohair@276 524 <p/>
ohair@276 525 <code>export PATH=$PATH:/opt/SunStudioExpress/bin/</code>
ohair@276 526 </blockquote>
robilad@132 527 </blockquote>
robilad@132 528 <!-- ------------------------------------------------------ -->
ohair@13 529 <hr>
ohair@13 530 <h2><a name="directories">Source Directory Structure</a></h2>
ohair@13 531 <blockquote>
ohair@13 532 <p>
ohair@276 533 The source code for the OpenJDK is delivered in a set of
ohair@276 534 directories:
ohair@276 535 <tt>hotspot</tt>,
ohair@276 536 <tt>langtools</tt>,
ohair@276 537 <tt>corba</tt>,
ohair@276 538 <tt>jaxws</tt>,
ohair@276 539 <tt>jaxp</tt>,
ohair@276 540 and
ohair@276 541 <tt>jdk</tt>.
ohair@276 542 The <tt>hotspot</tt> directory contains the source code and make
ohair@276 543 files for building the OpenJDK Hotspot Virtual Machine.
ohair@276 544 The <tt>langtools</tt> directory contains the source code and make
ohair@276 545 files for building the OpenJDK javac and language tools.
ohair@276 546 The <tt>corba</tt> directory contains the source code and make
ohair@276 547 files for building the OpenJDK Corba files.
ohair@276 548 The <tt>jaxws</tt> directory contains the source code and make
ohair@276 549 files for building the OpenJDK JAXWS files.
ohair@276 550 The <tt>jaxp</tt> directory contains the source code and make
ohair@276 551 files for building the OpenJDK JAXP files.
ohair@276 552 The <tt>jdk</tt> directory contains the source code and make files for
ohair@276 553 building the OpenJDK runtime libraries and misc files.
ohair@276 554 The top level <tt>Makefile</tt>
ohair@276 555 is used to build the entire OpenJDK.
ohair@13 556 </blockquote>
ohair@13 557 <!-- ------------------------------------------------------ -->
ohair@13 558 <hr>
ohair@13 559 <h2><a name="building">Build Information</a></h2>
ohair@13 560 <blockquote>
ohair@13 561 Building the OpenJDK
ohair@13 562 is done with a <tt><i>gmake</i></tt>
ohair@13 563 command line and various
ohair@13 564 environment or make variable settings that direct the make rules
ohair@13 565 to where various components have been installed.
ohair@13 566 Where possible the makefiles will attempt to located the various
ohair@13 567 components in the default locations or any component specific
ohair@13 568 variable settings.
ohair@13 569 When the normal defaults fail or components cannot be found,
ohair@13 570 the various
ohair@13 571 <tt>ALT_*</tt> variables (alternates)
ohair@13 572 can be used to help the makefiles locate components.
ohair@13 573 <p>
ohair@276 574 Refer to the bash/sh/ksh setup file
ohair@276 575 <tt>jdk/make/</tt>
ohair@276 576 if you need help in setting up your environment variables.
ohair@276 577 A build could be as simple as:
ohair@13 578 <blockquote>
ohair@13 579 <pre><tt>
duke@2 580 bash
duke@2 581 . jdk/make/
duke@2 582 <i>gmake</i> sanity &amp;&amp; <i>gmake</i>
ohair@13 583 </tt></pre>
ohair@13 584 </blockquote>
ohair@13 585 <p>
ohair@276 586 Of course ksh or sh would work too.
ohair@276 587 But some customization will probably be necessary.
ohair@276 588 The <tt>sanity</tt> rule will make some basic checks on build
ohair@276 589 dependencies and generate appropriate warning messages
ohair@276 590 regarding missing, out of date, or newer than expected components
ohair@276 591 found on your system.
ohair@13 592 </blockquote>
ohair@13 593 <!-- ------------------------------------------------------ -->
ohair@13 594 <hr>
ohair@13 595 <h3><a name="gmake">GNU make (<tt><i>gmake</i></tt>)</a></h3>
ohair@13 596 <blockquote>
ohair@13 597 The Makefiles in the OpenJDK are only valid when used with the
ohair@13 598 GNU version of the utility command <tt>make</tt>
ohair@13 599 (<tt><i>gmake</i></tt>).
ohair@13 600 A few notes about using GNU make:
ohair@13 601 <ul>
ohair@13 602 <li>
ohair@262 603 In general, you need GNU make version 3.81 or newer.
ohair@13 604 </li>
ohair@13 605 <li>
ohair@13 606 Place the location of the GNU make binary in the <tt>PATH</tt>.
ohair@13 607 </li>
ohair@13 608 <li>
ohair@13 609 <strong>Linux:</strong>
ohair@13 610 The <tt>/usr/bin/make</tt> command should work fine for you.
ohair@13 611 </li>
ohair@13 612 <li>
ohair@13 613 <strong>Solaris:</strong>
ohair@13 614 Do NOT use <tt>/usr/bin/make</tt> on Solaris.
ohair@13 615 If your Solaris system has the software
ohair@13 616 from the Solaris Companion CD installed,
ohair@13 617 you should use <tt>gmake</tt>
ohair@13 618 which will be located in either the <tt>/opt/sfw/bin</tt> or
ohair@13 619 <tt>/usr/sfw/bin</tt> directory.
ohair@25 620 In more recent versions of Solaris GNU make can be found
ohair@25 621 at <tt>/usr/bin/gmake</tt>.
ohair@13 622 </li>
ohair@13 623 <li>
ohair@13 624 <strong>Windows:</strong>
ohair@138 625 Make sure you start your build inside a bash/sh/ksh shell
ohair@138 626 and are using a <tt>make.exe</tt> utility built for that
ohair@138 627 environment (a cygwin <tt>make.exe</tt> is not the same
ohair@138 628 as a <tt>make.exe</tt> built for something like
ohair@138 629 <a href="">MKS</a>).
ohair@13 630 <br>
ohair@13 631 <b>WARNING:</b> Watch out for make version 3.81, it may
ohair@25 632 not work due to a lack of support for MS-DOS drive letter paths
ohair@25 633 like <tt>C:/</tt> or <tt>C:\</tt>.
ohair@13 634 Use a 3.80 version, or find a newer
ohair@49 635 version that has this problem fixed.
ohair@13 636 The older 3.80 version of make.exe can be downloaded with this
ohair@13 637 <a href="" target="_blank">
ohair@276 638 link</a>.
ohair@25 639 Use of this older 3.80 make.exe may require that you install the
ohair@25 640 libintl2.dll library or libintl2 cygwin package which is
ohair@25 641 no longer installed by default by the cygwin installer.
ohair@25 642 <br>
ohair@13 643 Also see the
ohair@13 644 <a href="" target="_blank">
ohair@276 645 mozilla developer center</a>
ohair@13 646 on this topic.
ohair@25 647 <br>
ohair@25 648 It's hoped that when make 3.82 starts shipping in a future cygwin
ohair@25 649 release that this MS-DOS path issue will be fixed.
ohair@25 650 In addition to the above 3.80 make.exe you can download
ohair@25 651 this
ohair@25 652 <a href="">
ohair@276 653 make.exe</a> which will not have a libintl2.dll
ohair@25 654 dependency.
ohair@13 655 </li>
ohair@13 656 </ul>
ohair@13 657 <p>
ohair@276 658 Information on GNU make, and access to ftp download sites, are
ohair@276 659 available on the
ohair@276 660 <a href="" target="_blank">
ohair@276 661 GNU make web site
ohair@276 662 </a>.
ohair@276 663 The latest source to GNU make is available at
ohair@276 664 <a href="" target="_blank">
ohair@276 665</a>.
ohair@13 666 </blockquote>
ohair@13 667 <!-- ------------------------------------------------------ -->
ohair@13 668 <hr>
ohair@13 669 <h3><a name="linux">Basic Linux System Setup</a></h3>
ohair@13 670 <blockquote>
ohair@13 671 <strong>i586 only:</strong>
ohair@13 672 The minimum recommended hardware for building the Linux version
ohair@13 673 is a Pentium class processor or better, at least 256 MB of RAM, and
ohair@13 674 approximately 1.5 GB of free disk space.
ohair@13 675 <p>
ohair@276 676 <strong>X64 only:</strong>
ohair@276 677 The minimum recommended hardware for building the Linux
ohair@276 678 version is an AMD Opteron class processor, at least 512 MB of RAM, and
ohair@276 679 approximately 4 GB of free disk space.
ohair@13 680 <p>
ohair@276 681 The build will use the tools contained in
ohair@276 682 <tt>/bin</tt> and
ohair@276 683 <tt>/usr/bin</tt>
ohair@276 684 of a standard installation of the Linux operating environment.
ohair@276 685 You should ensure that these directories are in your
ohair@276 686 <tt>PATH</tt>.
ohair@13 687 <p>
ohair@276 688 Note that some Linux systems have a habit of pre-populating
ohair@276 689 your environment variables for you, for example <tt>JAVA_HOME</tt>
ohair@276 690 might get pre-defined for you to refer to the JDK installed on
ohair@276 691 your Linux system.
ohair@276 692 You will need to unset <tt>JAVA_HOME</tt>.
ohair@276 693 It's a good idea to run <tt>env</tt> and verify the
ohair@276 694 environment variables you are getting from the default system
ohair@276 695 settings make sense for building the
ohair@276 696 OpenJDK.
ohair@13 697 </blockquote>
ohair@13 698 <!-- ------------------------------------------------------ -->
ohair@13 699 <h4><a name="linux_checklist">Basic Linux Check List</a></h4>
ohair@13 700 <blockquote>
ohair@13 701 <ol>
ohair@13 702 <li>
ohair@13 703 Install the
ohair@13 704 <a href="#bootjdk">Bootstrap JDK</a>, set
ohair@13 705 <tt><a href="#ALT_BOOTDIR">ALT_BOOTDIR</a></tt>.
ohair@13 706 </li>
ohair@13 707 <li>
ohair@13 708 Install the
ohair@13 709 <a href="#binaryplugs">Binary Plugs</a>, set
ohair@13 710 <tt><a href="#ALT_BINARY_PLUGS_PATH">ALT_BINARY_PLUGS_PATH</a></tt>.
ohair@13 711 </li>
ohair@13 712 <li>
ohair@13 713 <a href="#importjdk">Optional Import JDK</a>, set
ohair@13 714 <tt><a href="#ALT_JDK_IMPORT_PATH">ALT_JDK_IMPORT_PATH</a></tt>.
ohair@13 715 </li>
ohair@13 716 <li>
ohair@13 717 Install or upgrade the <a href="#freetype">FreeType development
ohair@276 718 package</a>.
ohair@13 719 </li>
ohair@25 720 <li>
ohair@25 721 Install
ohair@49 722 <a href="#ant">Ant</a>,
ohair@49 723 make sure it is in your PATH.
ohair@25 724 </li>
ohair@13 725 </ol>
ohair@13 726 </blockquote>
ohair@13 727 <!-- ------------------------------------------------------ -->
ohair@13 728 <hr>
ohair@13 729 <h3><a name="solaris">Basic Solaris System Setup</a></h3>
ohair@13 730 <blockquote>
ohair@13 731 The minimum recommended hardware for building the
ohair@13 732 Solaris SPARC version is an UltraSPARC with 512 MB of RAM.
ohair@13 733 For building
ohair@13 734 the Solaris x86 version, a Pentium class processor or better and at
ohair@13 735 least 512 MB of RAM are recommended.
ohair@13 736 Approximately 1.4 GB of free disk
ohair@13 737 space is needed for a 32-bit build.
ohair@13 738 <p>
ohair@276 739 If you are building the 64-bit version, you should
ohair@276 740 run the command "isainfo -v" to verify that you have a
ohair@276 741 64-bit installation, it should say <tt>sparcv9</tt> or
ohair@276 742 <tt>amd64</tt>.
ohair@276 743 An additional 7 GB of free disk space is needed
ohair@276 744 for a 64-bit build.
ohair@13 745 <p>
ohair@276 746 The build uses the tools contained in <tt>/usr/ccs/bin</tt>
ohair@276 747 and <tt>/usr/bin</tt> of a standard developer or full installation of
ohair@276 748 the Solaris operating environment.
ohair@13 749 <p>
ohair@276 750 Solaris patches specific to the JDK can be downloaded from the
ohair@276 751 <a href="" target="_blank">
ohair@276 752 SunSolve JDK Solaris patches download page</a>.
ohair@276 753 You should ensure that the latest patch cluster for
ohair@276 754 your version of the Solaris operating environment has also
ohair@276 755 been installed.
ohair@13 756 </blockquote>
ohair@13 757 <!-- ------------------------------------------------------ -->
ohair@13 758 <h4><a name="solaris_checklist">Basic Solaris Check List</a></h4>
ohair@13 759 <blockquote>
ohair@13 760 <ol>
ohair@13 761 <li>
ohair@13 762 Install the
ohair@13 763 <a href="#bootjdk">Bootstrap JDK</a>, set
ohair@13 764 <tt><a href="#ALT_BOOTDIR">ALT_BOOTDIR</a></tt>.
ohair@13 765 </li>
ohair@13 766 <li>
ohair@13 767 Install the
ohair@13 768 <a href="#binaryplugs">Binary Plugs</a>, set
ohair@13 769 <tt><a href="#ALT_BINARY_PLUGS_PATH">ALT_BINARY_PLUGS_PATH</a></tt>.
ohair@13 770 </li>
ohair@13 771 <li>
ohair@13 772 <a href="#importjdk">Optional Import JDK</a>, set
ohair@13 773 <tt><a href="#ALT_JDK_IMPORT_PATH">ALT_JDK_IMPORT_PATH</a></tt>.
ohair@13 774 </li>
ohair@13 775 <li>
ohair@13 776 Install the
ohair@13 777 <a href="#studio">Sun Studio Compilers</a>, set
ohair@13 778 <a href="#ALT_COMPILER_PATH"><tt>ALT_COMPILER_PATH</tt></a>.
ohair@13 779 </li>
ohair@13 780 <li>
ohair@13 781 Install the
ohair@13 782 <a href="#cups">CUPS Include files</a>, set
ohair@13 783 <tt><a href="#ALT_CUPS_HEADERS_PATH">ALT_CUPS_HEADERS_PATH</a></tt>.
ohair@13 784 </li>
ohair@25 785 <li>
andrew@90 786 Install the <a href="#xrender">XRender Include files</a>.
andrew@90 787 </li>
andrew@90 788 <li>
ohair@25 789 Install
ohair@49 790 <a href="#ant">Ant</a>,
ohair@49 791 make sure it is in your PATH.
ohair@25 792 </li>
ohair@13 793 </ol>
ohair@13 794 </blockquote>
ohair@13 795 <!-- ------------------------------------------------------ -->
ohair@13 796 <hr>
ohair@13 797 <h3><a name="windows">Basic Windows System Setup</a></h3>
ohair@13 798 <blockquote>
ohair@13 799 <strong>i586 only:</strong>
ohair@49 800 The minimum recommended hardware for building the 32-bit or X86
ohair@13 801 Windows version is an Pentium class processor or better, at least
ohair@13 802 512 MB of RAM, and approximately 600 MB of free disk space.
ohair@13 803 <strong>
ohair@49 804 NOTE: The Windows build machines need to use the
ohair@13 805 file system NTFS.
ohair@13 806 Build machines formatted to FAT32 will not work
ohair@13 807 because FAT32 doesn't support case-sensitivity in file names.
ohair@13 808 </strong>
ohair@13 809 <p>
ohair@276 810 <strong>X64 only:</strong>
ohair@276 811 The minimum recommended hardware for building
ohair@276 812 the Windows X64 version is an AMD Opteron class processor, at least 1
ohair@276 813 GB of RAM, and approximately 10 GB of free disk space.
ohair@13 814 </blockquote>
ohair@13 815 <!-- ------------------------------------------------------ -->
ohair@13 816 <h4><a name="paths">Windows Paths</a></h4>
ohair@13 817 <blockquote>
duke@2 818 <strong>Windows:</strong>
ohair@13 819 Note that GNU make is a historic utility and is based very
ohair@13 820 heavily on shell scripting, so it does not tolerate the Windows habit
ohair@13 821 of having spaces in pathnames or the use of the <tt>\</tt>characters in pathnames.
ohair@13 822 Luckily on most Windows systems, you can use <tt>/</tt>instead of \, and
ohair@13 823 there is always a 'short' pathname without spaces for any path that
ohair@13 824 contains spaces.
ohair@13 825 Unfortunately, this short pathname can be somewhat dynamic and the
ohair@13 826 formula is difficult to explain.
ohair@13 827 You can use <tt>cygpath</tt> utility to map pathnames with spaces
ohair@13 828 or the <tt>\</tt>character into the <tt>C:/</tt> style of pathname
ohair@13 829 (called 'mixed'), e.g.
ohair@13 830 <tt>cygpath -s -m "<i>path</i>"</tt>.
ohair@13 831 <p>
ohair@276 832 The makefiles will try to translate any pathnames supplied
ohair@276 833 to it into the <tt>C:/</tt> style automatically.
ohair@13 834 <p>
ohair@276 835 Note that use of CYGWIN creates a unique problem with regards to
ohair@276 836 setting <a href="#path"><tt>PATH</tt></a>. Normally on Windows
ohair@276 837 the <tt>PATH</tt> variable contains directories
ohair@276 838 separated with the ";" character (Solaris and Linux uses ":").
ohair@276 839 With CYGWIN, it uses ":", but that means that paths like "C:/path"
ohair@276 840 cannot be placed in the CYGWIN version of <tt>PATH</tt> and
ohair@276 841 instead CYGWIN uses something like <tt>/cygdrive/c/path</tt>
ohair@276 842 which CYGWIN understands, but only CYGWIN understands.
ohair@276 843 So be careful with paths on Windows.
ohair@13 844 </blockquote>
ohair@13 845 <!-- ------------------------------------------------------ -->
ohair@13 846 <h4><a name="windows_checklist">Basic Windows Check List</a></h4>
duke@2 847 <blockquote>
ohair@13 848 <ol>
ohair@13 849 <li>
ohair@13 850 Install the
ohair@13 851 <a href="#cygwin">CYGWIN product</a>.
ohair@13 852 </li>
ohair@13 853 <li>
ohair@13 854 Install the
ohair@13 855 <a href="#bootjdk">Bootstrap JDK</a>, set
ohair@13 856 <tt><a href="#ALT_BOOTDIR">ALT_BOOTDIR</a></tt>.
ohair@13 857 </li>
ohair@13 858 <li>
ohair@13 859 Install the
ohair@13 860 <a href="#binaryplugs">Binary Plugs</a>, set
ohair@13 861 <tt><a href="#ALT_BINARY_PLUGS_PATH">ALT_BINARY_PLUGS_PATH</a></tt>..
ohair@13 862 </li>
ohair@13 863 <li>
ohair@13 864 <a href="#importjdk">Optional Import JDK</a>, set
ohair@13 865 <tt><a href="#ALT_JDK_IMPORT_PATH">ALT_JDK_IMPORT_PATH</a></tt>.
ohair@13 866 </li>
ohair@13 867 <li>
ohair@13 868 Install the
prr@187 869 <a href="#msvc32">Microsoft Visual Studio Compilers</a>).
ohair@13 870 </li>
ohair@13 871 <li>
ohair@13 872 Setup all environment variables for compilers
prr@187 873 (see <a href="#msvc32">compilers</a>).
ohair@13 874 </li>
ohair@13 875 <li>
ohair@13 876 Install
ohair@13 877 <a href="#dxsdk">Microsoft DirectX SDK</a>.
ohair@13 878 </li>
ohair@25 879 <li>
ohair@25 880 Install
ohair@49 881 <a href="#ant">Ant</a>,
ohair@49 882 make sure it is in your PATH and set
ohair@25 883 <tt><a href="#ANT_HOME">ANT_HOME</a></tt>.
ohair@25 884 </li>
ohair@13 885 </ol>
duke@2 886 </blockquote>
ohair@13 887 <!-- ------------------------------------------------------ -->
ohair@13 888 <hr>
ohair@13 889 <h3><a name="dependencies">Build Dependencies</a></h3>
duke@2 890 <blockquote>
ohair@13 891 Depending on the platform, the OpenJDK build process has some basic
ohair@13 892 dependencies on components not part of the OpenJDK sources.
ohair@13 893 Some of these are specific to a platform, some even specific to
ohair@13 894 an architecture.
ohair@13 895 Each dependency will have a set of ALT variables that can be set
ohair@13 896 to tell the makefiles where to locate the component.
ohair@13 897 In most cases setting these ALT variables may not be necessary
ohair@13 898 and the makefiles will find defaults on the system in standard
ohair@13 899 install locations or through component specific variables.
ohair@13 900 <!-- ------------------------------------------------------ -->
ohair@13 901 <h4><a name="bootjdk">Bootstrap JDK</a></h4>
ohair@13 902 <blockquote>
ohair@13 903 All OpenJDK builds require access to the previously released
ohair@13 904 JDK 6, this is often called a bootstrap JDK.
ohair@13 905 The JDK 6 binaries can be downloaded from Sun's
ohair@138 906 <a href=""
ohair@276 907 target="_blank">JDK 6 download site</a>.
ohair@13 908 For build performance reasons
ohair@13 909 is very important that this bootstrap JDK be made available on the
ohair@13 910 local disk of the machine doing the build.
ohair@13 911 You should always set
ohair@13 912 <tt><a href="#ALT_BOOTDIR">ALT_BOOTDIR</a></tt>
ohair@13 913 to point to the location of
ohair@13 914 the bootstrap JDK installation, this is the directory pathname
ohair@13 915 that contains a <tt>bin, lib, and include</tt>
ohair@13 916 It's also a good idea to also place its <tt>bin</tt> directory
ohair@13 917 in the <tt>PATH</tt> environment variable, although it's
ohair@13 918 not required.
ohair@13 919 <p>
ohair@276 920 <strong>Solaris:</strong>
ohair@276 921 Some pre-installed JDK images may be available to you in the
ohair@276 922 directory <tt>/usr/jdk/instances</tt>.
ohair@276 923 If you don't set
ohair@276 924 <tt><a href="#ALT_BOOTDIR">ALT_BOOTDIR</a></tt>
ohair@276 925 the makefiles will look in that location for a JDK it can use.
ohair@13 926 </blockquote>
ohair@13 927 <!-- ------------------------------------------------------ -->
ohair@13 928 <h4><a name="binaryplugs">Binary Plugs</a></h4>
ohair@13 929 <blockquote>
ohair@13 930 Not all of the source code that makes up the JDK is available
ohair@13 931 under an open-source license.
ohair@13 932 This is a temporary situation and these binary plugs will be
ohair@13 933 replaced with fully open source replacements as soon as possible.
ohair@13 934 So currently, in order to build a complete OpenJDK image,
ohair@13 935 you must first download and install the appropriate
ohair@13 936 binary plug bundles for the OpenJDK, go to the
ohair@13 937 <a href="" target="_blank">OpenJDK</a> site and select
ohair@49 938 the
ohair@49 939 "<b>Bundles(7)</b>"
ohair@49 940 link and download the binaryplugs for
ohair@13 941 your particular platform.
ohair@13 942 The file downloaded is a jar file that must be extracted by running
ohair@13 943 the jar file with:
ohair@13 944 <blockquote>
ohair@13 945 <pre>
ohair@13 946 <tt><b>java -jar jdk-7-ea-plug-b<i>nn</i>-<i>os</i>-<i>arch</i>-<i>dd</i>_<i>month</i>_<i>year</i>.jar</b></tt>
ohair@13 947 </pre>
ohair@13 948 </blockquote>
ohair@13 949 A prompt will be issued for acceptance of these binary plug files.
ohair@13 950 During the OpenJDK build process these "binary plugs"
ohair@13 951 for the encumbered components will be copied into your
ohair@13 952 resulting OpenJDK binary build image.
ohair@13 953 These binary plug files are only for the purpose of
ohair@13 954 building an OpenJDK binary.
ohair@13 955 Make sure you set
ohair@13 956 <tt><a href="#ALT_BINARY_PLUGS_PATH">ALT_BINARY_PLUGS_PATH</a></tt>
ohair@13 957 to the root of this installation.
ohair@13 958 </blockquote>
ohair@13 959 <!-- ------------------------------------------------------ -->
ohair@13 960 <h4><a name="importjdk">Optional Import JDK</a></h4>
ohair@13 961 <blockquote>
ohair@13 962 The <tt><a href="#ALT_JDK_IMPORT_PATH">ALT_JDK_IMPORT_PATH</a></tt>
ohair@13 963 setting is only needed if you are not building the entire
ohair@13 964 JDK. For example, if you have built the entire JDK once, and
ohair@13 965 wanted to avoid repeatedly building the Hotspot VM, you could
ohair@13 966 set this to the location of the previous JDK install image
ohair@13 967 and the build will copy the needed files from this import area.
ohair@13 968 </blockquote>
ohair@13 969 <!-- ------------------------------------------------------ -->
ohair@25 970 <h4><a name="ant">Ant</a></h4>
ohair@25 971 <blockquote>
ohair@25 972 All OpenJDK builds require access to least Ant 1.6.5.
ohair@25 973 The Ant tool is available from the
ohair@51 974 <a href="" target="_blank">
ohair@276 975 Ant download site</a>.
ohair@49 976 You should always make sure <tt>ant</tt> is in your PATH, and
ohair@49 977 on Windows you may also need to set
ohair@25 978 <tt><a href="#ANT_HOME">ANT_HOME</a></tt>
ohair@25 979 to point to the location of
ohair@25 980 the Ant installation, this is the directory pathname
ohair@25 981 that contains a <tt>bin and lib</tt>.
ohair@25 982 </blockquote>
ohair@25 983 <!-- ------------------------------------------------------ -->
ohair@13 984 <h4><a name="cacerts">Certificate Authority File (cacert)</a></h4>
ohair@13 985 <blockquote>
ohair@13 986 See <a href="" target="_blank">
ohair@276 987</a>
ohair@13 988 for a better understanding of the Certificate Authority (CA).
ohair@13 989 A certificates file named "cacerts"
ohair@13 990 represents a system-wide keystore with CA certificates.
ohair@13 991 In JDK and JRE
ohair@13 992 binary bundles, the "cacerts" file contains root CA certificates from
ohair@13 993 several public CAs (e.g., VeriSign, Thawte, and Baltimore).
ohair@13 994 The source contain a cacerts file
ohair@13 995 without CA root certificates.
ohair@13 996 Formal JDK builders will need to secure
ohair@13 997 permission from each public CA and include the certificates into their
ohair@13 998 own custom cacerts file.
ohair@13 999 Failure to provide a populated cacerts file
ohair@13 1000 will result in verification errors of a certificate chain during runtime.
ohair@13 1001 The variable
ohair@13 1002 <tt><a href="#ALT_CACERTS_FILE">ALT_CACERTS_FILE</a></tt>
ohair@13 1003 can be used to override the default location of the
ohair@13 1004 cacerts file that will get placed in your build.
ohair@13 1005 By default an empty cacerts file is provided and that should be
ohair@13 1006 fine for most JDK developers.
ohair@13 1007 </blockquote>
ohair@13 1008 <!-- ------------------------------------------------------ -->
ohair@13 1009 <h4><a name="compilers">Compilers</a></h4>
ohair@13 1010 <blockquote>
ohair@13 1011 <strong><a name="gcc">Linux gcc/binutils</a></strong>
ohair@13 1012 <blockquote>
ohair@49 1013 The GNU gcc compiler version should be 4 or newer.
ohair@13 1014 The compiler used should be the default compiler installed
ohair@13 1015 in <tt>/usr/bin</tt>.
ohair@13 1016 </blockquote>
ohair@13 1017 <strong><a name="studio">Solaris: Sun Studio</a></strong>
ohair@13 1018 <blockquote>
ohair@13 1019 At a minimum, the
ohair@211 1020 <a href="" target="_blank">
ohair@276 1021 Sun Studio 12 Update 1 Compilers</a>
ohair@211 1022 (containing version 5.10 of the C and C++ compilers) is required,
ohair@211 1023 including specific patches.
ohair@276 1024 <p>
ohair@211 1025 The Solaris SPARC patch list is:
ohair@276 1026 <ul>
ohair@276 1027 <li>
ohair@276 1028 118683-05: SunOS 5.10: Patch for profiling libraries and assembler
ohair@276 1029 </li>
ohair@276 1030 <li>
ohair@276 1031 119963-21: SunOS 5.10: Shared library patch for C++
ohair@276 1032 </li>
ohair@276 1033 <li>
ohair@276 1034 120753-08: SunOS 5.10: Microtasking libraries (libmtsk) patch
ohair@276 1035 </li>
ohair@276 1036 <li>
ohair@276 1037 128228-09: Sun Studio 12 Update 1: Patch for Sun C++ Compiler
ohair@276 1038 </li>
ohair@276 1039 <li>
ohair@276 1040 141860-03: Sun Studio 12 Update 1: Patch for Compiler Common patch for Sun C C++ F77 F95
ohair@276 1041 </li>
ohair@276 1042 <li>
ohair@276 1043 141861-05: Sun Studio 12 Update 1: Patch for Sun C Compiler
ohair@276 1044 </li>
ohair@276 1045 <li>
ohair@276 1046 142371-01: Sun Studio 12.1 Update 1: Patch for dbx
ohair@276 1047 </li>
ohair@276 1048 <li>
ohair@276 1049 143384-02: Sun Studio 12 Update 1: Patch for debuginfo handling
ohair@276 1050 </li>
ohair@276 1051 <li>
ohair@276 1052 143385-02: Sun Studio 12 Update 1: Patch for Compiler Common patch for Sun C C++ F77 F95
ohair@276 1053 </li>
ohair@276 1054 <li>
ohair@276 1055 142369-01: Sun Studio 12.1: Patch for Performance Analyzer Tools
ohair@276 1056 </li>
ohair@211 1057 </ul>
ohair@211 1058 <p>
ohair@276 1059 The Solaris X86 patch list is:
ohair@211 1060 <ul>
ohair@276 1061 <li>
ohair@276 1062 119961-07: SunOS 5.10_x86, x64, Patch for profiling libraries and assembler
ohair@276 1063 </li>
ohair@276 1064 <li>
ohair@276 1065 119964-21: SunOS 5.10_x86: Shared library patch for C++_x86
ohair@276 1066 </li>
ohair@276 1067 <li>
ohair@276 1068 120754-08: SunOS 5.10_x86: Microtasking libraries (libmtsk) patch
ohair@276 1069 </li>
ohair@276 1070 <li>
ohair@276 1071 141858-06: Sun Studio 12 Update 1_x86: Sun Compiler Common patch for x86 backend
ohair@276 1072 </li>
ohair@276 1073 <li>
ohair@276 1074 128229-09: Sun Studio 12 Update 1_x86: Patch for C++ Compiler
ohair@276 1075 </li>
ohair@276 1076 <li>
ohair@276 1077 142363-05: Sun Studio 12 Update 1_x86: Patch for C Compiler
ohair@276 1078 </li>
ohair@276 1079 <li>
ohair@276 1080 142368-01: Sun Studio 12.1_x86: Patch for Performance Analyzer Tools
ohair@276 1081 </li>
ohair@211 1082 </ul>
ohair@13 1083 <p>
ohair@276 1084 Set
ohair@276 1085 <a href="#ALT_COMPILER_PATH"><tt>ALT_COMPILER_PATH</tt></a>
ohair@276 1086 to point to the location of
ohair@276 1087 the compiler binaries, and place this location in the <tt>PATH</tt>.
ohair@13 1088 <p>
ohair@276 1089 The Oracle Solaris Studio Express compilers at:
ohair@276 1090 <a href="" target="_blank">
ohair@276 1091 Oracle Solaris Studio Express Download site</a>
ohair@276 1092 are also an option, although these compilers have not
ohair@276 1093 been extensively used yet.
ohair@13 1094 </blockquote>
prr@187 1095 <strong><a name="msvc32">Windows i586: Microsoft Visual Studio 2010 Compilers</a></strong>
ohair@13 1096 <blockquote>
ohair@276 1097 <p>
ohair@276 1098 <b>BEGIN WARNING</b>: At this time (Spring/Summer 2010) JDK 7 is starting a transition to
ohair@276 1099 use the newest VS2010 Microsoft compilers. These build instructions are updated
ohair@276 1100 to show where we are going. We have a QA process to go through before
ohair@276 1101 official builds actually use VS2010. So for now, official builds are
ohair@276 1102 still using VS2003. No other compilers are known to build the entire JDK,
ohair@276 1103 including non-open portions.
ohair@276 1104 So for now you should be able to build with either VS2003 or VS2010.
ohair@276 1105 We do not guarantee that VS2008 will work, although there is sufficient
ohair@276 1106 makefile support to make at least basic JDK builds plausible.
ohair@276 1107 Visual Studio 2010 Express compilers are now able to build all the
ohair@276 1108 open source repositories, but this is 32 bit only. To build 64 bit
ohair@276 1109 Windows binaries use the the 7.1 Windows SDK.<b>END WARNING.</b>
ohair@276 1110 <p>
ohair@276 1111 The 32-bit OpenJDK Windows build
ohair@276 1112 requires
ohair@276 1113 Microsoft Visual Studio C++ 2010 (VS2010) Professional
ohair@276 1114 Edition or Express compiler.
ohair@276 1115 The compiler and other tools are expected to reside
ohair@276 1116 in the location defined by the variable
ohair@276 1117 <tt>VS100COMNTOOLS</tt> which
ohair@276 1118 is set by the Microsoft Visual Studio installer.
ohair@13 1119 <p>
ohair@276 1120 Once the compiler is installed,
ohair@276 1121 it is recommended that you run <tt>VCVARS32.BAT</tt>
ohair@276 1122 to set the compiler environment variables
ohair@276 1123 <tt>INCLUDE</tt>,
ohair@276 1124 <tt>LIB</tt>, and
ohair@276 1125 <tt>PATH</tt>
ohair@276 1126 prior to building the
ohair@276 1127 OpenJDK.
ohair@276 1128 The above environment variables <b>MUST</b> be set.
ohair@276 1129 This compiler also contains the Windows SDK v 7.0a,
ohair@276 1130 which is an update to the Windows 7 SDK.
ohair@13 1131 <p>
ohair@276 1132 <b>WARNING:</b> Make sure you check out the
ohair@276 1133 <a href="#cygwin">CYGWIN link.exe WARNING</a>.
ohair@276 1134 The path <tt>/usr/bin</tt> must be after the path to the
ohair@276 1135 Visual Studio product.
ohair@13 1136 </blockquote>
prr@187 1137 <strong><a name="msvc64">Windows x64: Microsoft Visual Studio 2010 Professional Compiler</a></strong>
ohair@13 1138 <blockquote>
prr@187 1139 For <b>X64</b>, builds, when using the VS2010 Professional
prr@187 1140 compiler, the 64 bit build set up is much the same as 32 bit
prr@175 1141 except that you run <tt>amd64\VCVARS64.BAT</tt>
prr@175 1142 to set the compiler environment variables.
prr@187 1143 Previously 64 bit builds had used the 64 bit compiler in
prr@187 1144 an unbundled Windows SDK but this is no longer necessary if
prr@187 1145 you have VS2010 Professional.
ohair@13 1146 </blockquote>
prr@187 1147 <strong><a name="mssdk64">Windows x64: Microsoft Windows 7.1 SDK 64 bit compilers.</a></strong>
ohair@276 1148 For a free alternative for 64 bit builds, use the 7.1 SDK.
ohair@276 1149 Microsoft say that to set up your paths for this run
ohair@276 1150 <pre>
prr@187 1151 c:\Program Files\Microsoft SDKs\Windows\v7.1\bin\setenv.cmd /x64.
ohair@276 1152 </pre>
ohair@276 1153 What was tested is just directly setting up LIB, INCLUDE,
ohair@276 1154 PATH and based on the installation directories using the
ohair@276 1155 DOS short name appropriate for the system, (you will
ohair@276 1156 need to set them for yours, not just blindly copy this) eg :
ohair@276 1157 <pre>
prr@187 1158 set VSINSTALLDIR=c:\PROGRA~2\MICROS~1.0
prr@187 1159 set WindowsSdkDir=c:\PROGRA~1\MICROS~1\Windows\v7.1
prr@187 1160 set PATH=%VSINSTALLDIR%\vc\bin\amd64;%VSINSTALLDIR%\Common7\IDE;%WindowsSdkDir%\bin;%PATH%
prr@187 1161 set INCLUDE=%VSINSTALLDIR%\vc\include;%WindowsSdkDir%\include
prr@187 1162 set LIB=%VSINSTALLDIR%\vc\lib\amd64;%WindowsSdkDir%\lib\x64
ohair@276 1163 </pre>
ohair@13 1164 </blockquote>
ohair@13 1165 <!-- ------------------------------------------------------ -->
ohair@13 1166 <h4><a name="zip">Zip and Unzip</a></h4>
ohair@13 1167 <blockquote>
ohair@13 1168 Version 2.2 (November 3rd 1997) or newer of the zip utility
ohair@13 1169 and version 5.12 or newer of the unzip utility is needed
ohair@13 1170 to build the JDK.
ohair@13 1171 With Solaris, Linux, and Windows CYGWIN, the zip and unzip
ohair@13 1172 utilities installed on the system should be fine.
ohair@13 1173 Information and the source code for
ohair@13 1174 ZIP.EXE and UNZIP.EXE is available on the
ohair@13 1175 <a href=""
ohair@13 1176 target="_blank">info-zip web site</a>.
ohair@13 1177 </blockquote>
ohair@13 1178 <!-- ------------------------------------------------------ -->
ohair@13 1179 <h4><a name="cups">Common UNIX Printing System (CUPS) Headers (Solaris &amp; Linux)</a></h4>
ohair@13 1180 <blockquote>
ohair@13 1181 <strong>Solaris:</strong>
ohair@13 1182 CUPS header files are required for building the
ohair@13 1183 OpenJDK on Solaris.
ohair@13 1184 The Solaris header files can be obtained by installing
ohair@13 1185 the package <strong>SFWcups</strong> from the Solaris Software
ohair@13 1186 Companion CD/DVD, these often will be installed into
ohair@13 1187 <tt>/opt/sfw/cups</tt>.
ohair@13 1188 <p>
ohair@276 1189 <strong>Linux:</strong>
ohair@276 1190 CUPS header files are required for building the
ohair@276 1191 OpenJDK on Linux.
ohair@276 1192 The Linux header files are usually available from a "cups"
ohair@276 1193 development package, it's recommended that you try and use
ohair@276 1194 the package provided by the particular version of Linux that
ohair@276 1195 you are using.
ohair@13 1196 <p>
ohair@276 1197 The CUPS header files can always be downloaded from
ohair@276 1198 <a href="" target="_blank"></a>.
ohair@276 1199 The variable
ohair@276 1200 <tt><a href="#ALT_CUPS_HEADERS_PATH">ALT_CUPS_HEADERS_PATH</a></tt>
ohair@276 1201 can be used to override the default location of the
ohair@276 1202 CUPS Header files.
ohair@13 1203 </blockquote>
ohair@13 1204 <!-- ------------------------------------------------------ -->
andrew@90 1205 <h4><a name="xrender">XRender Extension Headers (Solaris &amp; Linux)</a></h4>
andrew@90 1206 <blockquote>
andrew@90 1207 <p>
ohair@276 1208 <strong>Solaris:</strong>
ohair@276 1209 XRender header files are required for building the
ohair@276 1210 OpenJDK on Solaris.
ohair@276 1211 The XRender header file is included with the other X11 header files
ohair@276 1212 in the package <strong>SFWxwinc</strong> on new enough versions of
ohair@276 1213 Solaris and will be installed in
ohair@276 1214 <tt>/usr/X11/include/X11/extensions/Xrender.h</tt>
andrew@90 1215 </p><p>
ohair@276 1216 <strong>Linux:</strong>
ohair@276 1217 XRender header files are required for building the
ohair@276 1218 OpenJDK on Linux.
ohair@276 1219 The Linux header files are usually available from a "Xrender"
ohair@276 1220 development package, it's recommended that you try and use
ohair@276 1221 the package provided by the particular distribution of Linux that
ohair@276 1222 you are using.
ohair@276 1223 </p>
andrew@90 1224 </blockquote>
andrew@90 1225 <!-- ------------------------------------------------------ -->
ohair@13 1226 <h4><a name="freetype">FreeType 2</a></h4>
ohair@13 1227 <blockquote>
ohair@13 1228 Version 2.3 or newer of FreeType is required for building the OpenJDK.
ohair@13 1229 On Unix systems required files can be available as part of your
ohair@13 1230 distribution (while you still may need to upgrade them).
ohair@13 1231 Note that you need development version of package that
ohair@13 1232 includes both FreeType library and header files.
ohair@13 1233 <p>
ohair@276 1234 You can always download latest FreeType version from the
ohair@276 1235 <a href="" target="_blank">FreeType website</a>.
ohair@13 1236 <p>
ohair@276 1237 Makefiles will try to pick FreeType from /usr/lib and /usr/include.
ohair@276 1238 In case it is installed elsewhere you will need to set environment
ohair@276 1239 variables
ohair@276 1240 <tt><a href="#ALT_FREETYPE_LIB_PATH">ALT_FREETYPE_LIB_PATH</a></tt>
ohair@276 1241 and
ohair@276 1242 <tt><a href="#ALT_FREETYPE_HEADERS_PATH">ALT_FREETYPE_HEADERS_PATH</a></tt>
ohair@276 1243 to refer to place where library and header files are installed.
ohair@25 1244 <p>
ohair@276 1245 Building the freetype 2 libraries from scratch is also possible,
ohair@276 1246 however on Windows refer to the
ohair@276 1247 <a href="">
ohair@276 1248 Windows FreeType DLL build instructions</a>.
ohair@25 1249 <p>
ohair@276 1250 Note that by default FreeType is built with byte code hinting
ohair@276 1251 support disabled due to licensing restrictions.
ohair@276 1252 In this case, text appearance and metrics are expected to
ohair@276 1253 differ from Sun's official JDK build.
ohair@276 1254 See
ohair@276 1255 <a href="">
ohair@276 1256 the SourceForge FreeType2 Home Page
ohair@276 1257 </a>
ohair@276 1258 for more information.
ohair@13 1259 </blockquote>
ohair@13 1260 <!-- ------------------------------------------------------ -->
ohair@13 1261 <h4><a name="alsa">Advanced Linux Sound Architecture (ALSA) (Linux only)</a></h4>
ohair@13 1262 <blockquote>
ohair@13 1263 <strong>Linux only:</strong>
ohair@13 1264 Version 0.9.1 or newer of the ALSA files are
ohair@13 1265 required for building the OpenJDK on Linux.
ohair@13 1266 These Linux files are usually available from an "alsa"
ohair@13 1267 of "libasound"
ohair@13 1268 development package, it's highly recommended that you try and use
ohair@13 1269 the package provided by the particular version of Linux that
ohair@13 1270 you are using.
ohair@13 1271 The makefiles will check this emit a sanity error if it is
ohair@13 1272 missing or the wrong version.
ohair@13 1273 <p>
ohair@276 1274 In particular, older Linux systems will likely not have the
ohair@276 1275 right version of ALSA installed, for example
ohair@276 1276 Redhat AS 2.1 U2 and SuSE 8.1 do not include a sufficiently
ohair@276 1277 recent ALSA distribution.
ohair@276 1278 On rpm-based systems, you can see if ALSA is installed by
ohair@276 1279 running this command:
ohair@13 1280 <pre>
ohair@13 1281 <tt>rpm -qa | grep alsa</tt>
ohair@13 1282 </pre>
ohair@13 1283 Both <tt>alsa</tt> and <tt>alsa-devel</tt> packages are needed.
ohair@13 1284 <p>
ohair@276 1285 If your distribution does not come with ALSA, and you can't
ohair@276 1286 find ALSA packages built for your particular system,
ohair@276 1287 you can try to install the pre-built ALSA rpm packages from
ohair@276 1288 <a href="" target="_blank">
ohair@276 1289 <tt></tt></a>.
ohair@276 1290 Note that installing a newer ALSA could
ohair@276 1291 break sound output if an older version of ALSA was previously
ohair@276 1292 installed on the system, but it will enable JDK compilation.
ohair@13 1293 <blockquote>
ohair@13 1294 Installation: execute as root<br>
ohair@13 1295 [i586]: <code>rpm -Uv --force alsa-lib-devel-0.9.1-rh61.i386.rpm</code><br>
ohair@13 1296 [x64]: <code>rpm -Uv --force alsa-lib-devel-0.9.8-amd64.x86_64.rpm</code><br>
ohair@13 1297 Uninstallation:<br>
ohair@13 1298 [i586]: <code>rpm -ev alsa-lib-devel-0.9.1-rh61</code><br>
ohair@13 1299 [x64]:<code>rpm -ev alsa-lib-devel-0.9.8-amd64</code><br>
ohair@13 1300 Make sure that you do not link to the static library
ohair@13 1301 (<tt>libasound.a</tt>),
ohair@13 1302 by verifying that the dynamic library (<tt></tt>) is
ohair@13 1303 correctly installed in <tt>/usr/lib</tt>.
ohair@13 1304 </blockquote>
ohair@13 1305 As a last resort you can go to the
ohair@13 1306 <a href="" target="_blank">
ohair@276 1307 Advanced Linux Sound Architecture Site</a> and build it from
ohair@13 1308 source.
ohair@13 1309 <blockquote>
ohair@13 1310 Download driver and library
ohair@13 1311 source tarballs from
ohair@13 1312 <a href="" target="_blank">ALSA's homepage</a>.
ohair@13 1313 As root, execute the following
ohair@13 1314 commands (you may need to adapt the version number):
ohair@13 1315 <pre>
ohair@13 1316 <tt>
ohair@13 1317 $ tar xjf alsa-driver-0.9.1.tar.bz2
ohair@13 1318 $ cd alsa-driver-0.9.1
ohair@13 1319 $ ./configure
ohair@13 1320 $ make install
ohair@13 1321 $ cd ..
ohair@13 1322 $ tar xjf alsa-lib-0.9.1.tar.bz2
ohair@13 1323 $ cd alsa-lib-0.9.1
ohair@13 1324 $ ./configure
ohair@13 1325 $ make install
ohair@13 1326 </tt>
ohair@13 1327 </pre>
ohair@13 1328 Should one of the above steps fail, refer to the documentation on
ohair@13 1329 ALSA's home page.
ohair@13 1330 </blockquote>
ohair@13 1331 Note that this is a minimum install that enables
ohair@13 1332 building the JDK platform. To actually use ALSA sound drivers, more
ohair@13 1333 steps are necessary as outlined in the documentation on ALSA's homepage.
ohair@13 1334 <p>
ohair@276 1335 ALSA can be uninstalled by executing <tt>make uninstall</tt> first in
ohair@276 1336 the <tt>alsa-lib-0.9.1</tt> directory and then in
ohair@276 1337 <tt>alsa-driver-0.9.1</tt>.
ohair@13 1338 </blockquote>
ohair@13 1339 There are no ALT* variables to change the assumed locations of ALSA,
ohair@13 1340 the makefiles will expect to find the ALSA include files and library at:
ohair@13 1341 <tt>/usr/include/alsa</tt> and <tt>/usr/lib/</tt>.
duke@2 1342 </blockquote>
ohair@13 1343 <!-- ------------------------------------------------------ -->
ohair@13 1344 <h4>Windows Specific Dependencies</h4>
duke@2 1345 <blockquote>
ohair@13 1346 <strong>Unix Command Tools (<a name="cygwin">CYGWIN</a>)</strong>
ohair@13 1347 <blockquote>
ohair@13 1348 The OpenJDK requires access to a set of unix command tools
ohair@13 1349 on Windows which can be supplied by
ohair@13 1350 <a href="" target="_blank">CYGWIN</a>.
ohair@13 1351 <p>
ohair@276 1352 The OpenJDK build requires CYGWIN version 1.5.12 or newer.
ohair@276 1353 Information about CYGWIN can
ohair@276 1354 be obtained from the CYGWIN website at
ohair@276 1355 <a href="" target="_blank"></a>.
ohair@13 1356 <p>
ohair@276 1357 By default CYGWIN doesn't install all the tools required for building
ohair@276 1358 the OpenJDK.
ohair@276 1359 Along with the default installation, you need to install
ohair@276 1360 the following tools.
ohair@13 1361 <blockquote>
ohair@13 1362 <table border="1">
ohair@13 1363 <thead>
ohair@13 1364 <tr>
ohair@13 1365 <td>Binary Name</td>
ohair@41 1366 <td>Category</td>
ohair@13 1367 <td>Package</td>
ohair@13 1368 <td>Description</td>
ohair@13 1369 </tr>
ohair@13 1370 </thead>
ohair@13 1371 <tbody>
ohair@13 1372 <tr>
ohair@13 1373 <td>ar.exe</td>
ohair@13 1374 <td>Devel</td>
ohair@41 1375 <td>binutils</td>
ohair@41 1376 <td>The GNU assembler, linker and binary
ohair@276 1377 utilities</td>
ohair@13 1378 </tr>
ohair@13 1379 <tr>
ohair@13 1380 <td>make.exe</td>
ohair@13 1381 <td>Devel</td>
ohair@41 1382 <td>make</td>
ohair@41 1383 <td>The GNU version of the 'make' utility built for CYGWIN.<br>
ohair@276 1384 <b>NOTE</b>: See <a href="#gmake">the GNU make section</a></td>
ohair@13 1385 </tr>
ohair@13 1386 <tr>
ohair@13 1387 <td>m4.exe</td>
ohair@13 1388 <td>Interpreters</td>
ohair@41 1389 <td>m4</td>
ohair@41 1390 <td>GNU implementation of the traditional Unix macro
ohair@276 1391 processor</td>
ohair@13 1392 </tr>
ohair@13 1393 <tr>
ohair@13 1394 <td>cpio.exe</td>
ohair@13 1395 <td>Utils</td>
ohair@41 1396 <td>cpio</td>
ohair@41 1397 <td>A program to manage archives of files</td>
ohair@13 1398 </tr>
ohair@13 1399 <tr>
ohair@25 1400 <td>gawk.exe</td>
ohair@13 1401 <td>Utils</td>
ohair@41 1402 <td>awk</td>
ohair@41 1403 <td>Pattern-directed scanning and processing language</td>
ohair@13 1404 </tr>
ohair@13 1405 <tr>
ohair@13 1406 <td>file.exe</td>
ohair@13 1407 <td>Utils</td>
ohair@41 1408 <td>file</td>
ohair@41 1409 <td>Determines file type using 'magic' numbers</td>
ohair@13 1410 </tr>
ohair@13 1411 <tr>
ohair@13 1412 <td>zip.exe</td>
ohair@25 1413 <td>Archive</td>
ohair@41 1414 <td>zip</td>
ohair@41 1415 <td>Package and compress (archive) files</td>
ohair@13 1416 </tr>
ohair@13 1417 <tr>
ohair@13 1418 <td>unzip.exe</td>
ohair@25 1419 <td>Archive</td>
ohair@41 1420 <td>unzip</td>
ohair@41 1421 <td>Extract compressed files in a ZIP archive</td>
ohair@13 1422 </tr>
ohair@13 1423 <tr>
ohair@13 1424 <td>free.exe</td>
ohair@41 1425 <td>System</td>
ohair@41 1426 <td>procps</td>
ohair@41 1427 <td>Display amount of free and used memory in the system</td>
ohair@13 1428 </tr>
ohair@13 1429 </tbody>
ohair@13 1430 </table>
ohair@13 1431 </blockquote>
ohair@13 1432 <p>
ohair@276 1433 Note that the CYGWIN software can conflict with other non-CYGWIN
ohair@276 1434 software on your Windows system.
ohair@276 1435 CYGWIN provides a
ohair@276 1436 <a href="" target="_blank">FAQ</a> for
ohair@276 1437 known issues and problems, of particular interest is the
ohair@276 1438 section on
ohair@276 1439 <a href="" target="_blank">
ohair@276 1440 BLODA (applications that interfere with CYGWIN)</a>.
ohair@41 1441 <p>
ohair@276 1442 <b>WARNING:</b>
ohair@276 1443 Be very careful with <b><tt>link.exe</tt></b>, it will conflict
ohair@276 1444 with the Visual Studio version. You need the Visual Studio
ohair@276 1445 version of <tt>link.exe</tt>, not the CYGWIN one.
ohair@276 1446 So it's important that the Visual Studio paths in PATH preceed
ohair@276 1447 the CYGWIN path <tt>/usr/bin</tt>.
ohair@13 1448 </blockquote>
ohair@13 1449 <strong><a name="dxsdk">Microsoft DirectX 9.0 SDK header files and libraries</a></strong>
duke@2 1450 <blockquote>
ohair@13 1451 Microsoft DirectX 9.0 SDK (Summer 2004)
ohair@13 1452 headers are required for building
ohair@13 1453 OpenJDK.
ohair@13 1454 This SDK can be downloaded from
ohair@13 1455 <a href=";displaylang=en" target="_blank">
ohair@276 1456 Microsoft DirectX 9.0 SDK (Summer 2004)</a>.
ohair@13 1457 If the link above becomes obsolete, the SDK can be found from
ohair@13 1458 <a href="" target="_blank">the Microsoft Download Site</a>
ohair@13 1459 (search with "DirectX 9.0 SDK Update Summer 2004").
ohair@13 1460 The location of this SDK can be set with
ohair@13 1461 <tt><a href="#ALT_DXSDK_PATH">ALT_DXSDK_PATH</a></tt>
ohair@13 1462 but it's normally found via the DirectX environment variable
ohair@13 1463 <tt>DXSDK_DIR</tt>.
ohair@13 1464 </blockquote>
prr@175 1465 <strong><a name="msvcrt"><tt>MSVCR100.DLL</tt></a></strong>
ohair@13 1466 <blockquote>
prr@175 1467 The OpenJDK build requires access to a redistributable
prr@175 1468 <tt>MSVCR100.DLL</tt>.
prr@175 1469 This is usually picked up automatically from the redist
prr@175 1470 directories of Visual Studio 2010.
prr@175 1471 If this cannot be found set the
ohair@13 1472 <a href="#ALT_MSVCRT_DLL_PATH"><tt>ALT_MSVCRT_DLL_PATH</tt></a>
ohair@49 1473 variable to the location of this file.
ohair@13 1474 <p>
duke@2 1475 </blockquote>
duke@2 1476 </blockquote>
ohair@13 1477 <!-- ------------------------------------------------------ -->
ohair@13 1478 <hr>
ohair@13 1479 <h2><a name="creating">Creating the Build</a></h2>
duke@2 1480 <blockquote>
ohair@13 1481 Once a machine is setup to build the OpenJDK,
ohair@13 1482 the steps to create the build are fairly simple.
ohair@13 1483 The various ALT settings can either be made into variables
ohair@13 1484 or can be supplied on the
ohair@13 1485 <a href="#gmake"><tt><i>gmake</i></tt></a>
ohair@13 1486 command.
ohair@13 1487 <ol>
ohair@13 1488 <li>Use the sanity rule to double check all the ALT settings:
ohair@13 1489 <blockquote>
ohair@13 1490 <tt>
ohair@13 1491 <i>gmake</i>
ohair@13 1492 sanity
ohair@13 1493 [ARCH_DATA_MODEL=<i>32 or 64</i>]
ohair@13 1494 [other "ALT_" overrides]
ohair@13 1495 </tt>
ohair@13 1496 </blockquote>
ohair@13 1497 </li>
ohair@13 1498 <li>Start the build with the command:
ohair@13 1499 <blockquote>
ohair@13 1500 <tt>
ohair@13 1501 <i>gmake</i>
ohair@13 1502 [ARCH_DATA_MODEL=<i>32 or 64</i>]
ohair@13 1503 [ALT_OUTPUTDIR=<i>output_directory</i>]
ohair@13 1504 [other "ALT_" overrides]
ohair@13 1505 </tt>
ohair@13 1506 </blockquote>
ohair@13 1507 </li>
ohair@13 1508 </ol>
duke@2 1509 <p>
ohair@276 1510 <strong>Solaris:</strong>
ohair@276 1511 Note that ARCH_DATA_MODEL is really only needed on Solaris to
ohair@276 1512 indicate you want to built the 64-bit version.
ohair@276 1513 And before the Solaris 64-bit binaries can be used, they
ohair@276 1514 must be merged with the binaries from a separate 32-bit build.
ohair@276 1515 The merged binaries may then be used in either 32-bit or 64-bit mode, with
ohair@276 1516 the selection occurring at runtime
ohair@276 1517 with the <tt>-d32</tt> or <tt>-d64</tt> options.
duke@2 1518 </blockquote>
ohair@13 1519 <!-- ------------------------------------------------------ -->
ohair@13 1520 <hr>
ohair@13 1521 <h2><a name="testing">Testing the Build</a></h2>
ohair@13 1522 <blockquote>
ohair@13 1523 When the build is completed, you should see the generated
ohair@13 1524 binaries and associated files in the <tt>j2sdk-image</tt>
ohair@13 1525 directory in the output directory.
ohair@13 1526 The default output directory is
ohair@13 1527 <tt>build/<i>platform</i></tt>,
ohair@13 1528 where <tt><i>platform</i></tt> is one of
ohair@276 1529 <blockquote>
ohair@276 1530 <ul>
ohair@276 1531 <li><tt>solaris-sparc</tt></li>
ohair@276 1532 <li><tt>solaris-sparcv9</tt></li>
ohair@276 1533 <li><tt>solaris-i586</tt></li>
ohair@276 1534 <li><tt>solaris-amd64</tt></li>
ohair@276 1535 <li><tt>linux-i586</tt></li>
ohair@276 1536 <li><tt>linux-amd64</tt></li>
ohair@276 1537 <li><tt>windows-i586</tt></li>
ohair@276 1538 <li><tt>windows-amd64</tt></li>
ohair@276 1539 </ul>
ohair@276 1540 </blockquote>
ohair@13 1541 In particular, the
ohair@13 1542 <tt>build/<i>platform</i>/j2sdk-image/bin</tt>
ohair@13 1543 directory should contain executables for the
ohair@13 1544 OpenJDK tools and utilities.
duke@2 1545 <p>
ohair@276 1546 You can test that the build completed properly by using the build
ohair@276 1547 to run the various demos that you will find in the
ohair@276 1548 <tt>build/<i>platform</i>/j2sdk-image/demo</tt>
ohair@276 1549 directory.
ohair@13 1550 <p>
ohair@276 1551 The provided regression tests can be run with the <tt>jtreg</tt>
ohair@276 1552 utility from
ohair@276 1553 <a href="" target="_blank">the jtreg site</a>.
duke@2 1554 </blockquote>
ohair@13 1555 <!-- ------------------------------------------------------ -->
ohair@13 1556 <hr>
ohair@13 1557 <h2><a name="variables">Environment/Make Variables</a></h2>
ohair@13 1558 <p>
ohair@276 1559 Some of the
ohair@276 1560 environment or make variables (just called <b>variables</b> in this
ohair@276 1561 document) that can impact the build are:
duke@2 1562 <blockquote>
duke@2 1563 <dl>
ohair@49 1564 <dt><a name="path"><tt>PATH</tt></a> </dt>
ohair@49 1565 <dd>Typically you want to set the <tt>PATH</tt> to include:
ohair@49 1566 <ul>
ohair@49 1567 <li>The location of the GNU make binary</li>
ohair@49 1568 <li>The location of the Bootstrap JDK <tt>java</tt>
ohair@276 1569 (see <a href="#bootjdk">Bootstrap JDK</a>)</li>
ohair@49 1570 <li>The location of the C/C++ compilers
ohair@276 1571 (see <a href="#compilers"><tt>compilers</tt></a>)</li>
ohair@49 1572 <li>The location or locations for the Unix command utilities
ohair@276 1573 (e.g. <tt>/usr/bin</tt>)</li>
ohair@49 1574 </ul>
ohair@49 1575 </dd>
ohair@49 1576 <dt><tt>MILESTONE</tt> </dt>
ohair@49 1577 <dd>
ohair@49 1578 The milestone name for the build (<i>e.g.</i>"beta").
ohair@49 1579 The default value is "internal".
ohair@49 1580 </dd>
ohair@49 1581 <dt><tt>BUILD_NUMBER</tt> </dt>
ohair@49 1582 <dd>
ohair@49 1583 The build number for the build (<i>e.g.</i> "b27").
ohair@49 1584 The default value is "b00".
ohair@49 1585 </dd>
ohair@49 1586 <dt><a name="arch_data_model"><tt>ARCH_DATA_MODEL</tt></a></dt>
ohair@49 1587 <dd>The <tt>ARCH_DATA_MODEL</tt> variable
ohair@49 1588 is used to specify whether the build is to generate 32-bit or 64-bit
ohair@49 1589 binaries.
ohair@49 1590 The Solaris build supports either 32-bit or 64-bit builds, but
ohair@49 1591 Windows and Linux will support only one, depending on the specific
ohair@49 1592 OS being used.
ohair@49 1593 Normally, setting this variable is only necessary on Solaris.
ohair@49 1594 Set <tt>ARCH_DATA_MODEL</tt> to <tt>32</tt> for generating 32-bit binaries,
ohair@49 1595 or to <tt>64</tt> for generating 64-bit binaries.
ohair@49 1596 </dd>
ohair@49 1597 <dt><a name="ALT_BOOTDIR"><tt>ALT_BOOTDIR</tt></a></dt>
ohair@49 1598 <dd>
ohair@49 1599 The location of the bootstrap JDK installation.
ohair@49 1600 See <a href="#bootjdk">Bootstrap JDK</a> for more information.
ohair@49 1601 You should always install your own local Bootstrap JDK and
ohair@49 1602 always set <tt>ALT_BOOTDIR</tt> explicitly.
ohair@49 1603 </dd>
ohair@25 1604 <dt><a name="ALT_BINARY_PLUGS_PATH"><tt>ALT_BINARY_PLUGS_PATH</tt></a></dt>
duke@2 1605 <dd>
ohair@25 1606 The location of the binary plugs installation.
ohair@25 1607 See <a href="#binaryplugs">Binary Plugs</a> for more information.
ohair@25 1608 You should always have a local copy of a
ohair@25 1609 recent Binary Plugs install image
ohair@25 1610 and set this variable to that location.
ohair@13 1611 </dd>
ohair@49 1612 <dt><a name="ALT_JDK_IMPORT_PATH"><tt>ALT_JDK_IMPORT_PATH</tt></a></dt>
duke@2 1613 <dd>
ohair@49 1614 The location of a previously built JDK installation.
ohair@49 1615 See <a href="#importjdk">Optional Import JDK</a> for more information.
ohair@49 1616 </dd>
ohair@49 1617 <dt><a name="ALT_OUTPUTDIR"><tt>ALT_OUTPUTDIR</tt></a> </dt>
ohair@49 1618 <dd>
ohair@49 1619 An override for specifying the (absolute) path of where the
ohair@49 1620 build output is to go.
ohair@49 1621 The default output directory will be build/<i>platform</i>.
ohair@49 1622 </dd>
ohair@49 1623 <dt><a name="ALT_COMPILER_PATH"><tt>ALT_COMPILER_PATH</tt></a> </dt>
ohair@49 1624 <dd>
ohair@49 1625 The location of the C/C++ compiler.
ohair@49 1626 The default varies depending on the platform.
ohair@49 1627 </dd>
ohair@49 1628 <dt><tt><a name="ALT_CACERTS_FILE">ALT_CACERTS_FILE</a></tt></dt>
ohair@49 1629 <dd>
ohair@49 1630 The location of the <a href="#cacerts">cacerts</a> file.
ohair@49 1631 The default will refer to
ohair@49 1632 <tt>jdk/src/share/lib/security/cacerts</tt>.
ohair@49 1633 </dd>
ohair@49 1634 <dt><a name="ALT_CUPS_HEADERS_PATH"><tt>ALT_CUPS_HEADERS_PATH</tt></a> </dt>
ohair@49 1635 <dd>
ohair@49 1636 The location of the CUPS header files.
ohair@49 1637 See <a href="#cups">CUPS information</a> for more information.
ohair@49 1638 If this path does not exist the fallback path is
ohair@49 1639 <tt>/usr/include</tt>.
ohair@49 1640 </dd>
ohair@49 1641 <dt><a name="ALT_FREETYPE_LIB_PATH"><tt>ALT_FREETYPE_LIB_PATH</tt></a></dt>
ohair@49 1642 <dd>
ohair@49 1643 The location of the FreeType shared library.
ohair@49 1644 See <a href="#freetype">FreeType information</a> for details.
ohair@49 1645 </dd>
ohair@49 1646 <dt><a name="ALT_FREETYPE_HEADERS_PATH"><tt>ALT_FREETYPE_HEADERS_PATH</tt></a></dt>
ohair@49 1647 <dd>
ohair@49 1648 The location of the FreeType header files.
ohair@49 1649 See <a href="#freetype">FreeType information</a> for details.
ohair@49 1650 </dd>
ohair@49 1651 <dt><a name="ALT_JDK_DEVTOOLS_PATH"><tt>ALT_JDK_DEVTOOLS_PATH</tt></a></dt>
ohair@49 1652 <dd>
ohair@49 1653 The default root location of the devtools.
ohair@49 1654 The default value is
ohair@49 1655 <tt>$(ALT_SLASH_JAVA)/devtools</tt>.
ohair@49 1656 </dd>
ohair@49 1657 <dt><tt><a name="ALT_DEVTOOLS_PATH">ALT_DEVTOOLS_PATH</a></tt> </dt>
ohair@49 1658 <dd>
ohair@49 1659 The location of tools like the
ohair@49 1660 <a href="#zip"><tt>zip</tt> and <tt>unzip</tt></a>
ohair@49 1661 binaries, but might also contain the GNU make utility
ohair@49 1662 (<tt><i>gmake</i></tt>).
ohair@49 1663 So this area is a bit of a grab bag, especially on Windows.
ohair@49 1664 The default value depends on the platform and
ohair@49 1665 Unix Commands being used.
ohair@49 1666 On Linux the default will be
ohair@49 1667 <tt>$(ALT_JDK_DEVTOOLS_PATH)/linux/bin</tt>,
ohair@49 1668 on Solaris
ohair@49 1669 <tt>$(ALT_JDK_DEVTOOLS_PATH)/<i>{sparc,i386}</i>/bin</tt>,
ohair@49 1670 and on Windows with CYGWIN
ohair@49 1671 <tt>/usr/bin</tt>.
ohair@49 1672 </dd>
ohair@49 1673 <dt><a name="ALT_UNIXCCS_PATH"><tt>ALT_UNIXCCS_PATH</tt></a></dt>
ohair@49 1674 <dd>
ohair@49 1675 <strong>Solaris only:</strong>
ohair@49 1676 An override for specifying where the Unix CCS
ohair@49 1677 command set are located.
ohair@49 1678 The default location is <tt>/usr/ccs/bin</tt>
ohair@49 1679 </dd>
ohair@49 1680 <dt><a name="ALT_SLASH_JAVA"><tt>ALT_SLASH_JAVA</tt></a></dt>
ohair@49 1681 <dd>
ohair@49 1682 The default root location for many of the ALT path locations
ohair@49 1683 of the following ALT variables.
ohair@49 1684 The default value is
ohair@49 1685 <tt>"/java"</tt> on Solaris and Linux,
ohair@49 1686 <tt>"J:"</tt> on Windows.
ohair@49 1687 </dd>
ohair@49 1688 <dt><a name="ALT_BUILD_JDK_IMPORT_PATH"><tt>ALT_BUILD_JDK_IMPORT_PATH</tt></a></dt>
ohair@49 1689 <dd>
ohair@49 1690 These are useful in managing builds on multiple platforms.
ohair@49 1691 The default network location for all of the import JDK images
ohair@49 1692 for all platforms.
ohair@49 1693 If <tt><a href="#ALT_JDK_IMPORT_PATH">ALT_JDK_IMPORT_PATH</a></tt>
ohair@49 1694 is not set, this directory will be used and should contain
ohair@49 1695 the following directories:
ohair@49 1696 <tt>solaris-sparc</tt>,
ohair@49 1697 <tt>solaris-i586</tt>,
ohair@49 1698 <tt>solaris-sparcv9</tt>,
ohair@49 1699 <tt>solaris-amd64</tt>,
ohair@49 1700 <tt>linux-i586</tt>,
ohair@49 1701 <tt>linux-amd64</tt>,
ohair@49 1702 <tt>windows-i586</tt>,
ohair@49 1703 and
ohair@49 1704 <tt>windows-amd64</tt>.
ohair@49 1705 Where each of these directories contain the import JDK image
ohair@49 1706 for that platform.
duke@2 1707 </dd>
ohair@25 1708 <dt><a name="ALT_BUILD_BINARY_PLUGS_PATH"><tt>ALT_BUILD_BINARY_PLUGS_PATH</tt></a></dt>
duke@2 1709 <dd>
ohair@25 1710 These are useful in managing builds on multiple platforms.
ohair@25 1711 The default network location for all of the binary plug images
ohair@25 1712 for all platforms.
ohair@25 1713 If <tt><a href="#ALT_BINARY_PLUGS_PATH">ALT_BINARY_PLUGS_PATH</a></tt>
ohair@25 1714 is not set, this directory will be used and should contain
ohair@25 1715 the following directories:
ohair@25 1716 <tt>solaris-sparc</tt>,
ohair@25 1717 <tt>solaris-i586</tt>,
ohair@25 1718 <tt>solaris-sparcv9</tt>,
ohair@25 1719 <tt>solaris-amd64</tt>,
ohair@25 1720 <tt>linux-i586</tt>,
ohair@25 1721 <tt>linux-amd64</tt>,
ohair@25 1722 <tt>windows-i586</tt>,
ohair@25 1723 and
ohair@25 1724 <tt>windows-amd64</tt>.
ohair@25 1725 Where each of these directories contain the binary plugs image
ohair@25 1726 for that platform.
ohair@13 1727 </dd>
ohair@49 1728 <dt><strong>Windows specific:</strong></dt>
ohair@13 1729 <dd>
ohair@49 1730 <dl>
ohair@49 1731 <dt><a name="ALT_MSDEVTOOLS_PATH"><tt>ALT_MSDEVTOOLS_PATH</tt></a> </dt>
ohair@49 1732 <dd>
ohair@49 1733 The location of the
ohair@49 1734 Microsoft Visual Studio
ohair@49 1735 tools 'bin' directory.
ohair@49 1736 The default is usually derived from
ohair@49 1737 <a href="#ALT_COMPILER_PATH"><tt>ALT_COMPILER_PATH</tt></a>.
ohair@49 1738 </dd>
ohair@49 1739 <dt><tt><a name="ALT_DXSDK_PATH">ALT_DXSDK_PATH</a></tt> </dt>
ohair@49 1740 <dd>
ohair@49 1741 The location of the
ohair@49 1742 <a href="#dxsdk">Microsoft DirectX 9 SDK</a>.
ohair@49 1743 The default will be to try and use the DirectX environment
ohair@49 1744 variable <tt>DXSDK_DIR</tt>,
ohair@49 1745 failing that, look in <tt>C:/DXSDK</tt>.
ohair@49 1746 </dd>
ohair@49 1747 <dt><tt><a name="ALT_MSVCRT_DLL_PATH">ALT_MSVCRT_DLL_PATH</a></tt> </dt>
ohair@49 1748 <dd>
ohair@49 1749 The location of the
ohair@49 1750 <a href="#msvcrt"><tt>MSVCRT.DLL</tt></a>.
ohair@49 1751 </dd>
prr@175 1752 <dt><tt><a name="ALT_MSVCRNN_DLL_PATH">ALT_MSVCRNN_DLL_PATH</a></tt> </dt>
ohair@49 1753 <dd>
ohair@49 1754 The location of the
prr@175 1755 <a href="#msvcrt"><tt>MSVCR100.DLL</tt></a>.
ohair@49 1756 </dd>
ohair@49 1757 </dl>
duke@2 1758 </dd>
duke@2 1759 </dl>
ohair@13 1760 </blockquote>
ohair@13 1761 <!-- ------------------------------------------------------ -->
ohair@13 1762 <hr>
ohair@13 1763 <h2><a name="troubleshooting">Troubleshooting</a></h2>
ohair@13 1764 <blockquote>
ohair@13 1765 A build can fail for any number of reasons.
ohair@13 1766 Most failures
ohair@13 1767 are a result of trying to build in an environment in which all the
ohair@13 1768 pre-build requirements have not been met.
ohair@13 1769 The first step in
ohair@13 1770 troubleshooting a build failure is to recheck that you have satisfied
ohair@13 1771 all the pre-build requirements for your platform.
ohair@13 1772 Look for the check list of the platform you are building on in the
ohair@13 1773 <a href="#contents">Table of Contents</a>.
ohair@13 1774 <p>
ohair@276 1775 You can validate your build environment by using the <tt>sanity</tt>
ohair@276 1776 target.
ohair@276 1777 Any errors listed
ohair@276 1778 will stop the build from starting, and any warnings may result in
ohair@276 1779 a flawed product build.
ohair@276 1780 We strongly encourage you to evaluate every
ohair@276 1781 sanity check warning and fix it if required, before you proceed
ohair@276 1782 further with your build.
ohair@13 1783 <p>
ohair@276 1784 Some of the more common problems with builds are briefly described
ohair@276 1785 below, with suggestions for remedies.
ohair@13 1786 <ul>
ohair@13 1787 <li>
ohair@13 1788 <b>Slow Builds:</b>
ohair@13 1789 <blockquote>
ohair@13 1790 If your build machine seems to be overloaded from too many
ohair@13 1791 simultaneous C++ compiles, try setting the <tt>HOTSPOT_BUILD_JOBS</tt>
ohair@13 1792 variable to <tt>1</tt> (if you're using a multiple CPU
ohair@13 1793 machine, setting it to more than the the number of CPUs is probably
ohair@13 1794 not a good idea).
ohair@13 1795 <p>
ohair@276 1796 Creating the javadocs can be very slow, if you are running
ohair@276 1797 javadoc, consider skipping that step.
ohair@13 1798 <p>
ohair@276 1799 Faster hardware and more RAM always helps too.
ohair@276 1800 The VM build tends to be CPU intensive (many C++ compiles),
ohair@276 1801 and the rest of the JDK will often be disk intensive.
ohair@13 1802 <p>
ohair@276 1803 Faster compiles are possible using a tool called
ohair@276 1804 <a href="" target="_blank">ccache</a>.
ohair@13 1805 </blockquote>
ohair@13 1806 </li>
ohair@13 1807 <li>
ohair@13 1808 <b>File time issues:</b>
ohair@13 1809 <blockquote>
ohair@13 1810 If you see warnings that refer to file time stamps, e.g.
ohair@13 1811 <blockquote>
ohair@13 1812 <i>Warning message:</i><tt> File `xxx' has modification time in
ohair@276 1813 the future.</tt>
ohair@13 1814 <br>
ohair@13 1815 <i>Warning message:</i> <tt> Clock skew detected. Your build may
ohair@276 1816 be incomplete.</tt>
ohair@13 1817 </blockquote>
ohair@13 1818 These warnings can occur when the clock on the build machine is out of
ohair@13 1819 sync with the timestamps on the source files. Other errors, apparently
ohair@13 1820 unrelated but in fact caused by the clock skew, can occur along with
ohair@13 1821 the clock skew warnings. These secondary errors may tend to obscure the
ohair@13 1822 fact that the true root cause of the problem is an out-of-sync clock.
ohair@13 1823 For example, an out-of-sync clock has been known to cause an old
ohair@13 1824 version of javac to be used to compile some files, resulting in errors
ohair@13 1825 when the pre-1.4 compiler ran across the new <tt>assert</tt> keyword
ohair@13 1826 in the 1.4 source code.
ohair@13 1827 <p>
ohair@276 1828 If you see these warnings, reset the clock on the build
ohair@276 1829 machine, run "<tt><i>gmake</i> clobber</tt>" or delete the directory
ohair@276 1830 containing the build output, and restart the build from the beginning.
ohair@13 1831 </blockquote>
ohair@13 1832 </li>
ohair@13 1833 <li>
ohair@13 1834 <b>Error message: <tt>Trouble writing out table to disk</tt></b>
ohair@13 1835 <blockquote>
ohair@13 1836 Increase the amount of swap space on your build machine.
ohair@13 1837 </blockquote>
ohair@13 1838 </li>
ohair@13 1839 <li>
ohair@13 1840 <b>Error Message: <tt>libstdc++ not found:</tt></b>
ohair@13 1841 <blockquote>
ohair@13 1842 This is caused by a missing libstdc++.a library.
ohair@13 1843 This is installed as part of a specific package
ohair@13 1844 (e.g.
ohair@49 1845 By default some 64-bit Linux versions (e.g. Fedora)
ohair@49 1846 only install the 64-bit version of the libstdc++ package.
ohair@13 1847 Various parts of the JDK build require a static
ohair@13 1848 link of the C++ runtime libraries to allow for maximum
ohair@13 1849 portability of the built images.
ohair@13 1850 </blockquote>
ohair@13 1851 </li>
ohair@13 1852 <li>
ohair@13 1853 <b>Error Message: <tt>cannot restore segment prot after reloc</tt></b>
ohair@13 1854 <blockquote>
ohair@13 1855 This is probably an issue with SELinux (See
ohair@13 1856 <a href="" target="_blank">
ohair@276 1857</a>).
ohair@13 1858 Parts of the VM is built without the <tt>-fPIC</tt> for
ohair@13 1859 performance reasons.
ohair@13 1860 <p>
ohair@276 1861 To completely disable SELinux:
ohair@276 1862 <ol>
ohair@276 1863 <li><tt>$ su root</tt></li>
ohair@276 1864 <li><tt># system-config-securitylevel</tt></li>
ohair@276 1865 <li><tt>In the window that appears, select the SELinux tab</tt></li>
ohair@276 1866 <li><tt>Disable SELinux</tt></li>
ohair@276 1867 </ol>
ohair@13 1868 <p>
ohair@276 1869 Alternatively, instead of completely disabling it you could
ohair@276 1870 disable just this one check.
ohair@276 1871 <ol>
ohair@276 1872 <li>Select System->Administration->SELinux Management</li>
ohair@276 1873 <li>In the SELinux Management Tool which appears,
ohair@13 1874 select "Boolean" from the menu on the left</li>
ohair@276 1875 <li>Expand the "Memory Protection" group</li>
ohair@276 1876 <li>Check the first item, labeled
ohair@13 1877 "Allow all unconfined executables to use libraries requiring text relocation ..."</li>
ohair@276 1878 </ol>
ohair@13 1879 </blockquote>
ohair@13 1880 </li>
ohair@13 1881 <li>
ohair@13 1882 <b>Windows Error Message: <tt>*** fatal error - couldn't allocate heap, ... </tt></b>
ohair@13 1883 <blockquote>
ohair@13 1884 The CYGWIN software can conflict with other non-CYGWIN
ohair@13 1885 software. See the CYGWIN FAQ section on
ohair@13 1886 <a href="" target="_blank">
ohair@276 1887 BLODA (applications that interfere with CYGWIN)</a>.
ohair@13 1888 </blockquote>
ohair@13 1889 </li>
ohair@13 1890 <li>
ohair@13 1891 <b>Windows Error Message: <tt>*** multiple target patterns. Stop.</tt></b>
ohair@13 1892 <blockquote>
ohair@13 1893 The CYGWIN make version 3.81 may not like the Windows <tt>C:/</tt>
ohair@13 1894 style paths, it may not like the ':' character in the path
ohair@13 1895 when used in a makefile target definition.
ohair@13 1896 See the <a href="#gmake"><tt><i>gmake</i></tt></a> section.
ohair@13 1897 </blockquote>
ohair@13 1898 </li>
ohair@13 1899 </ul>
ohair@13 1900 </blockquote>
ohair@13 1901 <hr>
ohair@13 1902 </body>
ohair@13 1903 </html>