annotate README-builds.html @ 40:1d9112b073d7

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