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