annotate README-builds.html @ 130:3ac6dcf78232

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