Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / libcore / e53e767d885963bd6063671ce322f796759f3531 / . / README-builds.html
blob: 096d192e2b986ef781f72307ef4919a24e7b917c [file] [log] [blame]
J. Duke686d76f2007-12-01 00:00:00 +0000[diff] [blame]1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2
3<html>
4<head><title>OpenJDK Build README</title></head>
5
6<!-- ------------------------------------------------------ -->
7<hr noshade="noshade" size="3">
8
9<center>
10 <h1>OpenJDK Build README</h1>
11</center>
12
13<!-- ------------------------------------------------------ -->
14<hr noshade="noshade" size="3">
15
16<h2><a name="introduction">Introduction</a></h2>
17
18<blockquote>
19 <p>
20 This README file contains build instructions for the
21 <a href="http://openjdk.java.net">OpenJDK</a>.
22 Building the source code for the
23 OpenJDK
24 requires
25 a certain degree of technical expertise.
26</blockquote>
27
28<!-- ------------------------------------------------------ -->
29<hr noshade="noshade" size="3">
30
31<h2><a name="contents">Contents</a></h2>
32
33<blockquote>
34 <ul>
35 <li><a href="#introduction">Introduction</a></li>
36 <li><a href="#MBE">Minimum Build Environments</a></li>
37 <li><a href="#SDBE">Specific Developer Build Environments</a></li>
38 <li><a href="#directories">Source Directory Structure</a> </li>
39 <li><a href="#building">Build Information</a>
40 <ul type="disc">
41 <li><a href="#gmake">GNU Make (<tt><i>gmake</i></tt>)</a> </li>
42 <li><a href="#linux">Basic Linux System Setup</a> </li>
43 <li><a href="#solaris">Basic Solaris System Setup</a> </li>
44 <li><a href="#windows">Basic Windows System Setup</a> </li>
45 <li><a href="#dependencies">Build Dependencies</a> </li>
46 <ul type="disc">
47 <li><a href="#bootjdk">Bootstrap JDK</a> </li>
48 <li><a href="#binaryplugs">Binary Plugs</a> </li>
49 <li><a href="#cacerts">Certificate Authority File (cacert)</a> </li>
50 <li><a href="#compilers">Compilers</a>
51 <ul>
52 <li><a href="#msvc">Microsoft Visual Studio</a> </li>
53 <li><a href="#mssdk">Microsoft Platform SDK</a> </li>
54 <li><a href="#gcc">Linux gcc/binutils</a> </li>
55 <li><a href="#studio">Sun Studio</a> </li>
56 </ul>
57 </li>
58 <li>Linux and Solaris:
59 <ul>
60 <li><a href="#cups">CUPS Include files</a> </li>
61 </ul>
62 </li>
63 <li>Windows only:
64 <ul>
65 <li>Unix Command Tools (<a href="#cygwin">CYGWIN</a>)</li>
66 <li><a href="#dxsdk">DirectX 9.0 SDK</a> </li>
67 </ul>
68 </li>
69 </ul>
70 </ul>
71 </li>
72 <li><a href="#creating">Creating the Build</a> </li>
73 <li><a href="#testing">Testing the Build</a> </li>
74 <li><a href="#variables">Environment/Make Variables</a></li>
75 <li><a href="#troubleshooting">Troubleshooting</a></li>
76 </ul>
77</blockquote>
78
79<!-- ------------------------------------------------------ -->
80<hr noshade="noshade" size="3">
81
82<h2><a name="MBE">Minimum Build Environments</a></h2>
83
84<blockquote>
85 <p>
86 This file often describes specific requirements for what we call the
87 "minimum build environments" (MBE) for the JDK.
88 Building with the MBE will generate the most compatible
89 bits that install on, and run correctly on, the most variations
90 of the same base OS and hardware architecture.
91 These usually represent what is often called the
92 least common denominator platforms.
93 It is understood that most developers will NOT be using these
94 specific platforms, and in fact creating these specific platforms
95 may be difficult due to the age of some of this software.
96 <p>
97
98 <p>
99 The minimum OS and C/C++ compiler versions needed for building the
100 OpenJDK:
101 <p>
102 <center>
103 <table border="1">
104 <thead>
105 <tr>
106 <th>Base OS and Architecture</th>
107 <th>OS</th>
108 <th>Compiler</th>
109 </tr>
110 </thead>
111 <tbody>
112 <tr>
113 <td>Linux X86 (32bit)</td>
114 <td>Red Hat Enterprise Linux 4 </td>
115 <td>gcc 4 </td>
116 </tr>
117 <tr>
118 <td>Linux X64 (64bit)</td>
119 <td>Red Hat Enterprise Linux 4 </td>
120 <td>gcc 4 </td>
121 </tr>
122 <tr>
123 <td>Solaris SPARC (32bit)</td>
124 <td>Solaris 10 + patches
125 <br>
126 See <a href="http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/JavaSE">SunSolve</a> for patch downloads.
127 </td>
128 <td>Sun Studio 11 </td>
129 </tr>
130 <tr>
131 <td>Solaris SPARCV9 (64bit)</td>
132 <td>Solaris 10 + patches
133 <br>
134 See <a href="http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/JavaSE">SunSolve</a> for patch downloads.
135 </td>
136 <td>Sun Studio 11</td>
137 </tr>
138 <tr>
139 <td>Solaris X86 (32bit)</td>
140 <td>Solaris 10 + patches
141 <br>
142 See <a href="http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/JavaSE">SunSolve</a> for patch downloads.
143 </td>
144 <td>Sun Studio 11</td>
145 </tr>
146 <tr>
147 <td>Solaris X64 (64bit)</td>
148 <td>Solaris 10 + patches
149 <br>
150 See <a href="http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/JavaSE">SunSolve</a> for patch downloads.
151 </td>
152 <td>Sun Studio 11</td>
153 </tr>
154 <tr>
155 <td>Windows X86 (32bit)</td>
156 <td>Windows XP</td>
157 <td>Microsoft Visual Studio .NET 2003 Professional</td>
158 </tr>
159 <tr>
160 <td>Windows X64 (64bit)</td>
161 <td>Windows Server 2003 - Enterprise x64 Edition</td>
162 <td>Microsoft Platform SDK - April 2005</td>
163 </tr>
164 </tbody>
165 </table>
166 </center>
167</blockquote>
168
169<!-- ------------------------------------------------------ -->
170<hr noshade="noshade" size="3">
171
172<h2><a name="SDBE">Specific Developer Build Environments</a></h2>
173
174<blockquote>
175 <p>
176 We won't be listing all the possible environments, but
177 we will try to provide what information we have available to us.
178</blockquote>
179
180<h3><a name="fedora">Fedora</a></h3>
181
182<blockquote>
183 TBD
184</blockquote>
185
186<h3><a name="debian">Debian</a></h3>
187
188<blockquote>
189 TBD
190</blockquote>
191
192<h3><a name="ubuntu">Ubuntu</a></h3>
193
194<blockquote>
195 <p>
196 In addition to needing the Bootstrap JDK and the Binary Plugs,
197 when building on Ubuntu you will need to
198 make sure certain packages are installed.
199 In particular, certain X11 packages, make, m4, gawk, gcc 4,
200 binutils, cups, freetype
201 and alsa.
202
203 <h4>Ubuntu 6.06</h4>
204
205 <p>
206 The following list of packages for Ubuntu 6.06 is a working set that
207 does appear to work.
208
209 <p>
210 <b>Note that it's quite possible that some of these
211 packages are not required, so anyone discovering that some of the
212 packages listed below are NOT required,
213 please let the
214 OpenJDK
215 team know.</b>
216 <p>
217 All the packages below can be installed with the
218 Synaptic Package manager provided with the base Ubuntu 6.06 release.
219
220 <blockquote>
221 <ul>
222 <li>binutils (2.16.1cvs20060117-1ubuntu2.1)</li>
223 <li>cpp (4:4.0.3-1)</li>
224 <li>cpp-4.0 (4.0.3-1ubuntu5)</li>
225 <li>libfreetype6-dev</li>
226 <li>g++ (4:4.0.3-1)</li>
227 <li>g++-4.0 (4.0.3-1ubuntu5)</li>
228 <li>gawk (1:3.1.5-2build1)</li>
229 <li>gcc (4:4.0.3-1)</li>
230 <li>gcc-4.0 (4.0.3-1ubuntu5)</li>
231 <li>libasound2-dev (1.0.10-2ubuntu4)</li>
232 <li>libc6 (2.3.6-0ubuntu20) to 2.3.6-0ubuntu20.4</li>
233 <li>libc6-dev (2.3.6-0ubuntu20.4)</li>
234 <li>libc6-i686 (2.3.6-0ubuntu20) to 2.3.6-0ubuntu20.4</li>
235 <li>libcupsys2-dev (1.2.2-0ubuntu0.6.06)</li>
236 <li>libgcrypt11-dev (1.2.2-1)</li>
237 <li>libgnutls-dev (1.2.9-2ubuntu1.1)</li>
238 <li>libgnutls12 (1.2.9-2ubuntu1) to 1.2.9-2ubuntu1.1</li>
239 <li>libgpg-error-dev (1.1-4)</li>
240 <li>libice-dev (2:1.0.0-0ubuntu2)</li>
241 <li>liblockfile1 (1.06.1)</li>
242 <li>libopencdk8-dev (0.5.7-2)</li>
243 <li>libpopt-dev (1.7-5)</li>
244 <li>libsm-dev (2:1.0.0-0ubuntu2)</li>
245 <li>libstdc++6-4.0-dev (4.0.3-1ubuntu5)</li>
246 <li>libtasn1-2-dev (0.2.17-1ubuntu1)</li>
247 <li>libx11-dev (2:1.0.0-0ubuntu9)</li>
248 <li>libxau-dev (1:1.0.0-0ubuntu4)</li>
249 <li>libxaw-headers (2:1.0.1-0ubuntu3)</li>
250 <li>libxaw7-dev (2:1.0.1-0ubuntu3)</li>
251 <li>libxdmcp-dev (1:1.0.0-0ubuntu2)</li>
252 <li>libxext-dev (2:1.0.0-0ubuntu4)</li>
253 <li>libxi-dev (2:1.0.0-0ubuntu3) </li>
254 <li>libxmu-dev (2:1.0.0-0ubuntu3)</li>
255 <li>libxmu-headers (2:1.0.0-0ubuntu3)</li>
256 <li>libxmuu-dev (2:1.0.0-0ubuntu3)</li>
257 <li>libxp-dev (6.8.2-11ubuntu2)</li>
258 <li>libxpm-dev (1:3.5.4.2-0ubuntu3)</li>
259 <li>libxrandr-dev (1:1.1.0.2-0ubuntu4)</li>
260 <li>libxt-dev (1:1.0.0-0ubuntu3)</li>
261 <li>libxtrap-dev (2:1.0.0-0ubuntu2)</li>
262 <li>libxtst-dev (2:1.0.1-0ubuntu2)</li>
263 <li>libxv-dev (2:1.0.1-0ubuntu3)</li>
264 <li>linux-kernel-headers (2.6.11.2-0ubuntu18)</li>
265 <li>m4 (1.4.4-1)</li>
266 <li>make (3.80+3.81.b4-1)</li>
267 <li>ssl-cert (1.0.13)</li>
268 <li>x-dev (7.0.4-0ubuntu2)</li>
269 <li>x11proto-core-dev (7.0.4-0ubuntu2)</li>
270 <li>x11proto-input-dev (1.3.2-0ubuntu2)</li>
271 <li>x11proto-kb-dev (1.0.2-0ubuntu2)</li>
272 <li>x11proto-randr-dev (1.1.2-0ubuntu2)</li>
273 <li>x11proto-record-dev (1.13.2-0ubuntu2)</li>
274 <li>x11proto-trap-dev (3.4.3-0ubuntu2)</li>
275 <li>x11proto-video-dev (2.2.2-0ubuntu2)</li>
276 <li>x11proto-xext-dev (7.0.2-0ubuntu2)</li>
277 <li>xlibs-dev (7.0.0-0ubuntu45)</li>
278 <li>zlib1g-dev (1:1.2.3-6ubuntu4)</li>
279 </ul>
280 </blockquote>
281
282 <h4>Ubuntu 7.04</h4>
283
284 <p>
285 Using the Synaptic Package Manager, download the following
286 packages (double indented packages are automatically aquired
287 due to package dependencies):
288
289 <blockquote>
290 <ul>
291 <li>build-essential</li>
292 <ul>
293 <li>dpkg-dev</li>
294 <li>g++</li>
295 <li>g++-4.1</li>
296 <li>libc6-dev</li>
297 <li>libstdc++6.4.1-dev</li>
298 <li>linux-libc-dev</li>
299 </ul>
300 <li>gawk</li>
301 <li>m4</li>
302 <li>libasound2-dev</li>
303 <li>libcupsys2-dev</li>
304 <ul>
305 <li>libgcrypt11-dev</li>
306 <li>lgnutls-dev</li>
307 <li>libgpg-error-dev</li>
308 <li>liblzo-dev</li>
309 <li>libopencdk8-dev</li>
310 <li>libpopt-dev</li>
311 <li>libtasn1-3-dev</li>
312 <li>zlib1g-dev</li>
313 </ul>
314 <li>sun-java6-jdk</li>
315 <ul>
316 <li>java-common</li>
317 <li>libltdl3</li>
318 <li>odbcinst1debian1</li>
319 <li>sun-java6-bin</li>
320 <li>sun-java6-jre</li>
321 <li>unixodbc</li>
322 </ul>
323 <li>xlibs-dev</li>
324 <ul>
325 <li>(many)</li>
326 </ul>
327 <li>x11proto-print-dev</li>
328 <li>libxaw7-dev</li>
329 <ul>
330 <li>libxaw-headers</li>
331 </ul>
332 <li>libxp-dev</li>
333 <li>libfreetype6-dev</li>
334 </ul>
335 </blockquote>
336</blockquote>
337
338<!-- ------------------------------------------------------ -->
339<hr noshade="noshade" size="3">
340
341<h2><a name="directories">Source Directory Structure</a></h2>
342
343<blockquote>
344 <p>
Kelly O'Haird8e9d222008-03-05 18:56:03 -0800[diff] [blame]345 The source code for the OpenJDK is delivered in a set of
346 directories:
J. Duke686d76f2007-12-01 00:00:00 +0000[diff] [blame]347 <tt>hotspot</tt>,
348 <tt>langtools</tt>,
349 <tt>corba</tt>,
350 <tt>jaxws</tt>,
351 <tt>jaxp</tt>,
J. Duke686d76f2007-12-01 00:00:00 +0000[diff] [blame]352 and
Kelly O'Haird8e9d222008-03-05 18:56:03 -0800[diff] [blame]353 <tt>jdk</tt>.
J. Duke686d76f2007-12-01 00:00:00 +0000[diff] [blame]354 The <tt>hotspot</tt> directory contains the source code and make
Kelly O'Haird8e9d222008-03-05 18:56:03 -0800[diff] [blame]355 files for building the OpenJDK Hotspot Virtual Machine.
356 The <tt>langtools</tt> directory contains the source code and make
357 files for building the OpenJDK javac and language tools.
358 The <tt>corba</tt> directory contains the source code and make
359 files for building the OpenJDK Corba files.
360 The <tt>jaxws</tt> directory contains the source code and make
361 files for building the OpenJDK JAXWS files.
362 The <tt>jaxp</tt> directory contains the source code and make
363 files for building the OpenJDK JAXP files.
364 The <tt>jdk</tt> directory contains the source code and make files for
365 building the OpenJDK runtime libraries and misc files.
366 The top level <tt>Makefile</tt>
367 is used to build the entire OpenJDK.
J. Duke686d76f2007-12-01 00:00:00 +0000[diff] [blame]368</blockquote>
369
370<!-- ------------------------------------------------------ -->
371<hr noshade="noshade" size="3">
372
373<h2><a name="building">Build Information</a></h2>
374
375<blockquote>
376 <p>
377 Building the
378 OpenJDK
379 is done with a <tt><i>gmake</i></tt>
380 command line and various
381 environment or make variable settings that direct the make rules
382 to where various components have been installed.
383 Where possible the makefiles will attempt to located the various
384 components in the default locations or any component specific
385 variable settings.
386 When the normal defaults fail or components cannot be found,
387 the various
388 <tt>ALT_*</tt> variables (alternates)
389 can be used to help the makefiles locate components.
390 <p>
391 Refer to the bash/sh/ksh setup file
392 <tt>jdk/make/jdk_generic_profile.sh</tt>
393 if you need help in setting up your environment variables.
394 A build could be as simple as:
395 <blockquote>
396 <pre><tt>
397 bash
398 . jdk/make/jdk_generic_profile.sh
399 <i>gmake</i> sanity &amp;&amp; <i>gmake</i>
400 </tt></pre>
401 </blockquote>
402 <p>
403 Of course ksh or sh would work too.
404 But some customization will probably be necessary.
405 The <tt>sanity</tt> rule will make some basic checks on build
406 dependencies and generate appropriate warning messages
407 regarding missing, out of date, or newer than expected components
408 found on your system.
409</blockquote>
410
411<!-- ------------------------------------------------------ -->
412<hr noshade="noshade" size="3">
413
414<h3><a name="gmake">GNU make (<tt><i>gmake</i></tt>)</a></h3>
415
416<blockquote>
417 <p>
418 The Makefiles in the
419 OpenJDK
420 are only valid when used with the
421 GNU version of the utility command <tt>make</tt>
422 (<tt><i>gmake</i></tt>).
423 A few notes about using GNU make:
424 <ul>
425 <li>
426 In general, you need GNU make version 3.78.1 or newer.
427 </li>
428 <li>
429 Place the location of the GNU make binary in the <tt>PATH</tt>.
430 </li>
431 <li>
432 <strong>Linux:</strong>
433 The <tt>/usr/bin/make</tt> command should work fine for you.
434 </li>
435 <li>
436 <strong>Solaris:</strong>
437 Do NOT use <tt>/usr/bin/make</tt> on Solaris.
438 If your Solaris system has the software
439 from the Solaris Companion CD installed,
440 you should use <tt>gmake</tt>
441 which will be located in either the <tt>/opt/sfw/bin</tt> or
442 <tt>/usr/sfw/bin</tt> directory.
443 </li>
444 <li>
445 <strong>Windows:</strong>
446 Make sure you start your build inside a bash/sh/ksh shell.
447 <br>
448 <b>WARNING:</b> Watch out for make version 3.81, it may
449 not work due to a lack of support for drive letter paths
450 like <tt>C:/</tt>. Use a 3.80 version, or find a newer
451 version that has this problem fixed.
452 </li>
453 </ul>
454 <p>
455 Information on GNU make, and access to ftp download sites, are
456 available on the
457 <a href="http://www.gnu.org/software/make/make.html">
458 GNU make web site
459 </a>.
460 The latest source to GNU make is available at
461 <a href="http://ftp.gnu.org/pub/gnu/make/">ftp.gnu.org/pub/gnu/make/</a>.
462</blockquote>
463
464<!-- ------------------------------------------------------ -->
465<hr noshade="noshade" size="3">
466
467<h3><a name="linux">Basic Linux System Setup</a></h3>
468
469<blockquote>
470 <p>
471 <strong>i586 only:</strong>
472 The minimum recommended hardware for building the Linux version
473 is a Pentium class processor or better, at least 256 MB of RAM, and
474 approximately 1.5 GB of free disk space.
475 <p>
476 <strong>X64 only:</strong>
477 The minimum recommended hardware for building the Linux
478 version is an AMD Opteron class processor, at least 512 MB of RAM, and
479 approximately 4 GB of free disk space.
480 <p>
481 The build will use the tools contained in
482 <tt>/bin</tt> and
483 <tt>/usr/bin</tt>
484 of a standard installation of the Linux operating environment.
485 You should ensure that these directories are in your
486 <tt>PATH</tt>.
487 <p>
488 Note that some Linux systems have a habit of pre-populating
489 your environment variables for you, for example <tt>JAVA_HOME</tt>
490 might get pre-defined for you to refer to the JDK installed on
491 your Linux system.
492 You will need to unset <tt>JAVA_HOME</tt>.
493 It's a good idea to run <tt>env</tt> and verify the
494 environment variables you are getting from the default system
495 settings make sense for building the
496 OpenJDK.
497</blockquote>
498
499<!-- ------------------------------------------------------ -->
500
501<h4><a name="linux_checklist">Basic Linux Check List</a></h4>
502
503<blockquote>
504 <ol>
505 <li>
506 Install the
507 <a href="#bootjdk">Bootstrap JDK</a>, set
508 <tt><a href="#ALT_BOOTDIR">ALT_BOOTDIR</a></tt>.
509 </li>
510 <li>
511 Install the
512 <a href="#binaryplugs">Binary Plugs</a>, set
513 <tt><a href="#ALT_BINARY_PLUGS_PATH">ALT_BINARY_PLUGS_PATH</a></tt>.
514 </li>
515 <li>
516 Install or upgrade the <a href="#freetype">FreeType development
517 package</a>.
518 </li>
519 </ol>
520</blockquote>
521
522<!-- ------------------------------------------------------ -->
523<hr noshade="noshade" size="3">
524
525<h3><a name="solaris">Basic Solaris System Setup</a></h3>
526
527<blockquote>
528 <p>
529 The minimum recommended hardware for building the
530 Solaris SPARC version is an UltraSPARC with 512 MB of RAM.
531 For building
532 the Solaris x86 version, a Pentium class processor or better and at
533 least 128 MB of RAM are recommended.
534 Approximately 1.4 GB of free disk
535 space is needed for a 32-bit build.
536 <p>
537 If you are building the 64bit version, you should
538 run the command "isainfo -v" to verify that you have a
539 64-bit installation.
540 An additional 7 GB of free disk space is needed
541 for a 64-bit build.
542 <p>
543 The build uses the tools contained in <tt>/usr/ccs/bin</tt>
544 and <tt>/usr/bin</tt> of a standard developer or full installation of
545 the Solaris operating environment.
546</blockquote>
547
548<!-- ------------------------------------------------------ -->
549
550<h4><a name="solaris_checklist">Basic Solaris Check List</a></h4>
551
552<blockquote>
553 <ol>
554 <li>
555 Install the
556 <a href="#bootjdk">Bootstrap JDK</a>, set
557 <tt><a href="#ALT_BOOTDIR">ALT_BOOTDIR</a></tt>.
558 </li>
559 <li>
560 Install the
561 <a href="#binaryplugs">Binary Plugs</a>, set
562 <tt><a href="#ALT_BINARY_PLUGS_PATH">ALT_BINARY_PLUGS_PATH</a></tt>.
563 </li>
564 <li>
565 Install the
566 <a href="#studio">Sun Studio Compilers</a>, set
567 <a href="#ALT_COMPILER_PATH"><tt>ALT_COMPILER_PATH</tt></a>.
568 </li>
569 <li>
570 Install the
571 <a href="#cups">CUPS Include files</a>, set
572 <tt><a href="#ALT_CUPS_HEADERS_PATH">ALT_CUPS_HEADERS_PATH</a></tt>.
573 </li>
574 </ol>
575</blockquote>
576
577<!-- ------------------------------------------------------ -->
578<hr noshade="noshade" size="3">
579
580<h3><a name="windows">Basic Windows System Setup</a></h3>
581
582<blockquote>
583 <p>
584 <strong>i586 only:</strong>
585 The minimum recommended hardware for building the 32bit or X86
586 Windows version is an Pentium class processor or better, at least
587 512 MB of RAM, and approximately 600 MB of free disk space.
588 <strong>
589 NOTE: The Windows 2000 build machines need to use the
590 file system NTFS.
591 Build machines formatted to FAT32 will not work
592 because FAT32 doesn't support case-sensitivity in file names.
593 </strong>
594 <p>
595 <strong>X64 only:</strong>
596 The minimum recommended hardware for building
597 the Windows X64 version is an AMD Opteron class processor, at least 1
598 GB of RAM, and approximately 10 GB of free disk space.
599</blockquote>
600
601<!-- ------------------------------------------------------ -->
602
603<h4><a name="paths">Windows Paths</a></h4>
604
605<blockquote>
606 <p>
607 <strong>Windows:</strong>
608 Note that GNU make is a historic utility and is based very
609 heavily on shell scripting, so it does not tolerate the Windows habit
610 of having spaces in pathnames or the use of the <tt>\</tt>characters in pathnames.
611 Luckily on most Windows systems, you can use <tt>/</tt>instead of \, and
612 there is always a 'short' pathname without spaces for any path that
613 contains spaces.
614 Unfortunately, this short pathname can be somewhat dynamic and the
615 formula is difficult to explain.
616 You can use <tt>cygpath</tt> utility to map pathnames with spaces
617 or the <tt>\</tt>character into the <tt>C:/</tt> style of pathname
618 (called 'mixed'), e.g.
619 <tt>cygpath -s -m "<i>path</i>"</tt>.
620 <p>
621 The makefiles will try to translate any pathnames supplied
622 to it into the <tt>C:/</tt> style automatically.
623 <p>
624 Note that use of CYGWIN creates a unique problem with regards to
625 setting <a href="#path"><tt>PATH</tt></a>. Normally on Windows
626 the <tt>PATH</tt> variable contains directories
627 separated with the ";" character (Solaris and Linux uses ":").
628 With CYGWIN, it uses ":", but that means that paths like "C:/path"
629 cannot be placed in the CYGWIN version of <tt>PATH</tt> and
630 instead CYGWIN uses something like <tt>/cygdrive/c/path</tt>
631 which CYGWIN understands, but only CYGWIN understands.
632 So be careful with paths on Windows.
633</blockquote>
634
635<!-- ------------------------------------------------------ -->
636
637<h4><a name="windows_checklist">Basic Windows Check List</a></h4>
638
639<blockquote>
640 <ol>
641 <li>
642 Install the
643 <a href="#cygwin">CYGWIN product</a>.
644 </li>
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 Install the
657 <a href="#msvc">Microsoft Visual Studio .NET 2003 Professional</a> or the
658 <a href="#mssdk">Microsoft Platform SDK</a>.
659 </li>
660 <li>
661 Setup all environment variables for compilers
662 (see <a href="#msvc">compilers</a>).
663 </li>
664 <li>
665 Install
666 <a href="#dxsdk">Microsoft DirectX SDK</a>.
667 </li>
668 </ol>
669</blockquote>
670
671<!-- ------------------------------------------------------ -->
672<hr noshade="noshade" size="3">
673
674<h3><a name="dependencies">Build Dependencies</a></h3>
675
676<blockquote>
677 <p>
678 Depending on the platform, the
679 OpenJDK
680 build process has some basic
681 dependencies on components not part of the
682 OpenJDK
683 sources.
684 Some of these are specific to a platform, some even specific to
685 an architecture.
686 Each dependency will have a set of ALT variables that can be set
687 to tell the makefiles where to locate the component.
688 In most cases setting these ALT variables may not be necessary
689 and the makefiles will find defaults on the system in standard
690 install locations or through component specific variables.
691
692 <h4><a name="bootjdk">Bootstrap JDK</a></h4>
693
694 <blockquote>
695 <p>
696 All
697 OpenJDK
698 builds require access to the previously released
699 JDK 6, this is often called a bootstrap JDK.
700 The JDK 6 binaries can be downloaded from Sun's
701 <a href="http://java.sun.com/javase/1.6.0/download.html">JDK 6 download site</a>.
702 For build performance reasons
703 is very important that this bootstrap JDK be made available on the
704 local disk of the machine doing the build.
705 You should always set
706 <tt><a href="#ALT_BOOTDIR">ALT_BOOTDIR</a></tt>
707 to point to the location of
708 the bootstrap JDK installation, this is the directory pathname
709 that contains a <tt>bin, lib, and include</tt>
710 It's also a good idea to also place its <tt>bin</tt> directory
711 in the <tt>PATH</tt> environment variable, although it's
712 not required.
713 <p>
714 <strong>Solaris:</strong>
715 Some pre-installed JDK images may be available to you in the
716 directory <tt>/usr/jdk/instances</tt>.
717 If you don't set
718 <tt><a href="#ALT_BOOTDIR">ALT_BOOTDIR</a></tt>
719 the makefiles will look in that location for a JDK it can use.
720 </blockquote>
721
722 <h4><a name="binaryplugs">Binary Plugs</a></h4>
723
724 <blockquote>
725 <p>
726 Not all of the source code that makes up the JDK is available
727 under an open-source license.
728 In order to build an OpenJDK binary from source code,
729 you must first download and install the appropriate
Kelly O'Haird8e9d222008-03-05 18:56:03 -0800[diff] [blame]730 binary plug bundles from the OpenJDK, go to the
731 <a href="http://openjdk.java.net">OpenJDK</a> site and select
732 the "<b>Bundles(7)</b>" link.
J. Duke686d76f2007-12-01 00:00:00 +0000[diff] [blame]733 During the OpenJDK build process these "binary plugs"
734 for the encumbered components will be copied into your
735 resulting OpenJDK binary build image.
736 These binary plug files are only for the purpose of
737 building an OpenJDK binary.
Kelly O'Haird8e9d222008-03-05 18:56:03 -0800[diff] [blame]738 Make sure you set
J. Duke686d76f2007-12-01 00:00:00 +0000[diff] [blame]739 <tt><a href="#ALT_BINARY_PLUGS_PATH">ALT_BINARY_PLUGS_PATH</a></tt>
740 to the root of this installation.
741 </blockquote>
742
743 <h4><a name="cacerts">Certificate Authority File (cacert)</a></h4>
744
745 <blockquote>
746 <p>
747 See <a href="http://en.wikipedia.org/wiki/CAcert">
748 www.wikipedia.org/wiki/CAcert</a>
749 for a better understanding of the Certificate Authority (CA).
750 A certificates file named "cacerts"
751 represents a system-wide keystore with CA certificates.
752 In JDK and JRE
753 binary bundles, the "cacerts" file contains root CA certificates from
754 several public CAs (e.g., VeriSign, Thawte, and Baltimore).
755 The source contain a cacerts file
756 without CA root certificates.
757 Formal JDK builders will need to secure
758 permission from each public CA and include the certificates into their
759 own custom cacerts file.
760 Failure to provide a populated cacerts file
761 will result in verification errors of a certificate chain during runtime.
762 The variable
763 <tt><a href="#ALT_CACERTS_FILE">ALT_CACERTS_FILE</a></tt>
764 can be used to override the default location of the
765 cacerts file that will get placed in your build.
766 By default an empty cacerts file is provided and that should be
767 fine for most JDK developers.
768 </blockquote>
769
770 <h4><a name="compilers">Compilers</a></h4>
771
772 <blockquote>
773
774 <a name="gcc">
775 <strong>Linux gcc/binutils</strong>
776 </a>
777
778 <blockquote>
779 <p>
780 The GNU gcc compiler version should be 3.2.2 or newer.
781 The binutils package should be 2.11.93.0.2-11 or newer.
782 The compiler used should be the default compiler installed
783 in <tt>/usr/bin</tt>.
784 </blockquote>
785
786 <strong><a name="studio">Solaris: Sun Studio</a></strong>
787
788 <blockquote>
789 <p>
790 At a minimum, the
791 <a href="http://developers.sun.com/sunstudio/index.jsp">
792 Sun Studio 11 Compilers</a>
793 (containing version 5.8 of the C and C++ compilers) is required,
794 with patches from the
795 <a href="http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-access">
796 SunSolve web site</a>.
797 <p>
798 Set
799 <a href="#ALT_COMPILER_PATH"><tt>ALT_COMPILER_PATH</tt></a>
800 to point to the location of
801 the compiler binaries, and place this location in the <tt>PATH</tt>.
802 <p>
803 The Sun Studio Express compilers at:
804 <a href="http://developers.sun.com/sunstudio/downloads/express.jsp">
805 Sun Studio Express Download site</a>
806 are also an option, although these compilers have not
807 been extensively used yet.
808 </blockquote>
809
810 <a name="msvc">
811 <strong>Windows i586: Microsoft Visual Studio .NET 2003 Professional</strong>
812 </a>
813
814 <blockquote>
815 <p>
816 The 32-bit
817 OpenJDK
818 Windows build
819 requires Microsoft Visual Studio .NET 2003 (VS2003) Professional
820 Edition compiler.
821 The compiler and other tools are expected to reside
822 in the location defined by the variable <tt>VS71COMNTOOLS</tt> which
823 is set by the Microsoft Visual Studio .NET installer.
824 <p>
825 Once the compiler is installed,
826 it is recommended that you run <tt>VCVARS32.BAT</tt>
827 to set the compiler environment variables
828 <tt>MSVCDIR</tt>,
829 <tt>INCLUDE</tt>,
830 <tt>LIB</tt>, and
831 <tt>PATH</tt>
832 prior to building the
833 OpenJDK.
834 The above environment variables <b>MUST</b> be set.
835 <p>
836 The Microsoft Visual Studio .NET 2005 (VS2005) compiler
837 will not work at this time due to the new runtime dll
838 and the manifest requirements.
839 </blockquote>
840
841 <a name="mssdk">
842 <strong>Windows X64: Microsoft Platform SDK April 2005</strong>
843 </a>
844
845 <blockquote>
846 <p>
847 On <b>X64</b>,
848 the Microsoft Platform Software
849 Development Kit (SDK), April 2005 Edition compiler, is required for
850 building the
851 OpenJDK
852 because it contains the C/C++ compiler.
853 You will need to minimally install the Core SDK and
854 the MDAC SDK features of this compiler.
855 <p>
856 Once the Platform SDK is installed,
857 it is recommended that you run <tt>SetEnv.Cmd /X64</tt>
858 to set the compiler environment variables
859 <tt>MSSDK</tt>,
860 <tt>MSTOOLS</tt>,
861 <tt>INCLUDE</tt>,
862 <tt>LIB</tt>, and
863 <tt>PATH</tt>
864 prior to building the
865 OpenJDK.
866 The above environment variables <b>MUST</b> be set.
867 <p>
868 Note that this compiler may say it's version is a
869 Microsoft Visual Studio .NET 2005 (VS2005), but be careful,
870 it will not match the official VS2005 product.
871 This Platform SDK compiler is only used on X64 builds.
872 </blockquote>
873
874 </blockquote>
875
876 <h4><a name="cups">Common UNIX Printing System (CUPS) Headers (Solaris &amp; Linux)</a></h4>
877
878 <blockquote>
879 <p>
880 <strong>Solaris:</strong>
881 CUPS header files are required for building the
882 OpenJDK on Solaris.
883 The Solaris header files can be obtained by installing
884 the package <strong>SFWcups</strong> from the Solaris Software
885 Companion CD/DVD, these often will be installed into
886 <tt>/opt/sfw/cups</tt>.
887 <p>
888 <strong>Linux:</strong>
889 CUPS header files are required for building the
890 OpenJDK on Linux.
891 The Linux header files are usually available from a "cups"
892 development package, it's recommended that you try and use
893 the package provided by the particular version of Linux that
894 you are using.
895 <p>
896 The CUPS header files can always be downloaded from
897 <a href="http://www.cups.org">www.cups.org</a>.
898 The variable
899 <tt><a href="#ALT_CUPS_HEADERS_PATH">ALT_CUPS_HEADERS_PATH</a></tt>
900 can be used to override the default location of the
901 CUPS Header files.
902 </blockquote>
903
904 <h4><a name="freetype">FreeType 2</a></h4>
905
906 <blockquote>
907 <p>
908 Version 2.3 or newer of FreeType is required for building the OpenJDK.
909 On Unix systems required files can be available as part of your
910 distribution (while you still may need to upgrade them).
911 Note that you need development version of package that
912 includes both FreeType library and header files.
913 </p>
914 <p>
915 You can always download latest FreeType version from the
916 <a href="http://www.freetype.org">FreeType website</a>.
917 </p>
918 <p>
919 Makefiles will try to pick FreeType from /usr/lib and /usr/include.
920 In case it is installed elsewhere you will need to set environment
921 variables
922 <tt><a href="#ALT_FREETYPE_LIB_PATH">ALT_FREETYPE_LIB_PATH</a></tt>
923 and
924 <tt><a href="#ALT_FREETYPE_HEADERS_PATH">ALT_FREETYPE_HEADERS_PATH</a></tt>
925 to refer to place where library and header files are installed.
926 </p>
927 </blockquote>
928
929 <h4><a name="alsa">Advanced Linux Sound Architecture (ALSA) (Linux only)</a></h4>
930
931 <blockquote>
932 <p>
933 <strong>Linux only:</strong>
934 Version 0.9.1 or newer of the ALSA files are
935 required for building the
936 OpenJDK on Linux.
937 These Linux files are usually available from an "alsa"
938 of "libasound"
939 development package, it's recommended that you try and use
940 the package provided by the particular version of Linux that
941 you are using.
942 The makefiles will check this emit a sanity error if it is
943 missing or the wrong version.
944 As a last resort you can go to the
945 <a href="http://www.alsa-project.org" target="_blank">
946 Advanced Linux Sound Architecture Site</a>.
947 </blockquote>
948
949 <h4>Windows Specific Dependencies</h4>
950
951 <blockquote>
952
953 <strong>Unix Command Tools (<a name="cygwin">CYGWIN</a>)</strong>
954
955 <blockquote>
956 <p>
957 The
958 OpenJDK
959 requires access to a set of unix command tools
960 on Windows which can be supplied by
961 <a href="http://www.cygwin.com">CYGWIN</a>.
962 <p>
963 The
964 OpenJDK
965 build
966 requires CYGWIN version 1.5.12 or newer.
967 Information about CYGWIN can
968 be obtained from the CYGWIN website at
969 <a href="http://www.cygwin.com">www.cygwin.com</a>.
970 <p>
971 By default CYGWIN doesn't install all the tools required for building
972 the OpenJDK.
973 Along with the default installation, you need to install
974 the following tools.
975 <blockquote>
976 <table border="1">
977 <thead>
978 <tr>
979 <td>Binary Name</td>
980 <td>Package</td>
981 <td>Description</td>
982 </tr>
983 </thead>
984 <tbody>
985 <tr>
986 <td>ar.exe</td>
987 <td>Devel</td>
988 <td>binutils: The GNU assembler, linker and binary
989 utilities</td>
990 </tr>
991 <tr>
992 <td>make.exe</td>
993 <td>Devel</td>
994 <td>make: The GNU version of the 'make' utility</td>
995 </tr>
996 <tr>
997 <td>m4.exe</td>
998 <td>Interpreters</td>
999 <td>m4: GNU implementation of the traditional Unix macro
1000 processor</td>
1001 </tr>
1002 <tr>
1003 <td>cpio.exe</td>
1004 <td>Utils</td>
1005 <td>cpio: A program to manage archives of files</td>
1006 </tr>
1007 <tr>
1008 <td>file.exe</td>
1009 <td>Utils</td>
1010 <td>file: Determines file type using 'magic' numbers</td>
1011 </tr>
1012 </tbody>
1013 </table>
1014 </blockquote>
1015 </blockquote>
1016
1017 <a name="dxsdk">
1018 <strong>Microsoft DirectX 9.0 SDK header files and libraries</strong>
1019 </a>
1020
1021 <blockquote>
1022 <p>
1023 Microsoft DirectX 9.0 SDK (Summer 2004)
1024 headers are required for building
1025 OpenJDK.
1026 This SDK can be downloaded from
1027 <a href="http://www.microsoft.com/downloads/details.aspx?FamilyId=FD044A42-9912-42A3-9A9E-D857199F888E&amp;displaylang=en">
1028 Microsoft DirectX 9.0 SDK (Summer 2004)</a>.
1029 If the link above becomes obsolete, the SDK can be found from
1030 <a href="http://download.microsoft.com">the Microsoft Download Site</a>
1031 (search with "DirectX 9.0 SDK Update Summer 2004").
1032 The location of this SDK can be set with
1033 <tt><a href="#ALT_DXSDK_PATH">ALT_DXSDK_PATH</a></tt>
1034 but it's normally found via the DirectX environment variable
1035 <tt>DXSDK_DIR</tt>.
1036 </blockquote>
1037
1038 <a name="msvcrt">
1039 <strong><tt>MSVCRT.DLL</tt></strong>
1040 </a>
1041
1042 <blockquote>
1043 <p>
1044 <strong>i586 only:</strong>
1045 The
1046 OpenJDK
1047 32bit build requires
1048 access to <tt>MSVCRT.DLL</tt>
1049 version 6.00.8337.0 or newer.
1050 If the <tt>MSVCRT.DLL</tt> is not installed in
1051 the system32 directory set the
1052 <a href="#ALT_MSVCRT_DLL_PATH"><tt>ALT_MSVCRT_DLL_PATH</tt></a>
1053 variable to the location.
1054 <p>
1055 <strong>X64 only:</strong>
1056 The OpenJDK 64bit build requires access to
1057 <tt>MSVCRT.DLL</tt> version 7.0.3790.0 or newer, which is
1058 usually supplied by the
1059 <a href="#mssdk">Platform SDK</a>.
1060 If it is not available from the Platform SDK,
1061 set the
1062 <a href="#ALT_MSVCRT_DLL_PATH"><tt>ALT_MSVCRT_DLL_PATH</tt></a>
1063 variable to the location.
1064 </blockquote>
1065
1066 <a name="msvcr71">
1067 <strong><tt>MSVCR71.DLL</tt></strong>
1068 </a>
1069
1070 <blockquote>
1071 <p>
1072 <strong>i586 only:</strong>
1073 The
1074 OpenJDK
1075 build requires access to
1076 MSVCR71.DLL version 7.10.3052.4 or newer which should be
1077 supplied by the
1078 <a href="#msvc">Visual Studio product</a>
1079 If the <tt>MSVCR71.DLL</tt> is not available from the
1080 Visual Studio product
1081 set the
1082 <a href="#ALT_MSVCR71_DLL_PATH"><tt>ALT_MSVCR71_DLL_PATH</tt></a>
1083 variable to the location.
1084 </blockquote>
1085
1086 </blockquote>
1087
1088
1089</blockquote>
1090
1091
1092<hr noshade="noshade" size="3">
1093
1094<h2><a name="creating">Creating the Build</a></h2>
1095
1096<blockquote>
1097 <p>
1098 Once a machine is setup to build the
1099 OpenJDK,
1100 the steps to create the
1101 build are fairly simple.
1102 The various ALT settings can either be made into variables
1103 or can be supplied on the
1104 <a href="#gmake"><tt><i>gmake</i></tt></a>
1105 command.
1106 <p>
1107 <ol>
1108 <li>Use the sanity rule to double check all the ALT settings:
1109 <blockquote>
1110 <tt>
1111 <i>gmake</i>
1112 sanity
1113 [ARCH_DATA_MODEL=<i>32 or 64</i>]
1114 [other "ALT_" overrides]
1115 </tt>
1116 </blockquote>
1117 </li>
1118 <li>Start the build with the command:
1119 <blockquote>
1120 <tt>
1121 <i>gmake</i>
1122 [ARCH_DATA_MODEL=<i>32 or 64</i>]
1123 [ALT_OUTPUTDIR=<i>output_directory</i>]
1124 [other "ALT_" overrides]
1125 </tt>
1126 </blockquote>
1127 </li>
1128 </ol>
1129 <p>
1130 <strong>Solaris:</strong>
1131 Note that ARCH_DATA_MODEL is really only needed on Solaris to
1132 indicate you want to built the 64-bit version.
1133 And before the Solaris 64-bit binaries can be used, they
1134 must be merged with the binaries from a separate 32-bit build.
1135 The merged binaries may then be used in either 32-bit or 64-bit mode, with
1136 the selection occurring at runtime
1137 with the <tt>-d32</tt> or <tt>-d64</tt> options.
1138</blockquote>
1139
1140<!-- ------------------------------------------------------ -->
1141<hr noshade="noshade" size="3">
1142
1143<h2><a name="testing">Testing the Build</a></h2>
1144
1145<blockquote>
1146 <p>
1147 When the build is completed, you should see the generated
1148 binaries and associated files in the <tt>j2sdk-image</tt>
1149 directory in the output directory.
1150 The default output directory is
1151 <tt>build/<i>platform</i></tt>,
1152 where <tt><i>platform</i></tt> is one of
1153 <tt><ul>
1154 <li>solaris-sparc</li>
1155 <li>solaris-sparcv9</li>
1156 <li>solaris-i586</li>
1157 <li>solaris-amd64</li>
1158 <li>linux-i586</li>
1159 <li>linux-amd64</li>
1160 <li>windows-i586</li>
1161 <li>windows-amd64</li>
1162 </ul></tt>
1163 In particular, the
1164 <tt>build/<i>platform</i>/j2sdk-image/bin</tt>
1165 directory should contain executables for the
1166 OpenJDK
1167 tools and utilities.
1168 <p>
1169 You can test that the build completed properly by using the build
1170 to run the various demos that you will find in the
1171 <tt>build/<i>platform</i>/j2sdk-image/demo</tt>
1172 directory.
1173 <p>
1174 The provided regression tests can be run with the <tt>jtreg</tt>
1175 utility from
1176 <a href="http://openjdk.java.net/jtreg/">the jtreg site</a>.
1177</blockquote>
1178
1179<!-- ------------------------------------------------------ -->
1180<hr noshade="noshade" size="3">
1181
1182<h2><a name="variables">Environment/Make Variables</a></h2>
1183
1184<p>
1185Some of the
1186environment or make variables (just called <b>variables</b> in this
1187document) that can impact the build are:
1188
1189<blockquote>
1190
1191 <dl>
1192
1193 <dt><a name="path"><tt>PATH</tt></a> </dt>
1194 <dd>Typically you want to set the <tt>PATH</tt> to include:
1195 <ul>
1196 <li>The location of the GNU make binary</li>
1197 <li>The location of the JDK 6 <tt>java</tt>
1198 (see <a href="#bootjdk">Bootstrap JDK</a>)</li>
1199 <li>The location of the C/C++ compilers
1200 (see <a href="#compilers"><tt>compilers</tt></a>)</li>
1201 <li>The location or locations for the Unix command utilities
1202 (e.g. <tt>/usr/bin</tt>)</li>
1203 </ul>
1204 </dd>
1205
1206 <dt><a name="arch_data_model"><tt>ARCH_DATA_MODEL</tt></a></dt>
1207 <dd>The <tt>ARCH_DATA_MODEL</tt> variable
1208 is used to specify whether the build is to generate 32-bit or 64-bit
1209 binaries.
1210 The Solaris build supports either 32-bit or 64-bit builds, but
1211 Windows and Linux will support only one, depending on the specific
1212 OS being used.
1213 Normally, setting this variable is only necessary on Solaris.
1214 Set <tt>ARCH_DATA_MODEL</tt> to <tt>32</tt> for generating 32-bit binaries,
1215 or to <tt>64</tt> for generating 64-bit binaries.
1216 </dd>
1217
1218 <dt><a name="ALT_BOOTDIR"><tt>ALT_BOOTDIR</tt></a></dt>
1219 <dd>
1220 The location of the bootstrap JDK installation.
1221 See <a href="#bootjdk">Bootstrap JDK</a> for more information.
1222 You should always install your own local Bootstrap JDK and
1223 always set <tt>ALT_BOOTDIR</tt> explicitly.
1224 </dd>
1225
1226 <dt><a name="ALT_OUTPUTDIR"><tt>ALT_OUTPUTDIR</tt></a> </dt>
1227 <dd>
1228 An override for specifying the (absolute) path of where the
1229 build output is to go.
1230 The default output directory will be build/<i>platform</i>.
1231 </dd>
1232
1233 <dt><a name="ALT_COMPILER_PATH"><tt>ALT_COMPILER_PATH</tt></a> </dt>
1234 <dd>
1235 The location of the C/C++ compiler.
1236 The default varies depending on the platform.
1237 </dd>
1238
1239 <dt><tt><a name="ALT_CACERTS_FILE">ALT_CACERTS_FILE</a></tt></dt>
1240 <dd>
1241 The location of the <a href="#cacerts">cacerts</a> file.
1242 The default will refer to
1243 <tt>jdk/src/share/lib/security/cacerts</tt>.
1244 </dd>
1245
1246 <dt><a name="ALT_BINARY_PLUGS_PATH"><tt>ALT_BINARY_PLUGS_PATH</tt></a></dt>
1247 <dd>
1248 The location of the binary plugs installation.
1249 See <a href="#binaryplugs">Binary Plugs</a> for more information.
1250 You should always have a local copy of a
1251 recent Binary Plugs install image
1252 and set this variable to that location.
1253 </dd>
1254
1255 <dt><a name="ALT_CUPS_HEADERS_PATH"><tt>ALT_CUPS_HEADERS_PATH</tt></a> </dt>
1256 <dd>
1257 The location of the CUPS header files.
1258 See <a href="#cups">CUPS information</a> for more information.
1259 If this path does not exist the fallback path is
1260 <tt>/usr/include</tt>.
1261 </dd>
1262
1263
1264 <dt><a name="ALT_FREETYPE_LIB_PATH"><tt>ALT_FREETYPE_LIB_PATH</tt></a></dt>
1265 <dd>
1266 The location of the FreeType shared library.
1267 See <a href="#freetype">FreeType information</a> for details.
1268 </dd>
1269
1270 <dt><a name="ALT_FREETYPE_HEADERS_PATH"><tt>ALT_FREETYPE_HEADERS_PATH</tt></a></dt>
1271 <dd>
1272 The location of the FreeType header files.
1273 See <a href="#freetype">FreeType information</a> for details.
1274 </dd>
1275
1276 <dt><strong>Windows specific:</strong></dt>
1277 <dd>
1278 <dl>
1279 <dt><a name="ALT_MSDEVTOOLS_PATH"><tt>ALT_MSDEVTOOLS_PATH</tt></a> </dt>
1280 <dd>
1281 The location of the Microsoft Visual Studio .NET 2003
1282 tools 'bin' directory.
1283 The default is usually derived from
1284 <a href="#ALT_COMPILER_PATH"><tt>ALT_COMPILER_PATH</tt></a>.
1285 </dd>
1286
1287 <dt><tt><a name="ALT_DXSDK_PATH">ALT_DXSDK_PATH</a></tt> </dt>
1288 <dd>
1289 The location of the
1290 <a href="#dxsdk">Microsoft DirectX 9 SDK</a>.
1291 The default will be to try and use the DirectX environment
1292 variable <tt>DXSDK_DIR</tt>,
1293 failing that, look in <tt>C:/DXSDK</tt>.
1294 </dd>
1295
1296 <dt><tt><a name="ALT_MSVCRT_DLL_PATH">ALT_MSVCRT_DLL_PATH</a></tt> </dt>
1297 <dd>
1298 The location of the
1299 <a href="#msvcrt"><tt>MSVCRT.DLL</tt></a>.
1300 </dd>
1301
1302 <dt><tt><a name="ALT_MSVCR71_DLL_PATH">ALT_MSVCR71_DLL_PATH</a></tt> </dt>
1303 <dd>
1304 <strong>i586 only:</strong>
1305 The location of the
1306 <a href="#msvcr71"><tt>MSVCR71.DLL</tt></a>.
1307 </dd>
1308 </dl>
1309 </dd>
1310
1311 </dl>
1312</blockquote>
1313
1314<!-- ------------------------------------------------------ -->
1315<hr noshade="noshade" size="3">
1316
1317<h2><a name="troubleshooting">Troubleshooting</a></h2>
1318
1319<blockquote>
1320 <p>
1321 A build can fail for any number of reasons.
1322 Most failures
1323 are a result of trying to build in an environment in which all the
1324 pre-build requirements have not been met.
1325 The first step in
1326 troubleshooting a build failure is to recheck that you have satisfied
1327 all the pre-build requirements for your platform.
1328 Look for the check list of the platform you are building on in the
1329 <a href="#contents">Table of Contents</a>.
1330
1331 <p>
1332 You can validate your build environment by using the <tt>sanity</tt>
1333 target.
1334 Any errors listed
1335 will stop the build from starting, and any warnings may result in
1336 a flawed product build.
1337 We strongly encourage you to evaluate every
1338 sanity check warning and fix it if required, before you proceed
1339 further with your build.
1340
1341 <p>
1342 Some of the more common problems with builds are briefly described
1343 below, with suggestions for remedies.
1344
1345 <ul>
1346 <li>
1347 <b>Slow Builds:</b>
1348 <blockquote>
1349 <p>
1350 If your build machine seems to be overloaded from too many
1351 simultaneous C++ compiles, try setting the <tt>HOTSPOT_BUILD_JOBS</tt>
1352 variable to <tt>1</tt> (if you're using a multiple CPU
1353 machine, setting it to more than the the number of CPUs is probably
1354 not a good idea).
1355 <p>
1356 Creating the javadocs can be very slow, if you are running
1357 javadoc, consider skipping that step.
1358 <p>
1359 Faster hardware and more RAM always helps too.
1360 The VM build tends to be CPU intensive (many C++ compiles),
1361 and the rest of the JDK will often be disk intensive.
1362 <p>
1363 Faster compiles are possible using a tool called
1364 <a href="http://ccache.samba.org/">ccache</a>.
1365 </blockquote>
1366 </li>
1367 <li>
1368 <b>File time issues:</b>
1369 <blockquote>
1370 <p>
1371 If you see warnings that refer to file time stamps, e.g.
1372 <blockquote>
1373 <i>Warning message:</i><tt> File `xxx' has modification time in
1374 the future.</tt>
1375 <br>
1376 <i>Warning message:</i> <tt> Clock skew detected. Your build may
1377 be incomplete.</tt>
1378 </blockquote>
1379 <p>
1380 These warnings can occur when the clock on the build machine is out of
1381 sync with the timestamps on the source files. Other errors, apparently
1382 unrelated but in fact caused by the clock skew, can occur along with
1383 the clock skew warnings. These secondary errors may tend to obscure the
1384 fact that the true root cause of the problem is an out-of-sync clock.
1385 For example, an out-of-sync clock has been known to cause an old
1386 version of javac to be used to compile some files, resulting in errors
1387 when the pre-1.4 compiler ran across the new <tt>assert</tt> keyword
1388 in the 1.4 source code.
1389 <p>
1390 If you see these warnings, reset the clock on the build
1391 machine, run "<tt><i>gmake</i> clobber</tt>" or delete the directory
1392 containing the build output, and restart the build from the beginning.
1393 </blockquote>
1394 </li>
1395 <li>
1396 <b>Error message: <tt>Trouble writing out table to disk</tt></b>
1397 <blockquote>
1398 <p>
1399 Increase the amount of swap space on your build machine.
1400 </blockquote>
1401 </li>
1402 <li>
1403 <b>Error Message: <tt>libstdc++ not found:</tt></b>
1404 <blockquote>
1405 This is caused by a missing libstdc++.a library.
1406 This is installed as part of a specific package
1407 (e.g. libstdc++.so.devel.386).
1408 By default some 64bit Linux versions (e.g. Fedora)
1409 only install the 64bit version of the libstdc++ package.
1410 Various parts of the JDK build require a static
1411 link of the C++ runtime libraries to allow for maximum
1412 portability of the built images.
1413 </blockquote>
1414 </li>
1415 <li>
1416 <b>Error Message: <tt>cannot restore segment prot after reloc</tt></b>
1417 <blockquote>
1418 This is probably an issue with SELinux (See
1419 <a href="http://en.wikipedia.org/wiki/SELinux">http://en.wikipedia.org/wiki/SELinux</a>).
1420 Parts of the VM is built without the <tt>-fPIC</tt> for
1421 performance reasons.
1422 <p>
1423 To completely disable SELinux:
1424 <ol><tt>
1425
1426 <li>$ su root</li>
1427 <li># system-config-securitylevel</li>
1428 <li>In the window that appears, select the SELinux tab</li>
1429 <li>Disable SELinux</li>
1430 </ol></tt>
1431 <p>
1432 Alternatively, instead of completely disabling it you could
1433 disable just this one check.
1434 <ol><tt>
1435 <li>Select System->Administration->SELinux Management</li>
1436 <li>In the SELinux Management Tool which appears,
1437 select "Boolean" from the menu on the left</li>
1438 <li>Expand the "Memory Protection" group</li>
1439 <li>Check the first item, labeled
1440 "Allow all unconfined executables to use libraries requiring text relocation ..."</li>
1441 </ol></tt>
1442 </blockquote>
1443 </li>
1444 </ul>
1445</blockquote>
1446
1447<hr noshade="noshade" size="3">