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