609 Certificate_Authority">Certificate Authority on Wikipedia</a> for a better understanding of the Certificate
610 Authority (CA). A certificates file named "cacerts" represents a system-wide
611 keystore with CA certificates. In JDK and JRE binary bundles, the "cacerts"
612 file contains root CA certificates from several public CAs (e.g., VeriSign,
613 Thawte, and Baltimore). The source contain a cacerts file without CA root
614 certificates. Formal JDK builders will need to secure permission from each
615 public CA and include the certificates into their own custom cacerts file.
616 Failure to provide a populated cacerts file will result in verification
617 errors of a certificate chain during runtime. By default an empty cacerts
618 file is provided and that should be fine for most JDK developers.</p>
619 </blockquote>
620
621 <p><a name="cups"></a></p>
622
623 <blockquote>
624 <p><strong><code>--with-cups=</code></strong><em>path</em> <br />
625 select the CUPS install location</p>
626
627 <p>The Common UNIX Printing System (CUPS) Headers are required for building the
628 OpenJDK on Solaris and Linux. The Solaris header files can be obtained by
629 installing the package <strong>SFWcups</strong> from the Solaris Software Companion
630 CD/DVD, these often will be installed into the directory <code>/opt/sfw/cups</code>.</p>
631
632 <p>The CUPS header files can always be downloaded from
633 <a href="http://www.cups.org">www.cups.org</a>.</p>
634
635 <p><strong><code>--with-cups-include=</code></strong><em>path</em> <br />
636 select the CUPS include directory location</p>
637
638 <p><strong><code>--with-debug-level=</code></strong><em>level</em> <br />
639 select the debug information level of release, fastdebug, or slowdebug</p>
640
641 <p><strong><code>--with-dev-kit=</code></strong><em>path</em> <br />
642 select location of the compiler install or developer install location</p>
643 </blockquote>
644
645 <p><a name="freetype"></a></p>
646
647 <blockquote>
648 <p><strong><code>--with-freetype=</code></strong><em>path</em> <br />
649 select the freetype files to use.</p>
650
1094 message.</p></li>
1095 </ul>
1096
1097 <hr />
1098
1099 <p><a name="gmake"></a></p>
1100
1101 <h2>Appendix B: GNU make</h2>
1102
1103 <p>The Makefiles in the OpenJDK are only valid when used with the GNU version of
1104 the utility command <code>make</code> (usually called <code>gmake</code> on Solaris). A few notes
1105 about using GNU make:</p>
1106
1107 <ul>
1108 <li>You need GNU make version 3.81 or newer. On Windows 4.0 or newer is
1109 recommended. If the GNU make utility on your systems is not of a suitable
1110 version, see "<a href="#buildgmake">Building GNU make</a>".</li>
1111 <li>Place the location of the GNU make binary in the <code>PATH</code>.</li>
1112 <li><strong>Solaris:</strong> Do NOT use <code>/usr/bin/make</code> on Solaris. If your Solaris system
1113 has the software from the Solaris Developer Companion CD installed, you
1114 should try and use <code>gmake</code> which will be located in either the <code>/usr/bin</code>,
1115 <code>/opt/sfw/bin</code> or <code>/usr/sfw/bin</code> directory.</li>
1116 <li><strong>Windows:</strong> Make sure you start your build inside a bash shell.</li>
1117 <li><strong>Mac OS X:</strong> The XCode "command line tools" must be installed on your Mac.</li>
1118 </ul>
1119
1120 <p>Information on GNU make, and access to ftp download sites, are available on the
1121 <a href="http://www.gnu.org/software/make/make.html">GNU make web site </a>. The latest
1122 source to GNU make is available at
1123 <a href="http://ftp.gnu.org/pub/gnu/make/">ftp.gnu.org/pub/gnu/make/</a>.</p>
1124
1125 <p><a name="buildgmake"></a></p>
1126
1127 <h3>Building GNU make</h3>
1128
1129 <p>First step is to get the GNU make 3.81 or newer source from
1130 <a href="http://ftp.gnu.org/pub/gnu/make/">ftp.gnu.org/pub/gnu/make/</a>. Building is a
1131 little different depending on the OS but is basically done with:</p>
1132
1133 <pre><code> bash ./configure
1134 make
1135 </code></pre>
|
609 Certificate_Authority">Certificate Authority on Wikipedia</a> for a better understanding of the Certificate
610 Authority (CA). A certificates file named "cacerts" represents a system-wide
611 keystore with CA certificates. In JDK and JRE binary bundles, the "cacerts"
612 file contains root CA certificates from several public CAs (e.g., VeriSign,
613 Thawte, and Baltimore). The source contain a cacerts file without CA root
614 certificates. Formal JDK builders will need to secure permission from each
615 public CA and include the certificates into their own custom cacerts file.
616 Failure to provide a populated cacerts file will result in verification
617 errors of a certificate chain during runtime. By default an empty cacerts
618 file is provided and that should be fine for most JDK developers.</p>
619 </blockquote>
620
621 <p><a name="cups"></a></p>
622
623 <blockquote>
624 <p><strong><code>--with-cups=</code></strong><em>path</em> <br />
625 select the CUPS install location</p>
626
627 <p>The Common UNIX Printing System (CUPS) Headers are required for building the
628 OpenJDK on Solaris and Linux. The Solaris header files can be obtained by
629 installing the package <strong>print/cups</strong>.</p>
630
631 <p>The CUPS header files can always be downloaded from
632 <a href="http://www.cups.org">www.cups.org</a>.</p>
633
634 <p><strong><code>--with-cups-include=</code></strong><em>path</em> <br />
635 select the CUPS include directory location</p>
636
637 <p><strong><code>--with-debug-level=</code></strong><em>level</em> <br />
638 select the debug information level of release, fastdebug, or slowdebug</p>
639
640 <p><strong><code>--with-dev-kit=</code></strong><em>path</em> <br />
641 select location of the compiler install or developer install location</p>
642 </blockquote>
643
644 <p><a name="freetype"></a></p>
645
646 <blockquote>
647 <p><strong><code>--with-freetype=</code></strong><em>path</em> <br />
648 select the freetype files to use.</p>
649
1093 message.</p></li>
1094 </ul>
1095
1096 <hr />
1097
1098 <p><a name="gmake"></a></p>
1099
1100 <h2>Appendix B: GNU make</h2>
1101
1102 <p>The Makefiles in the OpenJDK are only valid when used with the GNU version of
1103 the utility command <code>make</code> (usually called <code>gmake</code> on Solaris). A few notes
1104 about using GNU make:</p>
1105
1106 <ul>
1107 <li>You need GNU make version 3.81 or newer. On Windows 4.0 or newer is
1108 recommended. If the GNU make utility on your systems is not of a suitable
1109 version, see "<a href="#buildgmake">Building GNU make</a>".</li>
1110 <li>Place the location of the GNU make binary in the <code>PATH</code>.</li>
1111 <li><strong>Solaris:</strong> Do NOT use <code>/usr/bin/make</code> on Solaris. If your Solaris system
1112 has the software from the Solaris Developer Companion CD installed, you
1113 should try and use <code>/usr/bin/gmake</code> or <code>/usr/gnu/bin/make</code>.</li>
1114 <li><strong>Windows:</strong> Make sure you start your build inside a bash shell.</li>
1115 <li><strong>Mac OS X:</strong> The XCode "command line tools" must be installed on your Mac.</li>
1116 </ul>
1117
1118 <p>Information on GNU make, and access to ftp download sites, are available on the
1119 <a href="http://www.gnu.org/software/make/make.html">GNU make web site </a>. The latest
1120 source to GNU make is available at
1121 <a href="http://ftp.gnu.org/pub/gnu/make/">ftp.gnu.org/pub/gnu/make/</a>.</p>
1122
1123 <p><a name="buildgmake"></a></p>
1124
1125 <h3>Building GNU make</h3>
1126
1127 <p>First step is to get the GNU make 3.81 or newer source from
1128 <a href="http://ftp.gnu.org/pub/gnu/make/">ftp.gnu.org/pub/gnu/make/</a>. Building is a
1129 little different depending on the OS but is basically done with:</p>
1130
1131 <pre><code> bash ./configure
1132 make
1133 </code></pre>
|