source: trunk/openjdk/README-builds.html@ 339

Last change on this file since 339 was 309, checked in by dmik, 14 years ago

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