< prev index next >

./README-builds.md

Print this page




 543 >  select the path to the cacerts file.
 544 
 545 >  See [Certificate Authority on Wikipedia](http://en.wikipedia.org/wiki/
 546    Certificate_Authority) for a better understanding of the Certificate
 547    Authority (CA). A certificates file named "cacerts" represents a system-wide
 548    keystore with CA certificates. In JDK and JRE binary bundles, the "cacerts"
 549    file contains root CA certificates from several public CAs (e.g., VeriSign,
 550    Thawte, and Baltimore). The source contain a cacerts file without CA root
 551    certificates. Formal JDK builders will need to secure permission from each
 552    public CA and include the certificates into their own custom cacerts file.
 553    Failure to provide a populated cacerts file will result in verification
 554    errors of a certificate chain during runtime. By default an empty cacerts
 555    file is provided and that should be fine for most JDK developers.
 556 
 557 <a name="cups"></a>
 558 >  **`--with-cups=`**_path_  
 559 >  select the CUPS install location
 560 
 561 >  The Common UNIX Printing System (CUPS) Headers are required for building the
 562    OpenJDK on Solaris and Linux. The Solaris header files can be obtained by
 563    installing the package **SFWcups** from the Solaris Software Companion
 564    CD/DVD, these often will be installed into the directory `/opt/sfw/cups`.
 565 
 566 >  The CUPS header files can always be downloaded from
 567    [www.cups.org](http://www.cups.org).
 568 
 569 >  **`--with-cups-include=`**_path_  
 570 >  select the CUPS include directory location
 571 
 572 >  **`--with-debug-level=`**_level_  
 573 >  select the debug information level of release, fastdebug, or slowdebug
 574 
 575 >  **`--with-dev-kit=`**_path_  
 576 >  select location of the compiler install or developer install location
 577 
 578 <a name="freetype"></a>
 579 >  **`--with-freetype=`**_path_  
 580 >  select the freetype files to use.
 581 
 582 >  Expecting the freetype libraries under `lib/` and the headers under
 583    `include/`.
 584 


1000  * **Windows Error Message: `spawn failed`**  
1001    Try rebooting the system, or there could be some kind of issue with the disk
1002    or disk partition being used. Sometimes it comes with a "Permission Denied"
1003    message.
1004 
1005 *****
1006 
1007 <a name="gmake"></a>
1008 ## Appendix B: GNU make
1009 
1010 The Makefiles in the OpenJDK are only valid when used with the GNU version of
1011 the utility command `make` (usually called `gmake` on Solaris). A few notes
1012 about using GNU make:
1013 
1014  * You need GNU make version 3.81 or newer. On Windows 4.0 or newer is
1015    recommended. If the GNU make utility on your systems is not of a suitable
1016    version, see "[Building GNU make](#buildgmake)".
1017  * Place the location of the GNU make binary in the `PATH`.
1018  * **Solaris:** Do NOT use `/usr/bin/make` on Solaris. If your Solaris system
1019    has the software from the Solaris Developer Companion CD installed, you
1020    should try and use `gmake` which will be located in either the `/usr/bin`,
1021    `/opt/sfw/bin` or `/usr/sfw/bin` directory.
1022  * **Windows:** Make sure you start your build inside a bash shell.
1023  * **Mac OS X:** The XCode "command line tools" must be installed on your Mac.
1024 
1025 Information on GNU make, and access to ftp download sites, are available on the
1026 [GNU make web site ](http://www.gnu.org/software/make/make.html). The latest
1027 source to GNU make is available at
1028 [ftp.gnu.org/pub/gnu/make/](http://ftp.gnu.org/pub/gnu/make/).
1029 
1030 <a name="buildgmake"></a>
1031 ### Building GNU make
1032 
1033 First step is to get the GNU make 3.81 or newer source from
1034 [ftp.gnu.org/pub/gnu/make/](http://ftp.gnu.org/pub/gnu/make/). Building is a
1035 little different depending on the OS but is basically done with:
1036 
1037       bash ./configure
1038       make
1039 
1040 *****
1041 




 543 >  select the path to the cacerts file.
 544 
 545 >  See [Certificate Authority on Wikipedia](http://en.wikipedia.org/wiki/
 546    Certificate_Authority) for a better understanding of the Certificate
 547    Authority (CA). A certificates file named "cacerts" represents a system-wide
 548    keystore with CA certificates. In JDK and JRE binary bundles, the "cacerts"
 549    file contains root CA certificates from several public CAs (e.g., VeriSign,
 550    Thawte, and Baltimore). The source contain a cacerts file without CA root
 551    certificates. Formal JDK builders will need to secure permission from each
 552    public CA and include the certificates into their own custom cacerts file.
 553    Failure to provide a populated cacerts file will result in verification
 554    errors of a certificate chain during runtime. By default an empty cacerts
 555    file is provided and that should be fine for most JDK developers.
 556 
 557 <a name="cups"></a>
 558 >  **`--with-cups=`**_path_  
 559 >  select the CUPS install location
 560 
 561 >  The Common UNIX Printing System (CUPS) Headers are required for building the
 562    OpenJDK on Solaris and Linux. The Solaris header files can be obtained by
 563    installing the package **print/cups**.

 564 
 565 >  The CUPS header files can always be downloaded from
 566    [www.cups.org](http://www.cups.org).
 567 
 568 >  **`--with-cups-include=`**_path_  
 569 >  select the CUPS include directory location
 570 
 571 >  **`--with-debug-level=`**_level_  
 572 >  select the debug information level of release, fastdebug, or slowdebug
 573 
 574 >  **`--with-dev-kit=`**_path_  
 575 >  select location of the compiler install or developer install location
 576 
 577 <a name="freetype"></a>
 578 >  **`--with-freetype=`**_path_  
 579 >  select the freetype files to use.
 580 
 581 >  Expecting the freetype libraries under `lib/` and the headers under
 582    `include/`.
 583 


 999  * **Windows Error Message: `spawn failed`**  
1000    Try rebooting the system, or there could be some kind of issue with the disk
1001    or disk partition being used. Sometimes it comes with a "Permission Denied"
1002    message.
1003 
1004 *****
1005 
1006 <a name="gmake"></a>
1007 ## Appendix B: GNU make
1008 
1009 The Makefiles in the OpenJDK are only valid when used with the GNU version of
1010 the utility command `make` (usually called `gmake` on Solaris). A few notes
1011 about using GNU make:
1012 
1013  * You need GNU make version 3.81 or newer. On Windows 4.0 or newer is
1014    recommended. If the GNU make utility on your systems is not of a suitable
1015    version, see "[Building GNU make](#buildgmake)".
1016  * Place the location of the GNU make binary in the `PATH`.
1017  * **Solaris:** Do NOT use `/usr/bin/make` on Solaris. If your Solaris system
1018    has the software from the Solaris Developer Companion CD installed, you
1019    should try and use `/usr/bin/gmake` or `/usr/gnu/bin/make`.

1020  * **Windows:** Make sure you start your build inside a bash shell.
1021  * **Mac OS X:** The XCode "command line tools" must be installed on your Mac.
1022 
1023 Information on GNU make, and access to ftp download sites, are available on the
1024 [GNU make web site ](http://www.gnu.org/software/make/make.html). The latest
1025 source to GNU make is available at
1026 [ftp.gnu.org/pub/gnu/make/](http://ftp.gnu.org/pub/gnu/make/).
1027 
1028 <a name="buildgmake"></a>
1029 ### Building GNU make
1030 
1031 First step is to get the GNU make 3.81 or newer source from
1032 [ftp.gnu.org/pub/gnu/make/](http://ftp.gnu.org/pub/gnu/make/). Building is a
1033 little different depending on the OS but is basically done with:
1034 
1035       bash ./configure
1036       make
1037 
1038 *****
1039 


< prev index next >