Wed, 30 Apr 2008 19:35:26 -0700

Wed, 30 Apr 2008 19:35:26 -0700
changeset 13
parent 5
child 25
child 30

6563616: Clarify instructions for unpacking openjdk binary "plug"
6611685: Incorrect link to CA certs info from build README
6682167: Add cygwin faq to README-builds.html
Reviewed-by: xdono

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@13 8 <table width="100%" style="background-color:white">
ohair@13 9 <tr>
ohair@13 10 <td align="center">
ohair@13 11 <a href="" border="0">
ohair@13 12 <img alt="OpenJDK"
ohair@13 13 src=""
ohair@13 14 width=256
ohair@13 15 style="border-style: none"/>
ohair@13 16 </a>
ohair@13 17 </td>
ohair@13 18 </tr>
ohair@13 19 <tr>
ohair@13 20 <td align=center>
ohair@13 21 <h1>OpenJDK Build README</h1>
ohair@13 22 </td>
ohair@13 23 </tr>
ohair@13 24 </table>
ohair@13 25 <!-- ------------------------------------------------------ -->
ohair@13 26 <hr>
ohair@13 27 <h2><a name="introduction">Introduction</a></h2>
ohair@13 28 <blockquote>
ohair@13 29 <p>
ohair@13 30 This README file contains build instructions for the
ohair@13 31 <a href="" target="_blank">OpenJDK</a>.
ohair@13 32 Building the source code for the
ohair@13 33 OpenJDK
ohair@13 34 requires
ohair@13 35 a certain degree of technical expertise.
ohair@13 36 </blockquote>
ohair@13 37 <!-- ------------------------------------------------------ -->
ohair@13 38 <hr>
ohair@13 39 <h2><a name="contents">Contents</a></h2>
ohair@13 40 <blockquote>
ohair@13 41 <ul>
ohair@13 42 <li><a href="#introduction">Introduction</a></li>
ohair@13 43 <li><a href="#MBE">Minimum Build Environments</a></li>
ohair@13 44 <li><a href="#SDBE">Specific Developer Build Environments</a></li>
ohair@13 45 <li><a href="#directories">Source Directory Structure</a> </li>
ohair@13 46 <li><a href="#building">Build Information</a>
ohair@13 47 <ul>
ohair@13 48 <li><a href="#gmake">GNU Make (<tt><i>gmake</i></tt>)</a> </li>
ohair@13 49 <li><a href="#linux">Basic Linux System Setup</a> </li>
ohair@13 50 <li><a href="#solaris">Basic Solaris System Setup</a> </li>
ohair@13 51 <li><a href="#windows">Basic Windows System Setup</a> </li>
ohair@13 52 <li><a href="#dependencies">Build Dependencies</a> </li>
duke@2 53 <ul>
ohair@13 54 <li><a href="#bootjdk">Bootstrap JDK</a> </li>
ohair@13 55 <li><a href="#binaryplugs">Binary Plugs</a> </li>
ohair@13 56 <li><a href="#importjdk">Optional Import JDK</a> </li>
ohair@13 57 <li><a href="#cacerts">Certificate Authority File (cacert)</a> </li>
ohair@13 58 <li><a href="#compilers">Compilers</a>
ohair@13 59 <ul>
ohair@13 60 <li><a href="#msvc">Microsoft Visual Studio</a> </li>
ohair@13 61 <li><a href="#mssdk">Microsoft Platform SDK</a> </li>
ohair@13 62 <li><a href="#gcc">Linux gcc/binutils</a> </li>
ohair@13 63 <li><a href="#studio">Sun Studio</a> </li>
ohair@13 64 </ul>
ohair@13 65 </li>
ohair@13 66 <li><a href="#zip">Zip and Unzip</a> </li>
ohair@13 67 <li><a href="#freetype">FreeType2 Fonts</a> </li>
ohair@13 68 <li>Linux and Solaris:
ohair@13 69 <ul>
ohair@13 70 <li><a href="#cups">CUPS Include files</a> </li>
ohair@13 71 </ul>
ohair@13 72 </li>
ohair@13 73 <li>Linux only:
ohair@13 74 <ul>
ohair@13 75 <li><a href="#alsa">ALSA files</a> </li>
ohair@13 76 </ul>
ohair@13 77 </li>
ohair@13 78 <li>Windows only:
ohair@13 79 <ul>
ohair@13 80 <li>Unix Command Tools (<a href="#cygwin">CYGWIN</a>)</li>
ohair@13 81 <li><a href="#dxsdk">DirectX 9.0 SDK</a> </li>
ohair@13 82 </ul>
ohair@13 83 </li>
duke@2 84 </ul>
ohair@13 85 </ul>
ohair@13 86 </li>
ohair@13 87 <li><a href="#creating">Creating the Build</a> </li>
ohair@13 88 <li><a href="#testing">Testing the Build</a> </li>
ohair@13 89 <li><a href="#variables">Environment/Make Variables</a></li>
ohair@13 90 <li><a href="#troubleshooting">Troubleshooting</a></li>
ohair@13 91 </ul>
ohair@13 92 </blockquote>
ohair@13 93 <!-- ------------------------------------------------------ -->
ohair@13 94 <hr>
ohair@13 95 <h2><a name="MBE">Minimum Build Environments</a></h2>
ohair@13 96 <blockquote>
ohair@13 97 This file often describes specific requirements for what we call the
ohair@13 98 "minimum build environments" (MBE) for the JDK.
ohair@13 99 Building with the MBE will generate the most compatible
ohair@13 100 bits that install on, and run correctly on, the most variations
ohair@13 101 of the same base OS and hardware architecture.
ohair@13 102 These usually represent what is often called the
ohair@13 103 least common denominator platforms.
ohair@13 104 It is understood that most developers will NOT be using these
ohair@13 105 specific platforms, and in fact creating these specific platforms
ohair@13 106 may be difficult due to the age of some of this software.
ohair@13 107 <p>
ohair@13 108 The minimum OS and C/C++ compiler versions needed for building the
ohair@13 109 OpenJDK:
ohair@13 110 <p>
ohair@13 111 <table border="1">
ohair@13 112 <thead>
ohair@13 113 <tr>
ohair@13 114 <th>Base OS and Architecture</th>
ohair@13 115 <th>OS</th>
ohair@13 116 <th>Compiler</th>
ohair@13 117 </tr>
ohair@13 118 </thead>
ohair@13 119 <tbody>
ohair@13 120 <tr>
ohair@13 121 <td>Linux X86 (32bit)</td>
ohair@13 122 <td>Red Hat Enterprise Linux 4 </td>
ohair@13 123 <td>gcc 4 </td>
ohair@13 124 </tr>
ohair@13 125 <tr>
ohair@13 126 <td>Linux X64 (64bit)</td>
ohair@13 127 <td>Red Hat Enterprise Linux 4 </td>
ohair@13 128 <td>gcc 4 </td>
ohair@13 129 </tr>
ohair@13 130 <tr>
ohair@13 131 <td>Solaris SPARC (32bit)</td>
ohair@13 132 <td>Solaris 10 + patches
ohair@13 133 <br>
ohair@13 134 See <a href="" target="_blank">
ohair@13 135 SunSolve</a> for patch downloads.
ohair@13 136 </td>
ohair@13 137 <td>Sun Studio 11 </td>
ohair@13 138 </tr>
ohair@13 139 <tr>
ohair@13 140 <td>Solaris SPARCV9 (64bit)</td>
ohair@13 141 <td>Solaris 10 + patches
ohair@13 142 <br>
ohair@13 143 See <a href="" target="_blank">
ohair@13 144 SunSolve</a> for patch downloads.
ohair@13 145 </td>
ohair@13 146 <td>Sun Studio 11</td>
ohair@13 147 </tr>
ohair@13 148 <tr>
ohair@13 149 <td>Solaris X86 (32bit)</td>
ohair@13 150 <td>Solaris 10 + patches
ohair@13 151 <br>
ohair@13 152 See <a href="" target="_blank">
ohair@13 153 SunSolve</a> for patch downloads.
ohair@13 154 </td>
ohair@13 155 <td>Sun Studio 11</td>
ohair@13 156 </tr>
ohair@13 157 <tr>
ohair@13 158 <td>Solaris X64 (64bit)</td>
ohair@13 159 <td>Solaris 10 + patches
ohair@13 160 <br>
ohair@13 161 See <a href="" target="_blank">
ohair@13 162 SunSolve</a> for patch downloads.
ohair@13 163 </td>
ohair@13 164 <td>Sun Studio 11</td>
ohair@13 165 </tr>
ohair@13 166 <tr>
ohair@13 167 <td>Windows X86 (32bit)</td>
ohair@13 168 <td>Windows XP</td>
ohair@13 169 <td>Microsoft Visual Studio .NET 2003 Professional</td>
ohair@13 170 </tr>
ohair@13 171 <tr>
ohair@13 172 <td>Windows X64 (64bit)</td>
ohair@13 173 <td>Windows Server 2003 - Enterprise x64 Edition</td>
ohair@13 174 <td>Microsoft Platform SDK - April 2005</td>
ohair@13 175 </tr>
ohair@13 176 </tbody>
ohair@13 177 </table>
ohair@13 178 </blockquote>
ohair@13 179 <!-- ------------------------------------------------------ -->
ohair@13 180 <hr>
ohair@13 181 <h2><a name="SDBE">Specific Developer Build Environments</a></h2>
ohair@13 182 <blockquote>
ohair@13 183 We won't be listing all the possible environments, but
ohair@13 184 we will try to provide what information we have available to us.
ohair@13 185 </blockquote>
ohair@13 186 <!-- ------------------------------------------------------ -->
ohair@13 187 <h3><a name="fedora">Fedora</a></h3>
ohair@13 188 <blockquote>
ohair@13 189 TBD
ohair@13 190 </blockquote>
ohair@13 191 <!-- ------------------------------------------------------ -->
ohair@13 192 <h3><a name="debian">Debian</a></h3>
ohair@13 193 <blockquote>
ohair@13 194 TBD
ohair@13 195 </blockquote>
ohair@13 196 <!-- ------------------------------------------------------ -->
ohair@13 197 <h3><a name="ubuntu">Ubuntu</a></h3>
ohair@13 198 <blockquote>
ohair@13 199 In addition to needing the Bootstrap JDK and the Binary Plugs,
ohair@13 200 when building on Ubuntu you will need to
ohair@13 201 make sure certain packages are installed.
ohair@13 202 In particular, certain X11 packages, make, m4, gawk, gcc 4,
ohair@13 203 binutils, cups, freetype
ohair@13 204 and alsa.
ohair@13 205 <!-- ------------------------------------------------------ -->
ohair@13 206 <h4>Ubuntu 6.06</h4>
ohair@13 207 <p>
ohair@13 208 The following list of packages for Ubuntu 6.06 is a working set that
ohair@13 209 does appear to work.
ohair@13 210 <p>
ohair@13 211 <b>Note that it's quite possible that some of these
ohair@13 212 packages are not required, so anyone discovering that some of the
ohair@13 213 packages listed below are NOT required,
ohair@13 214 please let the
ohair@13 215 OpenJDK
ohair@13 216 team know.</b>
ohair@13 217 <p>
ohair@13 218 All the packages below can be installed with the
ohair@13 219 Synaptic Package manager provided with the base Ubuntu 6.06 release.
ohair@13 220 <blockquote>
ohair@13 221 <ul>
ohair@13 222 <li>binutils (2.16.1cvs20060117-1ubuntu2.1)</li>
ohair@13 223 <li>cpp (4:4.0.3-1)</li>
ohair@13 224 <li>cpp-4.0 (4.0.3-1ubuntu5)</li>
ohair@13 225 <li>libfreetype6-dev</li>
ohair@13 226 <li>g++ (4:4.0.3-1)</li>
ohair@13 227 <li>g++-4.0 (4.0.3-1ubuntu5)</li>
ohair@13 228 <li>gawk (1:3.1.5-2build1)</li>
ohair@13 229 <li>gcc (4:4.0.3-1)</li>
ohair@13 230 <li>gcc-4.0 (4.0.3-1ubuntu5)</li>
ohair@13 231 <li>libasound2-dev (1.0.10-2ubuntu4)</li>
ohair@13 232 <li>libc6 (2.3.6-0ubuntu20) to 2.3.6-0ubuntu20.4</li>
ohair@13 233 <li>libc6-dev (2.3.6-0ubuntu20.4)</li>
ohair@13 234 <li>libc6-i686 (2.3.6-0ubuntu20) to 2.3.6-0ubuntu20.4</li>
ohair@13 235 <li>libcupsys2-dev (1.2.2-0ubuntu0.6.06)</li>
ohair@13 236 <li>libgcrypt11-dev (1.2.2-1)</li>
ohair@13 237 <li>libgnutls-dev (1.2.9-2ubuntu1.1)</li>
ohair@13 238 <li>libgnutls12 (1.2.9-2ubuntu1) to 1.2.9-2ubuntu1.1</li>
ohair@13 239 <li>libgpg-error-dev (1.1-4)</li>
ohair@13 240 <li>libice-dev (2:1.0.0-0ubuntu2)</li>
ohair@13 241 <li>liblockfile1 (1.06.1)</li>
ohair@13 242 <li>libopencdk8-dev (0.5.7-2)</li>
ohair@13 243 <li>libpopt-dev (1.7-5)</li>
ohair@13 244 <li>libsm-dev (2:1.0.0-0ubuntu2)</li>
ohair@13 245 <li>libstdc++6-4.0-dev (4.0.3-1ubuntu5)</li>
ohair@13 246 <li>libtasn1-2-dev (0.2.17-1ubuntu1)</li>
ohair@13 247 <li>libx11-dev (2:1.0.0-0ubuntu9)</li>
ohair@13 248 <li>libxau-dev (1:1.0.0-0ubuntu4)</li>
ohair@13 249 <li>libxaw-headers (2:1.0.1-0ubuntu3)</li>
ohair@13 250 <li>libxaw7-dev (2:1.0.1-0ubuntu3)</li>
ohair@13 251 <li>libxdmcp-dev (1:1.0.0-0ubuntu2)</li>
ohair@13 252 <li>libxext-dev (2:1.0.0-0ubuntu4)</li>
ohair@13 253 <li>libxi-dev (2:1.0.0-0ubuntu3) </li>
ohair@13 254 <li>libxmu-dev (2:1.0.0-0ubuntu3)</li>
ohair@13 255 <li>libxmu-headers (2:1.0.0-0ubuntu3)</li>
ohair@13 256 <li>libxmuu-dev (2:1.0.0-0ubuntu3)</li>
ohair@13 257 <li>libxp-dev (6.8.2-11ubuntu2)</li>
ohair@13 258 <li>libxpm-dev (1:</li>
ohair@13 259 <li>libxrandr-dev (1:</li>
ohair@13 260 <li>libxt-dev (1:1.0.0-0ubuntu3)</li>
ohair@13 261 <li>libxtrap-dev (2:1.0.0-0ubuntu2)</li>
ohair@13 262 <li>libxtst-dev (2:1.0.1-0ubuntu2)</li>
ohair@13 263 <li>libxv-dev (2:1.0.1-0ubuntu3)</li>
ohair@13 264 <li>linux-kernel-headers (</li>
ohair@13 265 <li>m4 (1.4.4-1)</li>
ohair@13 266 <li>make (3.80+3.81.b4-1)</li>
ohair@13 267 <li>ssl-cert (1.0.13)</li>
ohair@13 268 <li>x-dev (7.0.4-0ubuntu2)</li>
ohair@13 269 <li>x11proto-core-dev (7.0.4-0ubuntu2)</li>
ohair@13 270 <li>x11proto-input-dev (1.3.2-0ubuntu2)</li>
ohair@13 271 <li>x11proto-kb-dev (1.0.2-0ubuntu2)</li>
ohair@13 272 <li>x11proto-randr-dev (1.1.2-0ubuntu2)</li>
ohair@13 273 <li>x11proto-record-dev (1.13.2-0ubuntu2)</li>
ohair@13 274 <li>x11proto-trap-dev (3.4.3-0ubuntu2)</li>
ohair@13 275 <li>x11proto-video-dev (2.2.2-0ubuntu2)</li>
ohair@13 276 <li>x11proto-xext-dev (7.0.2-0ubuntu2)</li>
ohair@13 277 <li>xlibs-dev (7.0.0-0ubuntu45)</li>
ohair@13 278 <li>zlib1g-dev (1:1.2.3-6ubuntu4)</li>
duke@2 279 </ul>
ohair@13 280 </blockquote>
ohair@13 281 <!-- ------------------------------------------------------ -->
ohair@13 282 <h4>Ubuntu 7.04</h4>
ohair@13 283 <p>
ohair@13 284 Using the Synaptic Package Manager, download the following
ohair@13 285 packages (double indented packages are automatically aquired
ohair@13 286 due to package dependencies):
ohair@13 287 <blockquote>
ohair@13 288 <ul>
ohair@13 289 <li>build-essential</li>
ohair@13 290 <ul>
ohair@13 291 <li>dpkg-dev</li>
ohair@13 292 <li>g++</li>
ohair@13 293 <li>g++-4.1</li>
ohair@13 294 <li>libc6-dev</li>
ohair@13 295 <li>libstdc++6.4.1-dev</li>
ohair@13 296 <li>linux-libc-dev</li>
ohair@13 297 </ul>
ohair@13 298 <li>gawk</li>
ohair@13 299 <li>m4</li>
ohair@13 300 <li>libasound2-dev</li>
ohair@13 301 <li>libcupsys2-dev</li>
ohair@13 302 <ul>
ohair@13 303 <li>libgcrypt11-dev</li>
ohair@13 304 <li>lgnutls-dev</li>
ohair@13 305 <li>libgpg-error-dev</li>
ohair@13 306 <li>liblzo-dev</li>
ohair@13 307 <li>libopencdk8-dev</li>
ohair@13 308 <li>libpopt-dev</li>
ohair@13 309 <li>libtasn1-3-dev</li>
ohair@13 310 <li>zlib1g-dev</li>
ohair@13 311 </ul>
ohair@13 312 <li>sun-java6-jdk</li>
ohair@13 313 <ul>
ohair@13 314 <li>java-common</li>
ohair@13 315 <li>libltdl3</li>
ohair@13 316 <li>odbcinst1debian1</li>
ohair@13 317 <li>sun-java6-bin</li>
ohair@13 318 <li>sun-java6-jre</li>
ohair@13 319 <li>unixodbc</li>
ohair@13 320 </ul>
ohair@13 321 <li>xlibs-dev</li>
ohair@13 322 <ul>
ohair@13 323 <li>(many)</li>
ohair@13 324 </ul>
ohair@13 325 <li>x11proto-print-dev</li>
ohair@13 326 <li>libxaw7-dev</li>
ohair@13 327 <ul>
ohair@13 328 <li>libxaw-headers</li>
ohair@13 329 </ul>
ohair@13 330 <li>libxp-dev</li>
ohair@13 331 <li>libfreetype6-dev</li>
ohair@13 332 </ul>
ohair@13 333 </blockquote>
ohair@13 334 </blockquote>
ohair@13 335 <!-- ------------------------------------------------------ -->
ohair@13 336 <hr>
ohair@13 337 <h2><a name="directories">Source Directory Structure</a></h2>
ohair@13 338 <blockquote>
ohair@13 339 <p>
ohair@13 340 The source code for the OpenJDK is delivered in a set of
ohair@13 341 directories:
ohair@13 342 <tt>hotspot</tt>,
ohair@13 343 <tt>langtools</tt>,
ohair@13 344 <tt>corba</tt>,
ohair@13 345 <tt>jaxws</tt>,
ohair@13 346 <tt>jaxp</tt>,
ohair@13 347 and
ohair@13 348 <tt>jdk</tt>.
ohair@13 349 The <tt>hotspot</tt> directory contains the source code and make
ohair@13 350 files for building the OpenJDK Hotspot Virtual Machine.
ohair@13 351 The <tt>langtools</tt> directory contains the source code and make
ohair@13 352 files for building the OpenJDK javac and language tools.
ohair@13 353 The <tt>corba</tt> directory contains the source code and make
ohair@13 354 files for building the OpenJDK Corba files.
ohair@13 355 The <tt>jaxws</tt> directory contains the source code and make
ohair@13 356 files for building the OpenJDK JAXWS files.
ohair@13 357 The <tt>jaxp</tt> directory contains the source code and make
ohair@13 358 files for building the OpenJDK JAXP files.
ohair@13 359 The <tt>jdk</tt> directory contains the source code and make files for
ohair@13 360 building the OpenJDK runtime libraries and misc files.
ohair@13 361 The top level <tt>Makefile</tt>
ohair@13 362 is used to build the entire OpenJDK.
ohair@13 363 </blockquote>
ohair@13 364 <!-- ------------------------------------------------------ -->
ohair@13 365 <hr>
ohair@13 366 <h2><a name="building">Build Information</a></h2>
ohair@13 367 <blockquote>
ohair@13 368 Building the OpenJDK
ohair@13 369 is done with a <tt><i>gmake</i></tt>
ohair@13 370 command line and various
ohair@13 371 environment or make variable settings that direct the make rules
ohair@13 372 to where various components have been installed.
ohair@13 373 Where possible the makefiles will attempt to located the various
ohair@13 374 components in the default locations or any component specific
ohair@13 375 variable settings.
ohair@13 376 When the normal defaults fail or components cannot be found,
ohair@13 377 the various
ohair@13 378 <tt>ALT_*</tt> variables (alternates)
ohair@13 379 can be used to help the makefiles locate components.
ohair@13 380 <p>
ohair@13 381 Refer to the bash/sh/ksh setup file
ohair@13 382 <tt>jdk/make/</tt>
ohair@13 383 if you need help in setting up your environment variables.
ohair@13 384 A build could be as simple as:
ohair@13 385 <blockquote>
ohair@13 386 <pre><tt>
duke@2 387 bash
duke@2 388 . jdk/make/
duke@2 389 <i>gmake</i> sanity &amp;&amp; <i>gmake</i>
ohair@13 390 </tt></pre>
ohair@13 391 </blockquote>
ohair@13 392 <p>
ohair@13 393 Of course ksh or sh would work too.
ohair@13 394 But some customization will probably be necessary.
ohair@13 395 The <tt>sanity</tt> rule will make some basic checks on build
ohair@13 396 dependencies and generate appropriate warning messages
ohair@13 397 regarding missing, out of date, or newer than expected components
ohair@13 398 found on your system.
ohair@13 399 </blockquote>
ohair@13 400 <!-- ------------------------------------------------------ -->
ohair@13 401 <hr>
ohair@13 402 <h3><a name="gmake">GNU make (<tt><i>gmake</i></tt>)</a></h3>
ohair@13 403 <blockquote>
ohair@13 404 The Makefiles in the OpenJDK are only valid when used with the
ohair@13 405 GNU version of the utility command <tt>make</tt>
ohair@13 406 (<tt><i>gmake</i></tt>).
ohair@13 407 A few notes about using GNU make:
ohair@13 408 <ul>
ohair@13 409 <li>
ohair@13 410 In general, you need GNU make version 3.78.1 or newer.
ohair@13 411 </li>
ohair@13 412 <li>
ohair@13 413 Place the location of the GNU make binary in the <tt>PATH</tt>.
ohair@13 414 </li>
ohair@13 415 <li>
ohair@13 416 <strong>Linux:</strong>
ohair@13 417 The <tt>/usr/bin/make</tt> command should work fine for you.
ohair@13 418 </li>
ohair@13 419 <li>
ohair@13 420 <strong>Solaris:</strong>
ohair@13 421 Do NOT use <tt>/usr/bin/make</tt> on Solaris.
ohair@13 422 If your Solaris system has the software
ohair@13 423 from the Solaris Companion CD installed,
ohair@13 424 you should use <tt>gmake</tt>
ohair@13 425 which will be located in either the <tt>/opt/sfw/bin</tt> or
ohair@13 426 <tt>/usr/sfw/bin</tt> directory.
ohair@13 427 </li>
ohair@13 428 <li>
ohair@13 429 <strong>Windows:</strong>
ohair@13 430 Make sure you start your build inside a bash/sh/ksh shell.
ohair@13 431 <br>
ohair@13 432 <b>WARNING:</b> Watch out for make version 3.81, it may
ohair@13 433 not work due to a lack of support for drive letter paths
ohair@13 434 like <tt>C:/</tt>. See
ohair@13 435 <a href="#gmake">section on gmake</a>.
ohair@13 436 Use a 3.80 version, or find a newer
ohair@13 437 version that has this problem fixed.
ohair@13 438 The older 3.80 version of make.exe can be downloaded with this
ohair@13 439 <a href="" target="_blank">
ohair@13 440 link</a>.
ohair@13 441 Also see the
ohair@13 442 <a href="" target="_blank">
ohair@13 443 mozilla developer center</a>
ohair@13 444 on this topic.
ohair@13 445 </li>
ohair@13 446 </ul>
ohair@13 447 <p>
ohair@13 448 Information on GNU make, and access to ftp download sites, are
ohair@13 449 available on the
ohair@13 450 <a href="" target="_blank">
ohair@13 451 GNU make web site
ohair@13 452 </a>.
ohair@13 453 The latest source to GNU make is available at
ohair@13 454 <a href="" target="_blank">
ohair@13 455</a>.
ohair@13 456 </blockquote>
ohair@13 457 <!-- ------------------------------------------------------ -->
ohair@13 458 <hr>
ohair@13 459 <h3><a name="linux">Basic Linux System Setup</a></h3>
ohair@13 460 <blockquote>
ohair@13 461 <strong>i586 only:</strong>
ohair@13 462 The minimum recommended hardware for building the Linux version
ohair@13 463 is a Pentium class processor or better, at least 256 MB of RAM, and
ohair@13 464 approximately 1.5 GB of free disk space.
ohair@13 465 <p>
ohair@13 466 <strong>X64 only:</strong>
ohair@13 467 The minimum recommended hardware for building the Linux
ohair@13 468 version is an AMD Opteron class processor, at least 512 MB of RAM, and
ohair@13 469 approximately 4 GB of free disk space.
ohair@13 470 <p>
ohair@13 471 The build will use the tools contained in
ohair@13 472 <tt>/bin</tt> and
ohair@13 473 <tt>/usr/bin</tt>
ohair@13 474 of a standard installation of the Linux operating environment.
ohair@13 475 You should ensure that these directories are in your
ohair@13 476 <tt>PATH</tt>.
ohair@13 477 <p>
ohair@13 478 Note that some Linux systems have a habit of pre-populating
ohair@13 479 your environment variables for you, for example <tt>JAVA_HOME</tt>
ohair@13 480 might get pre-defined for you to refer to the JDK installed on
ohair@13 481 your Linux system.
ohair@13 482 You will need to unset <tt>JAVA_HOME</tt>.
ohair@13 483 It's a good idea to run <tt>env</tt> and verify the
ohair@13 484 environment variables you are getting from the default system
ohair@13 485 settings make sense for building the
ohair@13 486 OpenJDK.
ohair@13 487 </blockquote>
ohair@13 488 <!-- ------------------------------------------------------ -->
ohair@13 489 <h4><a name="linux_checklist">Basic Linux Check List</a></h4>
ohair@13 490 <blockquote>
ohair@13 491 <ol>
ohair@13 492 <li>
ohair@13 493 Install the
ohair@13 494 <a href="#bootjdk">Bootstrap JDK</a>, set
ohair@13 495 <tt><a href="#ALT_BOOTDIR">ALT_BOOTDIR</a></tt>.
ohair@13 496 </li>
ohair@13 497 <li>
ohair@13 498 Install the
ohair@13 499 <a href="#binaryplugs">Binary Plugs</a>, set
ohair@13 500 <tt><a href="#ALT_BINARY_PLUGS_PATH">ALT_BINARY_PLUGS_PATH</a></tt>.
ohair@13 501 </li>
ohair@13 502 <li>
ohair@13 503 <a href="#importjdk">Optional Import JDK</a>, set
ohair@13 504 <tt><a href="#ALT_JDK_IMPORT_PATH">ALT_JDK_IMPORT_PATH</a></tt>.
ohair@13 505 </li>
ohair@13 506 <li>
ohair@13 507 Install or upgrade the <a href="#freetype">FreeType development
ohair@13 508 package</a>.
ohair@13 509 </li>
ohair@13 510 </ol>
ohair@13 511 </blockquote>
ohair@13 512 <!-- ------------------------------------------------------ -->
ohair@13 513 <hr>
ohair@13 514 <h3><a name="solaris">Basic Solaris System Setup</a></h3>
ohair@13 515 <blockquote>
ohair@13 516 The minimum recommended hardware for building the
ohair@13 517 Solaris SPARC version is an UltraSPARC with 512 MB of RAM.
ohair@13 518 For building
ohair@13 519 the Solaris x86 version, a Pentium class processor or better and at
ohair@13 520 least 512 MB of RAM are recommended.
ohair@13 521 Approximately 1.4 GB of free disk
ohair@13 522 space is needed for a 32-bit build.
ohair@13 523 <p>
ohair@13 524 If you are building the 64bit version, you should
ohair@13 525 run the command "isainfo -v" to verify that you have a
ohair@13 526 64-bit installation, it should say <tt>sparcv9</tt> or
ohair@13 527 <tt>amd64</tt>.
ohair@13 528 An additional 7 GB of free disk space is needed
ohair@13 529 for a 64-bit build.
ohair@13 530 <p>
ohair@13 531 The build uses the tools contained in <tt>/usr/ccs/bin</tt>
ohair@13 532 and <tt>/usr/bin</tt> of a standard developer or full installation of
ohair@13 533 the Solaris operating environment.
ohair@13 534 <p>
ohair@13 535 Solaris patches specific to the JDK can be downloaded from the
ohair@13 536 <a href="" target="_blank">
ohair@13 537 SunSolve JDK Solaris patches download page</a>.
ohair@13 538 You should ensure that the latest patch cluster for
ohair@13 539 your version of the Solaris operating environment has also
ohair@13 540 been installed.
ohair@13 541 </blockquote>
ohair@13 542 <!-- ------------------------------------------------------ -->
ohair@13 543 <h4><a name="solaris_checklist">Basic Solaris Check List</a></h4>
ohair@13 544 <blockquote>
ohair@13 545 <ol>
ohair@13 546 <li>
ohair@13 547 Install the
ohair@13 548 <a href="#bootjdk">Bootstrap JDK</a>, set
ohair@13 549 <tt><a href="#ALT_BOOTDIR">ALT_BOOTDIR</a></tt>.
ohair@13 550 </li>
ohair@13 551 <li>
ohair@13 552 Install the
ohair@13 553 <a href="#binaryplugs">Binary Plugs</a>, set
ohair@13 554 <tt><a href="#ALT_BINARY_PLUGS_PATH">ALT_BINARY_PLUGS_PATH</a></tt>.
ohair@13 555 </li>
ohair@13 556 <li>
ohair@13 557 <a href="#importjdk">Optional Import JDK</a>, set
ohair@13 558 <tt><a href="#ALT_JDK_IMPORT_PATH">ALT_JDK_IMPORT_PATH</a></tt>.
ohair@13 559 </li>
ohair@13 560 <li>
ohair@13 561 Install the
ohair@13 562 <a href="#studio">Sun Studio Compilers</a>, set
ohair@13 563 <a href="#ALT_COMPILER_PATH"><tt>ALT_COMPILER_PATH</tt></a>.
ohair@13 564 </li>
ohair@13 565 <li>
ohair@13 566 Install the
ohair@13 567 <a href="#cups">CUPS Include files</a>, set
ohair@13 568 <tt><a href="#ALT_CUPS_HEADERS_PATH">ALT_CUPS_HEADERS_PATH</a></tt>.
ohair@13 569 </li>
ohair@13 570 </ol>
ohair@13 571 </blockquote>
ohair@13 572 <!-- ------------------------------------------------------ -->
ohair@13 573 <hr>
ohair@13 574 <h3><a name="windows">Basic Windows System Setup</a></h3>
ohair@13 575 <blockquote>
ohair@13 576 <strong>i586 only:</strong>
ohair@13 577 The minimum recommended hardware for building the 32bit or X86
ohair@13 578 Windows version is an Pentium class processor or better, at least
ohair@13 579 512 MB of RAM, and approximately 600 MB of free disk space.
ohair@13 580 <strong>
ohair@13 581 NOTE: The Windows 2000 build machines need to use the
ohair@13 582 file system NTFS.
ohair@13 583 Build machines formatted to FAT32 will not work
ohair@13 584 because FAT32 doesn't support case-sensitivity in file names.
ohair@13 585 </strong>
ohair@13 586 <p>
ohair@13 587 <strong>X64 only:</strong>
ohair@13 588 The minimum recommended hardware for building
ohair@13 589 the Windows X64 version is an AMD Opteron class processor, at least 1
ohair@13 590 GB of RAM, and approximately 10 GB of free disk space.
ohair@13 591 </blockquote>
ohair@13 592 <!-- ------------------------------------------------------ -->
ohair@13 593 <h4><a name="paths">Windows Paths</a></h4>
ohair@13 594 <blockquote>
duke@2 595 <strong>Windows:</strong>
ohair@13 596 Note that GNU make is a historic utility and is based very
ohair@13 597 heavily on shell scripting, so it does not tolerate the Windows habit
ohair@13 598 of having spaces in pathnames or the use of the <tt>\</tt>characters in pathnames.
ohair@13 599 Luckily on most Windows systems, you can use <tt>/</tt>instead of \, and
ohair@13 600 there is always a 'short' pathname without spaces for any path that
ohair@13 601 contains spaces.
ohair@13 602 Unfortunately, this short pathname can be somewhat dynamic and the
ohair@13 603 formula is difficult to explain.
ohair@13 604 You can use <tt>cygpath</tt> utility to map pathnames with spaces
ohair@13 605 or the <tt>\</tt>character into the <tt>C:/</tt> style of pathname
ohair@13 606 (called 'mixed'), e.g.
ohair@13 607 <tt>cygpath -s -m "<i>path</i>"</tt>.
ohair@13 608 <p>
ohair@13 609 The makefiles will try to translate any pathnames supplied
ohair@13 610 to it into the <tt>C:/</tt> style automatically.
ohair@13 611 <p>
ohair@13 612 Note that use of CYGWIN creates a unique problem with regards to
ohair@13 613 setting <a href="#path"><tt>PATH</tt></a>. Normally on Windows
ohair@13 614 the <tt>PATH</tt> variable contains directories
ohair@13 615 separated with the ";" character (Solaris and Linux uses ":").
ohair@13 616 With CYGWIN, it uses ":", but that means that paths like "C:/path"
ohair@13 617 cannot be placed in the CYGWIN version of <tt>PATH</tt> and
ohair@13 618 instead CYGWIN uses something like <tt>/cygdrive/c/path</tt>
ohair@13 619 which CYGWIN understands, but only CYGWIN understands.
ohair@13 620 So be careful with paths on Windows.
ohair@13 621 </blockquote>
ohair@13 622 <!-- ------------------------------------------------------ -->
ohair@13 623 <h4><a name="windows_checklist">Basic Windows Check List</a></h4>
duke@2 624 <blockquote>
ohair@13 625 <ol>
ohair@13 626 <li>
ohair@13 627 Install the
ohair@13 628 <a href="#cygwin">CYGWIN product</a>.
ohair@13 629 </li>
ohair@13 630 <li>
ohair@13 631 Install the
ohair@13 632 <a href="#bootjdk">Bootstrap JDK</a>, set
ohair@13 633 <tt><a href="#ALT_BOOTDIR">ALT_BOOTDIR</a></tt>.
ohair@13 634 </li>
ohair@13 635 <li>
ohair@13 636 Install the
ohair@13 637 <a href="#binaryplugs">Binary Plugs</a>, set
ohair@13 638 <tt><a href="#ALT_BINARY_PLUGS_PATH">ALT_BINARY_PLUGS_PATH</a></tt>..
ohair@13 639 </li>
ohair@13 640 <li>
ohair@13 641 <a href="#importjdk">Optional Import JDK</a>, set
ohair@13 642 <tt><a href="#ALT_JDK_IMPORT_PATH">ALT_JDK_IMPORT_PATH</a></tt>.
ohair@13 643 </li>
ohair@13 644 <li>
ohair@13 645 Install the
ohair@13 646 <a href="#msvc">Microsoft Visual Studio .NET 2003 Professional</a> or the
ohair@13 647 <a href="#mssdk">Microsoft Platform SDK</a>.
ohair@13 648 </li>
ohair@13 649 <li>
ohair@13 650 Setup all environment variables for compilers
ohair@13 651 (see <a href="#msvc">compilers</a>).
ohair@13 652 </li>
ohair@13 653 <li>
ohair@13 654 Install
ohair@13 655 <a href="#dxsdk">Microsoft DirectX SDK</a>.
ohair@13 656 </li>
ohair@13 657 </ol>
duke@2 658 </blockquote>
ohair@13 659 <!-- ------------------------------------------------------ -->
ohair@13 660 <hr>
ohair@13 661 <h3><a name="dependencies">Build Dependencies</a></h3>
duke@2 662 <blockquote>
ohair@13 663 Depending on the platform, the OpenJDK build process has some basic
ohair@13 664 dependencies on components not part of the OpenJDK sources.
ohair@13 665 Some of these are specific to a platform, some even specific to
ohair@13 666 an architecture.
ohair@13 667 Each dependency will have a set of ALT variables that can be set
ohair@13 668 to tell the makefiles where to locate the component.
ohair@13 669 In most cases setting these ALT variables may not be necessary
ohair@13 670 and the makefiles will find defaults on the system in standard
ohair@13 671 install locations or through component specific variables.
ohair@13 672 <!-- ------------------------------------------------------ -->
ohair@13 673 <h4><a name="bootjdk">Bootstrap JDK</a></h4>
ohair@13 674 <blockquote>
ohair@13 675 All OpenJDK builds require access to the previously released
ohair@13 676 JDK 6, this is often called a bootstrap JDK.
ohair@13 677 The JDK 6 binaries can be downloaded from Sun's
ohair@13 678 <a href="" target="_blank">JDK 6 download site</a>.
ohair@13 679 For build performance reasons
ohair@13 680 is very important that this bootstrap JDK be made available on the
ohair@13 681 local disk of the machine doing the build.
ohair@13 682 You should always set
ohair@13 683 <tt><a href="#ALT_BOOTDIR">ALT_BOOTDIR</a></tt>
ohair@13 684 to point to the location of
ohair@13 685 the bootstrap JDK installation, this is the directory pathname
ohair@13 686 that contains a <tt>bin, lib, and include</tt>
ohair@13 687 It's also a good idea to also place its <tt>bin</tt> directory
ohair@13 688 in the <tt>PATH</tt> environment variable, although it's
ohair@13 689 not required.
ohair@13 690 <p>
ohair@13 691 <strong>Solaris:</strong>
ohair@13 692 Some pre-installed JDK images may be available to you in the
ohair@13 693 directory <tt>/usr/jdk/instances</tt>.
ohair@13 694 If you don't set
ohair@13 695 <tt><a href="#ALT_BOOTDIR">ALT_BOOTDIR</a></tt>
ohair@13 696 the makefiles will look in that location for a JDK it can use.
ohair@13 697 </blockquote>
ohair@13 698 <!-- ------------------------------------------------------ -->
ohair@13 699 <h4><a name="binaryplugs">Binary Plugs</a></h4>
ohair@13 700 <blockquote>
ohair@13 701 Not all of the source code that makes up the JDK is available
ohair@13 702 under an open-source license.
ohair@13 703 This is a temporary situation and these binary plugs will be
ohair@13 704 replaced with fully open source replacements as soon as possible.
ohair@13 705 So currently, in order to build a complete OpenJDK image,
ohair@13 706 you must first download and install the appropriate
ohair@13 707 binary plug bundles for the OpenJDK, go to the
ohair@13 708 <a href="" target="_blank">OpenJDK</a> site and select
ohair@13 709 the "<b>Bundles(7)</b>" link and download the binaryplugs for
ohair@13 710 your particular platform.
ohair@13 711 The file downloaded is a jar file that must be extracted by running
ohair@13 712 the jar file with:
ohair@13 713 <blockquote>
ohair@13 714 <pre>
ohair@13 715 <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 716 </pre>
ohair@13 717 </blockquote>
ohair@13 718 A prompt will be issued for acceptance of these binary plug files.
ohair@13 719 During the OpenJDK build process these "binary plugs"
ohair@13 720 for the encumbered components will be copied into your
ohair@13 721 resulting OpenJDK binary build image.
ohair@13 722 These binary plug files are only for the purpose of
ohair@13 723 building an OpenJDK binary.
ohair@13 724 Make sure you set
ohair@13 725 <tt><a href="#ALT_BINARY_PLUGS_PATH">ALT_BINARY_PLUGS_PATH</a></tt>
ohair@13 726 to the root of this installation.
ohair@13 727 </blockquote>
ohair@13 728 <!-- ------------------------------------------------------ -->
ohair@13 729 <h4><a name="importjdk">Optional Import JDK</a></h4>
ohair@13 730 <blockquote>
ohair@13 731 The <tt><a href="#ALT_JDK_IMPORT_PATH">ALT_JDK_IMPORT_PATH</a></tt>
ohair@13 732 setting is only needed if you are not building the entire
ohair@13 733 JDK. For example, if you have built the entire JDK once, and
ohair@13 734 wanted to avoid repeatedly building the Hotspot VM, you could
ohair@13 735 set this to the location of the previous JDK install image
ohair@13 736 and the build will copy the needed files from this import area.
ohair@13 737 </blockquote>
ohair@13 738 <!-- ------------------------------------------------------ -->
ohair@13 739 <h4><a name="cacerts">Certificate Authority File (cacert)</a></h4>
ohair@13 740 <blockquote>
ohair@13 741 See <a href="" target="_blank">
ohair@13 742</a>
ohair@13 743 for a better understanding of the Certificate Authority (CA).
ohair@13 744 A certificates file named "cacerts"
ohair@13 745 represents a system-wide keystore with CA certificates.
ohair@13 746 In JDK and JRE
ohair@13 747 binary bundles, the "cacerts" file contains root CA certificates from
ohair@13 748 several public CAs (e.g., VeriSign, Thawte, and Baltimore).
ohair@13 749 The source contain a cacerts file
ohair@13 750 without CA root certificates.
ohair@13 751 Formal JDK builders will need to secure
ohair@13 752 permission from each public CA and include the certificates into their
ohair@13 753 own custom cacerts file.
ohair@13 754 Failure to provide a populated cacerts file
ohair@13 755 will result in verification errors of a certificate chain during runtime.
ohair@13 756 The variable
ohair@13 757 <tt><a href="#ALT_CACERTS_FILE">ALT_CACERTS_FILE</a></tt>
ohair@13 758 can be used to override the default location of the
ohair@13 759 cacerts file that will get placed in your build.
ohair@13 760 By default an empty cacerts file is provided and that should be
ohair@13 761 fine for most JDK developers.
ohair@13 762 </blockquote>
ohair@13 763 <!-- ------------------------------------------------------ -->
ohair@13 764 <h4><a name="compilers">Compilers</a></h4>
ohair@13 765 <blockquote>
ohair@13 766 <strong><a name="gcc">Linux gcc/binutils</a></strong>
ohair@13 767 <blockquote>
ohair@13 768 The GNU gcc compiler version should be 3.2.2 or newer.
ohair@13 769 The binutils package should be or newer.
ohair@13 770 The compiler used should be the default compiler installed
ohair@13 771 in <tt>/usr/bin</tt>.
ohair@13 772 <p>
ohair@13 773 Older Linux systems may require a gcc and bunutils update.
ohair@13 774 The Redhat Enterprise Advanced Server 2.1 update 2 system
ohair@13 775 is one of these systems.
ohair@13 776 RedHat Linux users can obtain this binutils package from
ohair@13 777 <a href=""
ohair@13 778 target="_blank">Redhat web site</a>.
ohair@13 779 You will need to remove the default compiler and binutils
ohair@13 780 packages and install the required packages
ohair@13 781 into the default location on the system.
ohair@13 782 However if you have a new video card driver, like
ohair@13 783 Geforce 4 it is best to use
ohair@13 784 the same compiler as the kernel was built with to
ohair@13 785 build the new video card driver module.
ohair@13 786 So you should build the modules before making this change.
ohair@13 787 </blockquote>
ohair@13 788 <strong><a name="studio">Solaris: Sun Studio</a></strong>
ohair@13 789 <blockquote>
ohair@13 790 At a minimum, the
ohair@13 791 <a href="" target="_blank">
ohair@13 792 Sun Studio 11 Compilers</a>
ohair@13 793 (containing version 5.8 of the C and C++ compilers) is required,
ohair@13 794 with patches from the
ohair@13 795 <a href="" target="_blank">
ohair@13 796 SunSolve web site</a>.
ohair@13 797 <p>
ohair@13 798 Set
ohair@13 799 <a href="#ALT_COMPILER_PATH"><tt>ALT_COMPILER_PATH</tt></a>
ohair@13 800 to point to the location of
ohair@13 801 the compiler binaries, and place this location in the <tt>PATH</tt>.
ohair@13 802 <p>
ohair@13 803 The Sun Studio Express compilers at:
ohair@13 804 <a href="" target="_blank">
ohair@13 805 Sun Studio Express Download site</a>
ohair@13 806 are also an option, although these compilers have not
ohair@13 807 been extensively used yet.
ohair@13 808 </blockquote>
ohair@13 809 <strong><a name="msvc">Windows i586: Microsoft Visual Studio .NET 2003 Professional</a></strong>
ohair@13 810 <blockquote>
ohair@13 811 The 32-bit OpenJDK Windows build
ohair@13 812 requires Microsoft Visual Studio .NET 2003 (VS2003) Professional
ohair@13 813 Edition compiler.
ohair@13 814 The compiler and other tools are expected to reside
ohair@13 815 in the location defined by the variable <tt>VS71COMNTOOLS</tt> which
ohair@13 816 is set by the Microsoft Visual Studio .NET installer.
ohair@13 817 <p>
ohair@13 818 Once the compiler is installed,
ohair@13 819 it is recommended that you run <tt>VCVARS32.BAT</tt>
ohair@13 820 to set the compiler environment variables
ohair@13 821 <tt>MSVCDIR</tt>,
ohair@13 822 <tt>INCLUDE</tt>,
ohair@13 823 <tt>LIB</tt>, and
ohair@13 824 <tt>PATH</tt>
ohair@13 825 prior to building the
ohair@13 826 OpenJDK.
ohair@13 827 The above environment variables <b>MUST</b> be set.
ohair@13 828 <p>
ohair@13 829 The Microsoft Visual Studio .NET 2005 (VS2005) compiler
ohair@13 830 will not work at this time due to the new runtime dll
ohair@13 831 and the manifest requirements.
ohair@13 832 </blockquote>
ohair@13 833 <strong><a name="mssdk">Windows X64: Microsoft Platform SDK April 2005</a></strong>
ohair@13 834 <blockquote>
ohair@13 835 On <b>X64</b>, the Microsoft Platform Software
ohair@13 836 Development Kit (SDK), April 2005 Edition compiler,
ohair@13 837 is required for building the OpenJDK
ohair@13 838 because it contains the C/C++ compiler.
ohair@13 839 You will need to minimally install the Core SDK and
ohair@13 840 the MDAC SDK features of this compiler.
ohair@13 841 <p>
ohair@13 842 Once the Platform SDK is installed,
ohair@13 843 it is recommended that you run <tt>SetEnv.Cmd /X64</tt>
ohair@13 844 to set the compiler environment variables
ohair@13 845 <tt>MSSDK</tt>,
ohair@13 846 <tt>MSTOOLS</tt>,
ohair@13 847 <tt>INCLUDE</tt>,
ohair@13 848 <tt>LIB</tt>, and
ohair@13 849 <tt>PATH</tt>
ohair@13 850 prior to building the
ohair@13 851 OpenJDK.
ohair@13 852 The above environment variables <b>MUST</b> be set.
ohair@13 853 <p>
ohair@13 854 Note that this compiler may say it's version is a
ohair@13 855 Microsoft Visual Studio .NET 2005 (VS2005), but be careful,
ohair@13 856 it will not match the official VS2005 product.
ohair@13 857 This Platform SDK compiler is only used on X64 builds.
ohair@13 858 </blockquote>
ohair@13 859 </blockquote>
ohair@13 860 <!-- ------------------------------------------------------ -->
ohair@13 861 <h4><a name="zip">Zip and Unzip</a></h4>
ohair@13 862 <blockquote>
ohair@13 863 Version 2.2 (November 3rd 1997) or newer of the zip utility
ohair@13 864 and version 5.12 or newer of the unzip utility is needed
ohair@13 865 to build the JDK.
ohair@13 866 With Solaris, Linux, and Windows CYGWIN, the zip and unzip
ohair@13 867 utilities installed on the system should be fine.
ohair@13 868 Information and the source code for
ohair@13 869 ZIP.EXE and UNZIP.EXE is available on the
ohair@13 870 <a href=""
ohair@13 871 target="_blank">info-zip web site</a>.
ohair@13 872 </blockquote>
ohair@13 873 <!-- ------------------------------------------------------ -->
ohair@13 874 <h4><a name="cups">Common UNIX Printing System (CUPS) Headers (Solaris &amp; Linux)</a></h4>
ohair@13 875 <blockquote>
ohair@13 876 <strong>Solaris:</strong>
ohair@13 877 CUPS header files are required for building the
ohair@13 878 OpenJDK on Solaris.
ohair@13 879 The Solaris header files can be obtained by installing
ohair@13 880 the package <strong>SFWcups</strong> from the Solaris Software
ohair@13 881 Companion CD/DVD, these often will be installed into
ohair@13 882 <tt>/opt/sfw/cups</tt>.
ohair@13 883 <p>
ohair@13 884 <strong>Linux:</strong>
ohair@13 885 CUPS header files are required for building the
ohair@13 886 OpenJDK on Linux.
ohair@13 887 The Linux header files are usually available from a "cups"
ohair@13 888 development package, it's recommended that you try and use
ohair@13 889 the package provided by the particular version of Linux that
ohair@13 890 you are using.
ohair@13 891 <p>
ohair@13 892 The CUPS header files can always be downloaded from
ohair@13 893 <a href="" target="_blank"></a>.
ohair@13 894 The variable
ohair@13 895 <tt><a href="#ALT_CUPS_HEADERS_PATH">ALT_CUPS_HEADERS_PATH</a></tt>
ohair@13 896 can be used to override the default location of the
ohair@13 897 CUPS Header files.
ohair@13 898 </blockquote>
ohair@13 899 <!-- ------------------------------------------------------ -->
ohair@13 900 <h4><a name="freetype">FreeType 2</a></h4>
ohair@13 901 <blockquote>
ohair@13 902 Version 2.3 or newer of FreeType is required for building the OpenJDK.
ohair@13 903 On Unix systems required files can be available as part of your
ohair@13 904 distribution (while you still may need to upgrade them).
ohair@13 905 Note that you need development version of package that
ohair@13 906 includes both FreeType library and header files.
ohair@13 907 <p>
ohair@13 908 You can always download latest FreeType version from the
ohair@13 909 <a href="" target="_blank">FreeType website</a>.
ohair@13 910 <p>
ohair@13 911 Makefiles will try to pick FreeType from /usr/lib and /usr/include.
ohair@13 912 In case it is installed elsewhere you will need to set environment
ohair@13 913 variables
ohair@13 914 <tt><a href="#ALT_FREETYPE_LIB_PATH">ALT_FREETYPE_LIB_PATH</a></tt>
ohair@13 915 and
ohair@13 916 <tt><a href="#ALT_FREETYPE_HEADERS_PATH">ALT_FREETYPE_HEADERS_PATH</a></tt>
ohair@13 917 to refer to place where library and header files are installed.
ohair@13 918 </blockquote>
ohair@13 919 <!-- ------------------------------------------------------ -->
ohair@13 920 <h4><a name="alsa">Advanced Linux Sound Architecture (ALSA) (Linux only)</a></h4>
ohair@13 921 <blockquote>
ohair@13 922 <strong>Linux only:</strong>
ohair@13 923 Version 0.9.1 or newer of the ALSA files are
ohair@13 924 required for building the OpenJDK on Linux.
ohair@13 925 These Linux files are usually available from an "alsa"
ohair@13 926 of "libasound"
ohair@13 927 development package, it's highly recommended that you try and use
ohair@13 928 the package provided by the particular version of Linux that
ohair@13 929 you are using.
ohair@13 930 The makefiles will check this emit a sanity error if it is
ohair@13 931 missing or the wrong version.
ohair@13 932 <p>
ohair@13 933 In particular, older Linux systems will likely not have the
ohair@13 934 right version of ALSA installed, for example
ohair@13 935 Redhat AS 2.1 U2 and SuSE 8.1 do not include a sufficiently
ohair@13 936 recent ALSA distribution.
ohair@13 937 On rpm-based systems, you can see if ALSA is installed by
ohair@13 938 running this command:
ohair@13 939 <pre>
ohair@13 940 <tt>rpm -qa | grep alsa</tt>
ohair@13 941 </pre>
ohair@13 942 Both <tt>alsa</tt> and <tt>alsa-devel</tt> packages are needed.
ohair@13 943 <p>
ohair@13 944 If your distribution does not come with ALSA, and you can't
ohair@13 945 find ALSA packages built for your particular system,
ohair@13 946 you can try to install the pre-built ALSA rpm packages from
ohair@13 947 <a href="" target="_blank">
ohair@13 948 <tt></tt></a>.
ohair@13 949 Note that installing a newer ALSA could
ohair@13 950 break sound output if an older version of ALSA was previously
ohair@13 951 installed on the system, but it will enable JDK compilation.
ohair@13 952 <blockquote>
ohair@13 953 Installation: execute as root<br>
ohair@13 954 [i586]: <code>rpm -Uv --force alsa-lib-devel-0.9.1-rh61.i386.rpm</code><br>
ohair@13 955 [x64]: <code>rpm -Uv --force alsa-lib-devel-0.9.8-amd64.x86_64.rpm</code><br>
ohair@13 956 Uninstallation:<br>
ohair@13 957 [i586]: <code>rpm -ev alsa-lib-devel-0.9.1-rh61</code><br>
ohair@13 958 [x64]:<code>rpm -ev alsa-lib-devel-0.9.8-amd64</code><br>
ohair@13 959 Make sure that you do not link to the static library
ohair@13 960 (<tt>libasound.a</tt>),
ohair@13 961 by verifying that the dynamic library (<tt></tt>) is
ohair@13 962 correctly installed in <tt>/usr/lib</tt>.
ohair@13 963 </blockquote>
ohair@13 964 As a last resort you can go to the
ohair@13 965 <a href="" target="_blank">
ohair@13 966 Advanced Linux Sound Architecture Site</a> and build it from
ohair@13 967 source.
ohair@13 968 <blockquote>
ohair@13 969 Download driver and library
ohair@13 970 source tarballs from
ohair@13 971 <a href="" target="_blank">ALSA's homepage</a>.
ohair@13 972 As root, execute the following
ohair@13 973 commands (you may need to adapt the version number):
ohair@13 974 <pre>
ohair@13 975 <tt>
ohair@13 976 $ tar xjf alsa-driver-0.9.1.tar.bz2
ohair@13 977 $ cd alsa-driver-0.9.1
ohair@13 978 $ ./configure
ohair@13 979 $ make install
ohair@13 980 $ cd ..
ohair@13 981 $ tar xjf alsa-lib-0.9.1.tar.bz2
ohair@13 982 $ cd alsa-lib-0.9.1
ohair@13 983 $ ./configure
ohair@13 984 $ make install
ohair@13 985 </tt>
ohair@13 986 </pre>
ohair@13 987 Should one of the above steps fail, refer to the documentation on
ohair@13 988 ALSA's home page.
ohair@13 989 </blockquote>
ohair@13 990 Note that this is a minimum install that enables
ohair@13 991 building the JDK platform. To actually use ALSA sound drivers, more
ohair@13 992 steps are necessary as outlined in the documentation on ALSA's homepage.
ohair@13 993 <p>
ohair@13 994 ALSA can be uninstalled by executing <tt>make uninstall</tt> first in
ohair@13 995 the <tt>alsa-lib-0.9.1</tt> directory and then in
ohair@13 996 <tt>alsa-driver-0.9.1</tt>.
ohair@13 997 </blockquote>
ohair@13 998 There are no ALT* variables to change the assumed locations of ALSA,
ohair@13 999 the makefiles will expect to find the ALSA include files and library at:
ohair@13 1000 <tt>/usr/include/alsa</tt> and <tt>/usr/lib/</tt>.
duke@2 1001 </blockquote>
ohair@13 1002 <!-- ------------------------------------------------------ -->
ohair@13 1003 <h4>Windows Specific Dependencies</h4>
duke@2 1004 <blockquote>
ohair@13 1005 <strong>Unix Command Tools (<a name="cygwin">CYGWIN</a>)</strong>
ohair@13 1006 <blockquote>
ohair@13 1007 The OpenJDK requires access to a set of unix command tools
ohair@13 1008 on Windows which can be supplied by
ohair@13 1009 <a href="" target="_blank">CYGWIN</a>.
ohair@13 1010 <p>
ohair@13 1011 The OpenJDK build requires CYGWIN version 1.5.12 or newer.
ohair@13 1012 Information about CYGWIN can
ohair@13 1013 be obtained from the CYGWIN website at
ohair@13 1014 <a href="" target="_blank"></a>.
ohair@13 1015 <p>
ohair@13 1016 By default CYGWIN doesn't install all the tools required for building
ohair@13 1017 the OpenJDK.
ohair@13 1018 Along with the default installation, you need to install
ohair@13 1019 the following tools.
ohair@13 1020 <blockquote>
ohair@13 1021 <table border="1">
ohair@13 1022 <thead>
ohair@13 1023 <tr>
ohair@13 1024 <td>Binary Name</td>
ohair@13 1025 <td>Package</td>
ohair@13 1026 <td>Description</td>
ohair@13 1027 </tr>
ohair@13 1028 </thead>
ohair@13 1029 <tbody>
ohair@13 1030 <tr>
ohair@13 1031 <td>ar.exe</td>
ohair@13 1032 <td>Devel</td>
ohair@13 1033 <td>binutils: The GNU assembler, linker and binary
ohair@13 1034 utilities</td>
ohair@13 1035 </tr>
ohair@13 1036 <tr>
ohair@13 1037 <td>make.exe</td>
ohair@13 1038 <td>Devel</td>
ohair@13 1039 <td>make: The GNU version of the 'make' utility</td>
ohair@13 1040 </tr>
ohair@13 1041 <tr>
ohair@13 1042 <td>m4.exe</td>
ohair@13 1043 <td>Interpreters</td>
ohair@13 1044 <td>m4: GNU implementation of the traditional Unix macro
ohair@13 1045 processor</td>
ohair@13 1046 </tr>
ohair@13 1047 <tr>
ohair@13 1048 <td>cpio.exe</td>
ohair@13 1049 <td>Utils</td>
ohair@13 1050 <td>cpio: A program to manage archives of files</td>
ohair@13 1051 </tr>
ohair@13 1052 <tr>
ohair@13 1053 <td>awk.exe</td>
ohair@13 1054 <td>Utils</td>
ohair@13 1055 <td>awk: Pattern-directed scanning and processing language</td>
ohair@13 1056 </tr>
ohair@13 1057 <tr>
ohair@13 1058 <td>file.exe</td>
ohair@13 1059 <td>Utils</td>
ohair@13 1060 <td>file: Determines file type using 'magic' numbers</td>
ohair@13 1061 </tr>
ohair@13 1062 <tr>
ohair@13 1063 <td>zip.exe</td>
ohair@13 1064 <td>Utils</td>
ohair@13 1065 <td>zip: Package and compress (archive) files</td>
ohair@13 1066 </tr>
ohair@13 1067 <tr>
ohair@13 1068 <td>unzip.exe</td>
ohair@13 1069 <td>Utils</td>
ohair@13 1070 <td>unzip: Extract compressed files in a ZIP archive</td>
ohair@13 1071 </tr>
ohair@13 1072 <tr>
ohair@13 1073 <td>free.exe</td>
ohair@13 1074 <td>Utils</td>
ohair@13 1075 <td>free: Display amount of free and used memory in the system</td>
ohair@13 1076 </tr>
ohair@13 1077 </tbody>
ohair@13 1078 </table>
ohair@13 1079 </blockquote>
ohair@13 1080 <p>
ohair@13 1081 Note that the CYGWIN software can conflict with other non-CYGWIN
ohair@13 1082 software on your Windows system.
ohair@13 1083 CYGWIN provides a
ohair@13 1084 <a href="" target="_blank">FAQ</a> for
ohair@13 1085 known issues and problems, of particular interest is the
ohair@13 1086 section on
ohair@13 1087 <a href="" target="_blank">
ohair@13 1088 BLODA (applications that interfere with CYGWIN)</a>.
ohair@13 1089 </blockquote>
ohair@13 1090 <strong><a name="dxsdk">Microsoft DirectX 9.0 SDK header files and libraries</a></strong>
duke@2 1091 <blockquote>
ohair@13 1092 Microsoft DirectX 9.0 SDK (Summer 2004)
ohair@13 1093 headers are required for building
ohair@13 1094 OpenJDK.
ohair@13 1095 This SDK can be downloaded from
ohair@13 1096 <a href=";displaylang=en" target="_blank">
ohair@13 1097 Microsoft DirectX 9.0 SDK (Summer 2004)</a>.
ohair@13 1098 If the link above becomes obsolete, the SDK can be found from
ohair@13 1099 <a href="" target="_blank">the Microsoft Download Site</a>
ohair@13 1100 (search with "DirectX 9.0 SDK Update Summer 2004").
ohair@13 1101 The location of this SDK can be set with
ohair@13 1102 <tt><a href="#ALT_DXSDK_PATH">ALT_DXSDK_PATH</a></tt>
ohair@13 1103 but it's normally found via the DirectX environment variable
ohair@13 1104 <tt>DXSDK_DIR</tt>.
ohair@13 1105 </blockquote>
ohair@13 1106 <strong><a name="msvcrt"><tt>MSVCRT.DLL</tt></a></strong>
ohair@13 1107 <blockquote>
ohair@13 1108 <strong>i586 only:</strong>
ohair@13 1109 The OpenJDK 32bit build requires access to
ohair@13 1110 <tt>MSVCRT.DLL</tt> version 6.00.8337.0 or newer.
ohair@13 1111 If the <tt>MSVCRT.DLL</tt> is not installed in
ohair@13 1112 the system32 directory set the
ohair@13 1113 <a href="#ALT_MSVCRT_DLL_PATH"><tt>ALT_MSVCRT_DLL_PATH</tt></a>
ohair@13 1114 variable to the location.
ohair@13 1115 <p>
ohair@13 1116 <strong>X64 only:</strong>
ohair@13 1117 The OpenJDK 64bit build requires access to
ohair@13 1118 <tt>MSVCRT.DLL</tt> version 7.0.3790.0 or newer, which is
ohair@13 1119 usually supplied by the
ohair@13 1120 <a href="#mssdk">Platform SDK</a>.
ohair@13 1121 If it is not available from the Platform SDK,
ohair@13 1122 set the
ohair@13 1123 <a href="#ALT_MSVCRT_DLL_PATH"><tt>ALT_MSVCRT_DLL_PATH</tt></a>
ohair@13 1124 variable to the location.
ohair@13 1125 </blockquote>
ohair@13 1126 <strong><tt><a name="msvcr71">MSVCR71.DLL</a></tt></strong>
ohair@13 1127 <blockquote>
ohair@13 1128 <strong>i586 only:</strong>
ohair@13 1129 The
ohair@13 1130 OpenJDK
ohair@13 1131 build requires access to
ohair@13 1132 MSVCR71.DLL version 7.10.3052.4 or newer which should be
ohair@13 1133 supplied by the
ohair@13 1134 <a href="#msvc">Visual Studio product</a>
ohair@13 1135 If the <tt>MSVCR71.DLL</tt> is not available from the
ohair@13 1136 Visual Studio product
ohair@13 1137 set the
ohair@13 1138 <a href="#ALT_MSVCR71_DLL_PATH"><tt>ALT_MSVCR71_DLL_PATH</tt></a>
ohair@13 1139 variable to the location.
duke@2 1140 </blockquote>
duke@2 1141 </blockquote>
ohair@13 1142 <!-- ------------------------------------------------------ -->
ohair@13 1143 <hr>
ohair@13 1144 <h2><a name="creating">Creating the Build</a></h2>
duke@2 1145 <blockquote>
ohair@13 1146 Once a machine is setup to build the OpenJDK,
ohair@13 1147 the steps to create the build are fairly simple.
ohair@13 1148 The various ALT settings can either be made into variables
ohair@13 1149 or can be supplied on the
ohair@13 1150 <a href="#gmake"><tt><i>gmake</i></tt></a>
ohair@13 1151 command.
ohair@13 1152 <ol>
ohair@13 1153 <li>Use the sanity rule to double check all the ALT settings:
ohair@13 1154 <blockquote>
ohair@13 1155 <tt>
ohair@13 1156 <i>gmake</i>
ohair@13 1157 sanity
ohair@13 1158 [ARCH_DATA_MODEL=<i>32 or 64</i>]
ohair@13 1159 [other "ALT_" overrides]
ohair@13 1160 </tt>
ohair@13 1161 </blockquote>
ohair@13 1162 </li>
ohair@13 1163 <li>Start the build with the command:
ohair@13 1164 <blockquote>
ohair@13 1165 <tt>
ohair@13 1166 <i>gmake</i>
ohair@13 1167 [ARCH_DATA_MODEL=<i>32 or 64</i>]
ohair@13 1168 [ALT_OUTPUTDIR=<i>output_directory</i>]
ohair@13 1169 [other "ALT_" overrides]
ohair@13 1170 </tt>
ohair@13 1171 </blockquote>
ohair@13 1172 </li>
ohair@13 1173 </ol>
duke@2 1174 <p>
ohair@13 1175 <strong>Solaris:</strong>
ohair@13 1176 Note that ARCH_DATA_MODEL is really only needed on Solaris to
ohair@13 1177 indicate you want to built the 64-bit version.
ohair@13 1178 And before the Solaris 64-bit binaries can be used, they
ohair@13 1179 must be merged with the binaries from a separate 32-bit build.
ohair@13 1180 The merged binaries may then be used in either 32-bit or 64-bit mode, with
ohair@13 1181 the selection occurring at runtime
ohair@13 1182 with the <tt>-d32</tt> or <tt>-d64</tt> options.
duke@2 1183 </blockquote>
ohair@13 1184 <!-- ------------------------------------------------------ -->
ohair@13 1185 <hr>
ohair@13 1186 <h2><a name="testing">Testing the Build</a></h2>
ohair@13 1187 <blockquote>
ohair@13 1188 When the build is completed, you should see the generated
ohair@13 1189 binaries and associated files in the <tt>j2sdk-image</tt>
ohair@13 1190 directory in the output directory.
ohair@13 1191 The default output directory is
ohair@13 1192 <tt>build/<i>platform</i></tt>,
ohair@13 1193 where <tt><i>platform</i></tt> is one of
ohair@13 1194 <tt><ul>
ohair@13 1195 <li>solaris-sparc</li>
ohair@13 1196 <li>solaris-sparcv9</li>
ohair@13 1197 <li>solaris-i586</li>
ohair@13 1198 <li>solaris-amd64</li>
ohair@13 1199 <li>linux-i586</li>
ohair@13 1200 <li>linux-amd64</li>
ohair@13 1201 <li>windows-i586</li>
ohair@13 1202 <li>windows-amd64</li>
ohair@13 1203 </ul></tt>
ohair@13 1204 In particular, the
ohair@13 1205 <tt>build/<i>platform</i>/j2sdk-image/bin</tt>
ohair@13 1206 directory should contain executables for the
ohair@13 1207 OpenJDK tools and utilities.
duke@2 1208 <p>
ohair@13 1209 You can test that the build completed properly by using the build
ohair@13 1210 to run the various demos that you will find in the
ohair@13 1211 <tt>build/<i>platform</i>/j2sdk-image/demo</tt>
ohair@13 1212 directory.
ohair@13 1213 <p>
ohair@13 1214 The provided regression tests can be run with the <tt>jtreg</tt>
ohair@13 1215 utility from
ohair@13 1216 <a href="" target="_blank">the jtreg site</a>.
duke@2 1217 </blockquote>
ohair@13 1218 <!-- ------------------------------------------------------ -->
ohair@13 1219 <hr>
ohair@13 1220 <h2><a name="variables">Environment/Make Variables</a></h2>
ohair@13 1221 <p>
ohair@13 1222 Some of the
ohair@13 1223 environment or make variables (just called <b>variables</b> in this
ohair@13 1224 document) that can impact the build are:
duke@2 1225 <blockquote>
duke@2 1226 <dl>
ohair@13 1227 <dt><a name="path"><tt>PATH</tt></a> </dt>
ohair@13 1228 <dd>Typically you want to set the <tt>PATH</tt> to include:
ohair@13 1229 <ul>
ohair@13 1230 <li>The location of the GNU make binary</li>
ohair@13 1231 <li>The location of the Bootstrap JDK <tt>java</tt>
ohair@13 1232 (see <a href="#bootjdk">Bootstrap JDK</a>)</li>
ohair@13 1233 <li>The location of the C/C++ compilers
ohair@13 1234 (see <a href="#compilers"><tt>compilers</tt></a>)</li>
ohair@13 1235 <li>The location or locations for the Unix command utilities
ohair@13 1236 (e.g. <tt>/usr/bin</tt>)</li>
ohair@13 1237 </ul>
ohair@13 1238 </dd>
ohair@13 1239 <dt><tt>MILESTONE</tt> </dt>
duke@2 1240 <dd>
ohair@13 1241 The milestone name for the build (<i>e.g.</i>"beta").
ohair@13 1242 The default value is "internal".
duke@2 1243 </dd>
ohair@13 1244 <dt><tt>BUILD_NUMBER</tt> </dt>
duke@2 1245 <dd>
ohair@13 1246 The build number for the build (<i>e.g.</i> "b27").
ohair@13 1247 The default value is "b00".
duke@2 1248 </dd>
ohair@13 1249 <dt><a name="arch_data_model"><tt>ARCH_DATA_MODEL</tt></a></dt>
ohair@13 1250 <dd>The <tt>ARCH_DATA_MODEL</tt> variable
ohair@13 1251 is used to specify whether the build is to generate 32-bit or 64-bit
ohair@13 1252 binaries.
ohair@13 1253 The Solaris build supports either 32-bit or 64-bit builds, but
ohair@13 1254 Windows and Linux will support only one, depending on the specific
ohair@13 1255 OS being used.
ohair@13 1256 Normally, setting this variable is only necessary on Solaris.
ohair@13 1257 Set <tt>ARCH_DATA_MODEL</tt> to <tt>32</tt> for generating 32-bit binaries,
ohair@13 1258 or to <tt>64</tt> for generating 64-bit binaries.
ohair@13 1259 </dd>
ohair@13 1260 <dt><a name="ALT_BOOTDIR"><tt>ALT_BOOTDIR</tt></a></dt>
duke@2 1261 <dd>
ohair@13 1262 The location of the bootstrap JDK installation.
ohair@13 1263 See <a href="#bootjdk">Bootstrap JDK</a> for more information.
ohair@13 1264 You should always install your own local Bootstrap JDK and
ohair@13 1265 always set <tt>ALT_BOOTDIR</tt> explicitly.
duke@2 1266 </dd>
ohair@13 1267 <dt><a name="ALT_BINARY_PLUGS_PATH"><tt>ALT_BINARY_PLUGS_PATH</tt></a></dt>
duke@2 1268 <dd>
ohair@13 1269 The location of the binary plugs installation.
ohair@13 1270 See <a href="#binaryplugs">Binary Plugs</a> for more information.
ohair@13 1271 You should always have a local copy of a
ohair@13 1272 recent Binary Plugs install image
ohair@13 1273 and set this variable to that location.
ohair@13 1274 </dd>
ohair@13 1275 <dt><a name="ALT_JDK_IMPORT_PATH"><tt>ALT_JDK_IMPORT_PATH</tt></a></dt>
ohair@13 1276 <dd>
ohair@13 1277 The location of a previously built JDK installation.
ohair@13 1278 See <a href="#importjdk">Optional Import JDK</a> for more information.
ohair@13 1279 </dd>
ohair@13 1280 <dt><a name="ALT_OUTPUTDIR"><tt>ALT_OUTPUTDIR</tt></a> </dt>
ohair@13 1281 <dd>
ohair@13 1282 An override for specifying the (absolute) path of where the
ohair@13 1283 build output is to go.
ohair@13 1284 The default output directory will be build/<i>platform</i>.
ohair@13 1285 </dd>
ohair@13 1286 <dt><a name="ALT_COMPILER_PATH"><tt>ALT_COMPILER_PATH</tt></a> </dt>
ohair@13 1287 <dd>
ohair@13 1288 The location of the C/C++ compiler.
ohair@13 1289 The default varies depending on the platform.
ohair@13 1290 </dd>
ohair@13 1291 <dt><tt><a name="ALT_CACERTS_FILE">ALT_CACERTS_FILE</a></tt></dt>
ohair@13 1292 <dd>
ohair@13 1293 The location of the <a href="#cacerts">cacerts</a> file.
ohair@13 1294 The default will refer to
ohair@13 1295 <tt>jdk/src/share/lib/security/cacerts</tt>.
ohair@13 1296 </dd>
ohair@13 1297 <dt><a name="ALT_CUPS_HEADERS_PATH"><tt>ALT_CUPS_HEADERS_PATH</tt></a> </dt>
ohair@13 1298 <dd>
ohair@13 1299 The location of the CUPS header files.
ohair@13 1300 See <a href="#cups">CUPS information</a> for more information.
ohair@13 1301 If this path does not exist the fallback path is
ohair@13 1302 <tt>/usr/include</tt>.
ohair@13 1303 </dd>
ohair@13 1304 <dt><a name="ALT_FREETYPE_LIB_PATH"><tt>ALT_FREETYPE_LIB_PATH</tt></a></dt>
ohair@13 1305 <dd>
ohair@13 1306 The location of the FreeType shared library.
ohair@13 1307 See <a href="#freetype">FreeType information</a> for details.
ohair@13 1308 </dd>
ohair@13 1309 <dt><a name="ALT_FREETYPE_HEADERS_PATH"><tt>ALT_FREETYPE_HEADERS_PATH</tt></a></dt>
ohair@13 1310 <dd>
ohair@13 1311 The location of the FreeType header files.
ohair@13 1312 See <a href="#freetype">FreeType information</a> for details.
ohair@13 1313 </dd>
ohair@13 1314 <dt><a name="ALT_JDK_DEVTOOLS_PATH"><tt>ALT_JDK_DEVTOOLS_PATH</tt></a></dt>
ohair@13 1315 <dd>
ohair@13 1316 The default root location of the devtools.
ohair@13 1317 The default value is
ohair@13 1318 <tt>$(ALT_SLASH_JAVA)/devtools</tt>.
ohair@13 1319 </dd>
ohair@13 1320 <dt><tt><a name="ALT_DEVTOOLS_PATH">ALT_DEVTOOLS_PATH</a></tt> </dt>
ohair@13 1321 <dd>
ohair@13 1322 The location of tools like the
ohair@13 1323 <a href="#zip"><tt>zip</tt> and <tt>unzip</tt></a>
ohair@13 1324 binaries, but might also contain the GNU make utility
ohair@13 1325 (<tt><i>gmake</i></tt>).
ohair@13 1326 So this area is a bit of a grab bag, especially on Windows.
ohair@13 1327 The default value depends on the platform and
ohair@13 1328 Unix Commands being used.
ohair@13 1329 On Linux the default will be
ohair@13 1330 <tt>$(ALT_JDK_DEVTOOLS_PATH)/linux/bin</tt>,
ohair@13 1331 on Solaris
ohair@13 1332 <tt>$(ALT_JDK_DEVTOOLS_PATH)/<i>{sparc,i386}</i>/bin</tt>,
ohair@13 1333 on Windows with MKS
ohair@13 1334 <tt>%SYSTEMDRIVE%/UTILS</tt>,
ohair@13 1335 and on Windows with CYGWIN
ohair@13 1336 <tt>/usr/bin</tt>.
ohair@13 1337 </dd>
ohair@13 1338 <dt><a name="ALT_UNIXCOMMAND_PATH"><tt>ALT_UNIXCOMMAND_PATH</tt></a> </dt>
ohair@13 1339 <dd>
ohair@13 1340 An override for specifying where the
ohair@13 1341 Unix command set are located.
ohair@13 1342 The default location varies depending on the platform,
ohair@13 1343 <tt>"%SYSTEMDRIVE%/MKSNT"</tt> or
ohair@13 1344 <tt>$(ROOTDIR)</tt> on Windows with MKS, otherwise it's
ohair@13 1345 <tt>"/bin"</tt> or <tt>/usr/bin</tt>.
ohair@13 1346 </dd>
ohair@13 1347 <dt><a name="ALT_UNIXCCS_PATH"><tt>ALT_UNIXCCS_PATH</tt></a></dt>
ohair@13 1348 <dd>
ohair@13 1349 <strong>Solaris only:</strong>
ohair@13 1350 An override for specifying where the Unix CCS
ohair@13 1351 command set are located.
ohair@13 1352 The default location is <tt>/usr/ccs/bin</tt>
ohair@13 1353 </dd>
ohair@13 1354 <dt><a name="ALT_USRBIN_PATH"><tt>ALT_USRBIN_PATH</tt></a></dt>
ohair@13 1355 <dd>
ohair@13 1356 An override for specifying where the
ohair@13 1357 Unix <tt>/usr/bin</tt> commands are located. You usually do not need
ohair@13 1358 to set this variable: the default location is <tt>/usr/bin</tt>)
ohair@13 1359 </dd>
ohair@13 1360 <dt><a name="ALT_SLASHJAVA"><tt>ALT_SLASHJAVA</tt></a></dt>
ohair@13 1361 <dd>
ohair@13 1362 The default root location for many of the ALT path locations
ohair@13 1363 of the following ALT variables.
ohair@13 1364 The default value is
ohair@13 1365 <tt>"/java"</tt> on Solaris and Linux,
ohair@13 1366 <tt>"J:"</tt> on Windows.
ohair@13 1367 </dd>
ohair@13 1368 <dt><a name="ALT_BUILD_JDK_IMPORT_PATH"><tt>ALT_BUILD_JDK_IMPORT_PATH</tt></a></dt>
ohair@13 1369 <dd>
ohair@13 1370 These are useful in managing builds on multiple platforms.
ohair@13 1371 The default network location for all of the import JDK images
ohair@13 1372 for all platforms.
ohair@13 1373 If <tt><a href="#ALT_JDK_IMPORT_PATH">ALT_JDK_IMPORT_PATH</a></tt>
ohair@13 1374 is not set, this directory will be used and should contain
ohair@13 1375 the following directories:
ohair@13 1376 <tt>solaris-sparc</tt>,
ohair@13 1377 <tt>solaris-i586</tt>,
ohair@13 1378 <tt>solaris-sparcv9</tt>,
ohair@13 1379 <tt>solaris-amd64</tt>,
ohair@13 1380 <tt>linux-i586</tt>,
ohair@13 1381 <tt>linux-amd64</tt>,
ohair@13 1382 <tt>windows-i586</tt>,
ohair@13 1383 and
ohair@13 1384 <tt>windows-amd64</tt>.
ohair@13 1385 Where each of these directories contain the import JDK image
ohair@13 1386 for that platform.
ohair@13 1387 </dd>
ohair@13 1388 <dt><a name="ALT_BUILD_BINARY_PLUGS_PATH"><tt>ALT_BUILD_BINARY_PLUGS_PATH</tt></a></dt>
ohair@13 1389 <dd>
ohair@13 1390 These are useful in managing builds on multiple platforms.
ohair@13 1391 The default network location for all of the binary plug images
ohair@13 1392 for all platforms.
ohair@13 1393 If <tt><a href="#ALT_BINARY_PLUGS_PATH">ALT_BINARY_PLUGS_PATH</a></tt>
ohair@13 1394 is not set, this directory will be used and should contain
ohair@13 1395 the following directories:
ohair@13 1396 <tt>solaris-sparc</tt>,
ohair@13 1397 <tt>solaris-i586</tt>,
ohair@13 1398 <tt>solaris-sparcv9</tt>,
ohair@13 1399 <tt>solaris-amd64</tt>,
ohair@13 1400 <tt>linux-i586</tt>,
ohair@13 1401 <tt>linux-amd64</tt>,
ohair@13 1402 <tt>windows-i586</tt>,
ohair@13 1403 and
ohair@13 1404 <tt>windows-amd64</tt>.
ohair@13 1405 Where each of these directories contain the binary plugs image
ohair@13 1406 for that platform.
ohair@13 1407 </dd>
ohair@13 1408 <dt><strong>Windows specific:</strong></dt>
ohair@13 1409 <dd>
ohair@13 1410 <dl>
ohair@13 1411 <dt><a name="ALT_MSDEVTOOLS_PATH"><tt>ALT_MSDEVTOOLS_PATH</tt></a> </dt>
ohair@13 1412 <dd>
ohair@13 1413 The location of the Microsoft Visual Studio .NET 2003
ohair@13 1414 tools 'bin' directory.
ohair@13 1415 The default is usually derived from
ohair@13 1416 <a href="#ALT_COMPILER_PATH"><tt>ALT_COMPILER_PATH</tt></a>.
ohair@13 1417 </dd>
ohair@13 1418 <dt><tt><a name="ALT_DXSDK_PATH">ALT_DXSDK_PATH</a></tt> </dt>
ohair@13 1419 <dd>
ohair@13 1420 The location of the
ohair@13 1421 <a href="#dxsdk">Microsoft DirectX 9 SDK</a>.
ohair@13 1422 The default will be to try and use the DirectX environment
ohair@13 1423 variable <tt>DXSDK_DIR</tt>,
ohair@13 1424 failing that, look in <tt>C:/DXSDK</tt>.
ohair@13 1425 </dd>
ohair@13 1426 <dt><tt><a name="ALT_MSVCRT_DLL_PATH">ALT_MSVCRT_DLL_PATH</a></tt> </dt>
ohair@13 1427 <dd>
ohair@13 1428 The location of the
ohair@13 1429 <a href="#msvcrt"><tt>MSVCRT.DLL</tt></a>.
ohair@13 1430 </dd>
ohair@13 1431 <dt><tt><a name="ALT_MSVCR71_DLL_PATH">ALT_MSVCR71_DLL_PATH</a></tt> </dt>
ohair@13 1432 <dd>
ohair@13 1433 <strong>i586 only:</strong>
ohair@13 1434 The location of the
ohair@13 1435 <a href="#msvcr71"><tt>MSVCR71.DLL</tt></a>.
ohair@13 1436 </dd>
ohair@13 1437 </dl>
duke@2 1438 </dd>
duke@2 1439 </dl>
ohair@13 1440 </blockquote>
ohair@13 1441 <!-- ------------------------------------------------------ -->
ohair@13 1442 <hr>
ohair@13 1443 <h2><a name="troubleshooting">Troubleshooting</a></h2>
ohair@13 1444 <blockquote>
ohair@13 1445 A build can fail for any number of reasons.
ohair@13 1446 Most failures
ohair@13 1447 are a result of trying to build in an environment in which all the
ohair@13 1448 pre-build requirements have not been met.
ohair@13 1449 The first step in
ohair@13 1450 troubleshooting a build failure is to recheck that you have satisfied
ohair@13 1451 all the pre-build requirements for your platform.
ohair@13 1452 Look for the check list of the platform you are building on in the
ohair@13 1453 <a href="#contents">Table of Contents</a>.
ohair@13 1454 <p>
ohair@13 1455 You can validate your build environment by using the <tt>sanity</tt>
ohair@13 1456 target.
ohair@13 1457 Any errors listed
ohair@13 1458 will stop the build from starting, and any warnings may result in
ohair@13 1459 a flawed product build.
ohair@13 1460 We strongly encourage you to evaluate every
ohair@13 1461 sanity check warning and fix it if required, before you proceed
ohair@13 1462 further with your build.
ohair@13 1463 <p>
ohair@13 1464 Some of the more common problems with builds are briefly described
ohair@13 1465 below, with suggestions for remedies.
ohair@13 1466 <ul>
ohair@13 1467 <li>
ohair@13 1468 <b>Slow Builds:</b>
ohair@13 1469 <blockquote>
ohair@13 1470 If your build machine seems to be overloaded from too many
ohair@13 1471 simultaneous C++ compiles, try setting the <tt>HOTSPOT_BUILD_JOBS</tt>
ohair@13 1472 variable to <tt>1</tt> (if you're using a multiple CPU
ohair@13 1473 machine, setting it to more than the the number of CPUs is probably
ohair@13 1474 not a good idea).
ohair@13 1475 <p>
ohair@13 1476 Creating the javadocs can be very slow, if you are running
ohair@13 1477 javadoc, consider skipping that step.
ohair@13 1478 <p>
ohair@13 1479 Faster hardware and more RAM always helps too.
ohair@13 1480 The VM build tends to be CPU intensive (many C++ compiles),
ohair@13 1481 and the rest of the JDK will often be disk intensive.
ohair@13 1482 <p>
ohair@13 1483 Faster compiles are possible using a tool called
ohair@13 1484 <a href="" target="_blank">ccache</a>.
ohair@13 1485 </blockquote>
ohair@13 1486 </li>
ohair@13 1487 <li>
ohair@13 1488 <b>File time issues:</b>
ohair@13 1489 <blockquote>
ohair@13 1490 If you see warnings that refer to file time stamps, e.g.
ohair@13 1491 <blockquote>
ohair@13 1492 <i>Warning message:</i><tt> File `xxx' has modification time in
ohair@13 1493 the future.</tt>
ohair@13 1494 <br>
ohair@13 1495 <i>Warning message:</i> <tt> Clock skew detected. Your build may
ohair@13 1496 be incomplete.</tt>
ohair@13 1497 </blockquote>
ohair@13 1498 These warnings can occur when the clock on the build machine is out of
ohair@13 1499 sync with the timestamps on the source files. Other errors, apparently
ohair@13 1500 unrelated but in fact caused by the clock skew, can occur along with
ohair@13 1501 the clock skew warnings. These secondary errors may tend to obscure the
ohair@13 1502 fact that the true root cause of the problem is an out-of-sync clock.
ohair@13 1503 For example, an out-of-sync clock has been known to cause an old
ohair@13 1504 version of javac to be used to compile some files, resulting in errors
ohair@13 1505 when the pre-1.4 compiler ran across the new <tt>assert</tt> keyword
ohair@13 1506 in the 1.4 source code.
ohair@13 1507 <p>
ohair@13 1508 If you see these warnings, reset the clock on the build
ohair@13 1509 machine, run "<tt><i>gmake</i> clobber</tt>" or delete the directory
ohair@13 1510 containing the build output, and restart the build from the beginning.
ohair@13 1511 </blockquote>
ohair@13 1512 </li>
ohair@13 1513 <li>
ohair@13 1514 <b>Error message: <tt>Trouble writing out table to disk</tt></b>
ohair@13 1515 <blockquote>
ohair@13 1516 Increase the amount of swap space on your build machine.
ohair@13 1517 </blockquote>
ohair@13 1518 </li>
ohair@13 1519 <li>
ohair@13 1520 <b>Error Message: <tt>libstdc++ not found:</tt></b>
ohair@13 1521 <blockquote>
ohair@13 1522 This is caused by a missing libstdc++.a library.
ohair@13 1523 This is installed as part of a specific package
ohair@13 1524 (e.g.
ohair@13 1525 By default some 64bit Linux versions (e.g. Fedora)
ohair@13 1526 only install the 64bit version of the libstdc++ package.
ohair@13 1527 Various parts of the JDK build require a static
ohair@13 1528 link of the C++ runtime libraries to allow for maximum
ohair@13 1529 portability of the built images.
ohair@13 1530 </blockquote>
ohair@13 1531 </li>
ohair@13 1532 <li>
ohair@13 1533 <b>Error Message: <tt>cannot restore segment prot after reloc</tt></b>
ohair@13 1534 <blockquote>
ohair@13 1535 This is probably an issue with SELinux (See
ohair@13 1536 <a href="" target="_blank">
ohair@13 1537</a>).
ohair@13 1538 Parts of the VM is built without the <tt>-fPIC</tt> for
ohair@13 1539 performance reasons.
ohair@13 1540 <p>
ohair@13 1541 To completely disable SELinux:
ohair@13 1542 <tt>
ohair@13 1543 <ol>
ohair@13 1544 <li>$ su root</li>
ohair@13 1545 <li># system-config-securitylevel</li>
ohair@13 1546 <li>In the window that appears, select the SELinux tab</li>
ohair@13 1547 <li>Disable SELinux</li>
ohair@13 1548 </ol>
ohair@13 1549 </tt>
ohair@13 1550 <p>
ohair@13 1551 Alternatively, instead of completely disabling it you could
ohair@13 1552 disable just this one check.
ohair@13 1553 <tt>
ohair@13 1554 <ol>
ohair@13 1555 <li>Select System->Administration->SELinux Management</li>
ohair@13 1556 <li>In the SELinux Management Tool which appears,
ohair@13 1557 select "Boolean" from the menu on the left</li>
ohair@13 1558 <li>Expand the "Memory Protection" group</li>
ohair@13 1559 <li>Check the first item, labeled
ohair@13 1560 "Allow all unconfined executables to use libraries requiring text relocation ..."</li>
ohair@13 1561 </ol>
ohair@13 1562 </tt>
ohair@13 1563 </blockquote>
ohair@13 1564 </li>
ohair@13 1565 <li>
ohair@13 1566 <b>Windows Error Message: <tt>*** fatal error - couldn't allocate heap, ... </tt></b>
ohair@13 1567 <blockquote>
ohair@13 1568 The CYGWIN software can conflict with other non-CYGWIN
ohair@13 1569 software. See the CYGWIN FAQ section on
ohair@13 1570 <a href="" target="_blank">
ohair@13 1571 BLODA (applications that interfere with CYGWIN)</a>.
ohair@13 1572 </blockquote>
ohair@13 1573 </li>
ohair@13 1574 <li>
ohair@13 1575 <b>Windows Error Message: <tt>*** multiple target patterns. Stop.</tt></b>
ohair@13 1576 <blockquote>
ohair@13 1577 The CYGWIN make version 3.81 may not like the Windows <tt>C:/</tt>
ohair@13 1578 style paths, it may not like the ':' character in the path
ohair@13 1579 when used in a makefile target definition.
ohair@13 1580 See the <a href="#gmake"><tt><i>gmake</i></tt></a> section.
ohair@13 1581 </blockquote>
ohair@13 1582 </li>
ohair@13 1583 </ul>
ohair@13 1584 </blockquote>
ohair@13 1585 <hr>
ohair@13 1586 </body>
ohair@13 1587 </html>