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