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