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