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