Sat, 18 Dec 2010 18:28:31 -0800

Sat, 18 Dec 2010 18:28:31 -0800
changeset 262
parent 211
child 275
child 276

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