{"id":16559860,"url":"https://github.com/itsaky/openjdk-8-android","last_synced_at":"2025-08-16T10:51:33.665Z","repository":{"id":122482649,"uuid":"441800338","full_name":"itsaky/openjdk-8-android","owner":"itsaky","description":null,"archived":false,"fork":false,"pushed_at":"2021-12-26T10:31:49.000Z","size":106366,"stargazers_count":3,"open_issues_count":0,"forks_count":3,"subscribers_count":2,"default_branch":"main","last_synced_at":"2025-07-30T01:51:26.748Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":"Java","has_issues":false,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"gpl-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/itsaky.png","metadata":{"files":{"readme":"README-builds.html","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2021-12-26T03:19:58.000Z","updated_at":"2025-06-22T01:11:42.000Z","dependencies_parsed_at":"2024-05-01T18:34:12.026Z","dependency_job_id":null,"html_url":"https://github.com/itsaky/openjdk-8-android","commit_stats":null,"previous_names":["itsaky/openjdk-8-android"],"tags_count":1,"template":false,"template_full_name":null,"purl":"pkg:github/itsaky/openjdk-8-android","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/itsaky%2Fopenjdk-8-android","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/itsaky%2Fopenjdk-8-android/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/itsaky%2Fopenjdk-8-android/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/itsaky%2Fopenjdk-8-android/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/itsaky","download_url":"https://codeload.github.com/itsaky/openjdk-8-android/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/itsaky%2Fopenjdk-8-android/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":270702479,"owners_count":24630873,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","status":"online","status_checked_at":"2025-08-16T02:00:11.002Z","response_time":91,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-10-11T20:27:18.316Z","updated_at":"2025-08-16T10:51:28.649Z","avatar_url":"https://github.com/itsaky.png","language":"Java","funding_links":[],"categories":[],"sub_categories":[],"readme":"\u003c!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\"\u003e\n\u003chtml\u003e\n \u003chead\u003e\n \u003ctitle\u003eOpenJDK Build README\u003c/title\u003e\n \u003c/head\u003e\n \u003cbody style=\"background-color:aquamarine\"\u003e\n\n \u003c!-- ====================================================== --\u003e\n \u003ctable width=\"100%\"\u003e\n \u003ctr\u003e\n \u003ctd align=\"center\"\u003e\n \u003cimg alt=\"OpenJDK\" \n src=\"http://openjdk.java.net/images/openjdk.png\" \n width=256\u003e\n \u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd align=center\u003e\n \u003ch1\u003eOpenJDK Build README\u003c/h1\u003e\n \u003c/td\u003e\n \u003c/tr\u003e\n \u003c/table\u003e\n\n \u003c!-- ====================================================== --\u003e\n \u003chr\u003e\n \u003ch2\u003e\u003ca name=\"introduction\"\u003eIntroduction\u003c/a\u003e\u003c/h2\u003e\n \u003cblockquote\u003e\n This README file contains build instructions for the\n \u003ca href=\"http://openjdk.java.net\" target=\"_blank\"\u003eOpenJDK\u003c/a\u003e.\n Building the source code for the\n OpenJDK\n requires\n a certain degree of technical expertise.\n\n \u003c!-- ====================================================== --\u003e\n \u003ch3\u003e!!!!!!!!!!!!!!! THIS IS A MAJOR RE-WRITE of this document. !!!!!!!!!!!!!\u003c/h3\u003e\n \u003cblockquote\u003e\n Some Headlines:\n \u003cul\u003e\n \u003cli\u003e\n The build is now a \"\u003ccode\u003econfigure \u0026amp;\u0026amp; make\u003c/code\u003e\" style build\n \u003c/li\u003e\n \u003cli\u003e\n Any GNU make 3.81 or newer should work\n \u003c/li\u003e\n \u003cli\u003e\n The build should scale, i.e. more processors should\n cause the build to be done in less wall-clock time\n \u003c/li\u003e\n \u003cli\u003e\n Nested or recursive make invocations have been significantly\n reduced, as has the total fork/exec or spawning\n of sub processes during the build\n \u003c/li\u003e\n \u003cli\u003e\n Windows MKS usage is no longer supported\n \u003c/li\u003e\n \u003cli\u003e\n Windows Visual Studio \u003ccode\u003evsvars*.bat\u003c/code\u003e and \n \u003ccode\u003evcvars*.bat\u003c/code\u003e files are run automatically\n \u003c/li\u003e\n \u003cli\u003e\n Ant is no longer used when building the OpenJDK\n \u003c/li\u003e\n \u003cli\u003e\n Use of ALT_* environment variables for configuring the\n build is no longer supported\n \u003c/li\u003e\n \u003c/ul\u003e\n \u003c/blockquote\u003e\n \u003c/blockquote\u003e\n\n \u003c!-- ====================================================== --\u003e\n \u003chr\u003e\n \u003ch2\u003e\u003ca name=\"contents\"\u003eContents\u003c/a\u003e\u003c/h2\u003e\n \u003cblockquote\u003e\n \u003cul\u003e\n \u003cli\u003e\u003ca href=\"#introduction\"\u003eIntroduction\u003c/a\u003e\u003c/li\u003e\n\n \u003cli\u003e\u003ca href=\"#hg\"\u003eUse of Mercurial\u003c/a\u003e\n \u003cul\u003e\n \u003cli\u003e\u003ca href=\"#get_source\"\u003eGetting the Source\u003c/a\u003e\u003c/li\u003e\n \u003cli\u003e\u003ca href=\"#repositories\"\u003eRepositories\u003c/a\u003e\u003c/li\u003e\n \u003c/ul\u003e\n \u003c/li\u003e\n\n \u003cli\u003e\u003ca href=\"#building\"\u003eBuilding\u003c/a\u003e\n \u003cul\u003e\n \u003cli\u003e\u003ca href=\"#setup\"\u003eSystem Setup\u003c/a\u003e\n \u003cul\u003e\n \u003cli\u003e\u003ca href=\"#linux\"\u003eLinux\u003c/a\u003e\u003c/li\u003e\n \u003cli\u003e\u003ca href=\"#solaris\"\u003eSolaris\u003c/a\u003e\u003c/li\u003e\n \u003cli\u003e\u003ca href=\"#macosx\"\u003eMac OS X\u003c/a\u003e\u003c/li\u003e\n \u003cli\u003e\u003ca href=\"#windows\"\u003eWindows\u003c/a\u003e\u003c/li\u003e\n \u003c/ul\u003e\n \u003c/li\u003e\n \u003cli\u003e\u003ca href=\"#configure\"\u003eConfigure\u003c/a\u003e\u003c/li\u003e\n \u003cli\u003e\u003ca href=\"#make\"\u003eMake\u003c/a\u003e\u003c/li\u003e\n \u003c/ul\u003e\n \u003c/li\u003e\n \u003cli\u003e\u003ca href=\"#testing\"\u003eTesting\u003c/a\u003e\u003c/li\u003e\n \u003c/ul\u003e\n \u003chr\u003e\n \u003cul\u003e\n \u003cli\u003e\u003ca href=\"#hints\"\u003eAppendix A: Hints and Tips\u003c/a\u003e\n \u003cul\u003e\n \u003cli\u003e\u003ca href=\"#faq\"\u003eFAQ\u003c/a\u003e\u003c/li\u003e\n \u003cli\u003e\u003ca href=\"#performance\"\u003eBuild Performance Tips\u003c/a\u003e\u003c/li\u003e\n \u003cli\u003e\u003ca href=\"#troubleshooting\"\u003eTroubleshooting\u003c/a\u003e\u003c/li\u003e\n \u003c/ul\u003e\n \u003c/li\u003e\n \u003cli\u003e\u003ca href=\"#gmake\"\u003eAppendix B: GNU Make Information\u003c/a\u003e\u003c/li\u003e\n \u003cli\u003e\u003ca href=\"#buildenvironments\"\u003eAppendix C: Build Environments\u003c/a\u003e\u003c/li\u003e\n\n \u003c!-- Leave out\n \u003cli\u003e\u003ca href=\"#mapping\"\u003eAppendix D: Mapping Old Builds to the New Builds\u003c/a\u003e\u003c/li\u003e \n --\u003e\n\n \u003c/ul\u003e\n \u003c/blockquote\u003e\n\n \u003c!-- ====================================================== --\u003e\n \u003chr\u003e\n \u003ch2\u003e\u003ca name=\"hg\"\u003eUse of Mercurial\u003c/a\u003e\u003c/h2\u003e\n \u003cblockquote\u003e\n The OpenJDK sources are maintained with the revision control system\n \u003ca href=\"http://mercurial.selenic.com/wiki/Mercurial\"\u003eMercurial\u003c/a\u003e.\n If you are new to Mercurial, please see the\n \u003ca href=\"http://mercurial.selenic.com/wiki/BeginnersGuides\"\u003e\n Beginner Guides\u003c/a\u003e\n or refer to the \u003ca href=\"http://hgbook.red-bean.com/\"\u003e\n Mercurial Book\u003c/a\u003e.\n The first few chapters of the book provide an excellent overview of\n Mercurial, what it is and how it works.\n \u003cbr\u003e\n For using Mercurial with the OpenJDK refer to the\n \u003ca href=\"http://openjdk.java.net/guide/repositories.html#installConfig\"\u003e\n Developer Guide: Installing and Configuring Mercurial\u003c/a\u003e\n section for more information.\n\n \u003ch3\u003e\u003ca name=\"get_source\"\u003eGetting the Source\u003c/a\u003e\u003c/h3\u003e\n \u003cblockquote\u003e\n To get the entire set of OpenJDK Mercurial repositories\n use the script \u003ccode\u003eget_source.sh\u003c/code\u003e located in the \n root repository:\n \u003cblockquote\u003e\n \u003ccode\u003e\n hg clone http://hg.openjdk.java.net/jdk8/jdk8 \n \u003ci\u003eYourOpenJDK\u003c/i\u003e\n \u003cbr\u003e\n cd \u003ci\u003eYourOpenJDK\u003c/i\u003e\n \u003cbr\u003e\n bash ./get_source.sh\n \u003c/code\u003e\n \u003c/blockquote\u003e\n Once you have all the repositories, keep in mind that each\n repository is its own independent repository.\n You can also re-run \u003ccode\u003e./get_source.sh\u003c/code\u003e anytime to\n pull over all the latest changesets in all the repositories.\n This set of nested repositories has been given the term\n \"forest\" and there are various ways to apply the same\n \u003ccode\u003ehg\u003c/code\u003e command to each of the repositories.\n For example, the script \u003ccode\u003emake/scripts/hgforest.sh\u003c/code\u003e\n can be used to repeat the same \u003ccode\u003ehg\u003c/code\u003e\n command on every repository, e.g.\n \u003cblockquote\u003e\n \u003ccode\u003e\n cd \u003ci\u003eYourOpenJDK\u003c/i\u003e\n \u003cbr\u003e\n bash ./make/scripts/hgforest.sh status\n \u003c/code\u003e\n \u003c/blockquote\u003e\n \u003c/blockquote\u003e\n\n \u003ch3\u003e\u003ca name=\"repositories\"\u003eRepositories\u003c/a\u003e\u003c/h3\u003e\n \u003cblockquote\u003e\n \u003cp\u003eThe set of repositories and what they contain:\u003c/p\u003e\n \u003ctable border=\"1\"\u003e\n \u003cthead\u003e\n \u003ctr\u003e\n \u003cth\u003eRepository\u003c/th\u003e\n \u003cth\u003eContains\u003c/th\u003e\n \u003c/tr\u003e\n \u003c/thead\u003e \n \u003ctbody\u003e\n \u003ctr\u003e\n \u003ctd\u003e\n . (root)\n \u003c/td\u003e\n \u003ctd\u003e\n common configure and makefile logic\n \u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003e\n hotspot\n \u003c/td\u003e\n \u003ctd\u003e\n source code and make files for building\n the OpenJDK Hotspot Virtual Machine \n \u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003e\n langtools\n \u003c/td\u003e\n \u003ctd\u003e\n source code for the OpenJDK javac and language tools\n \u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003e\n jdk\n \u003c/td\u003e\n \u003ctd\u003e\n source code and make files for building\n the OpenJDK runtime libraries and misc files\n \u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003e\n jaxp\n \u003c/td\u003e\n \u003ctd\u003e\n source code for the OpenJDK JAXP functionality\n \u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003e\n jaxws\n \u003c/td\u003e\n \u003ctd\u003e\n source code for the OpenJDK JAX-WS functionality\n \u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003e\n corba\n \u003c/td\u003e\n \u003ctd\u003e\n source code for the OpenJDK Corba functionality\n \u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003e\n nashorn\n \u003c/td\u003e\n \u003ctd\u003e\n source code for the OpenJDK JavaScript implementation\n \u003c/td\u003e\n \u003c/tr\u003e\n \u003c/tbody\u003e\n \u003c/table\u003e\n \u003c/blockquote\u003e\n\n \u003ch3\u003e\u003ca name=\"guidelines\"\u003eRepository Source Guidelines\u003c/a\u003e\u003c/h3\u003e\n \u003cblockquote\u003e\n There are some very basic guidelines:\n \u003cul\u003e\n \u003cli\u003e\n Use of whitespace in source files\n (.java, .c, .h, .cpp, and .hpp files)\n is restricted.\n No TABs, no trailing whitespace on lines, and files\n should not terminate in more than one blank line.\n \u003c/li\u003e\n \u003cli\u003e\n Files with execute permissions should not be added\n to the source repositories.\n \u003c/li\u003e\n \u003cli\u003e\n All generated files need to be kept isolated from \n the files\n maintained or managed by the source control system.\n The standard area for generated files is the top level\n \u003ccode\u003ebuild/\u003c/code\u003e directory.\n \u003c/li\u003e\n \u003cli\u003e\n The default build process should be to build the product\n and nothing else, in one form, e.g. a product (optimized),\n debug (non-optimized, -g plus assert logic), or\n fastdebug (optimized, -g plus assert logic).\n \u003c/li\u003e\n \u003cli\u003e\n The \u003ctt\u003e.hgignore\u003c/tt\u003e file in each repository\n must exist and should\n include \u003ctt\u003e^build/\u003c/tt\u003e, \u003ctt\u003e^dist/\u003c/tt\u003e and \n optionally any\n \u003ctt\u003enbproject/private\u003c/tt\u003e directories.\n \u003cstrong\u003eIt should NEVER\u003c/strong\u003e include \n anything in the\n \u003ctt\u003esrc/\u003c/tt\u003e or \u003ctt\u003etest/\u003c/tt\u003e\n or any managed directory area of a repository.\n \u003c/li\u003e\n \u003cli\u003e\n Directory names and file names should never contain\n blanks or\n non-printing characters.\n \u003c/li\u003e\n \u003cli\u003e\n Generated source or binary files should NEVER be added to\n the repository (that includes \u003ctt\u003ejavah\u003c/tt\u003e output).\n There are some exceptions to this rule, in particular\n with some of the generated configure scripts.\n \u003c/li\u003e\n \u003cli\u003e\n Files not needed for typical building\n or testing of the repository\n should not be added to the repository.\n \u003c/li\u003e\n \u003c/ul\u003e\n \u003c/blockquote\u003e\n\n \u003c/blockquote\u003e\n\n \u003c!-- ====================================================== --\u003e\n \u003chr\u003e\n \u003ch2\u003e\u003ca name=\"building\"\u003eBuilding\u003c/a\u003e\u003c/h2\u003e\n \u003cblockquote\u003e\n The very first step in building the OpenJDK is making sure the\n system itself has everything it needs to do OpenJDK builds.\n Once a system is setup, it generally doesn't need to be done again.\n \u003cbr\u003e\n Building the OpenJDK is now done with running a \n \u003ca href=\"#configure\"\u003e\u003ccode\u003econfigure\u003c/code\u003e\u003c/a\u003e\n script which will try and find and verify you have everything\n you need, followed by running\n \u003ca href=\"#gmake\"\u003e\u003ccode\u003emake\u003c/code\u003e\u003c/a\u003e, e.g.\n \u003cblockquote\u003e\n \u003cb\u003e\n \u003ccode\u003e\n bash ./configure\u003cbr\u003e\n make all\n \u003c/code\u003e\n \u003c/b\u003e\n \u003c/blockquote\u003e\n Where possible the \u003ccode\u003econfigure\u003c/code\u003e script will attempt to located the\n various components in the default locations or via component\n specific variable settings.\n When the normal defaults fail or components cannot be found,\n additional \u003ccode\u003econfigure\u003c/code\u003e options may be necessary to help \u003ccode\u003econfigure\u003c/code\u003e\n find the necessary tools for the build, or you may need to\n re-visit the setup of your system due to missing software\n packages.\n \u003cbr\u003e\n \u003cstrong\u003eNOTE:\u003c/strong\u003e The \u003ccode\u003econfigure\u003c/code\u003e script\n file does not have\n execute permissions and will need to be explicitly run with\n \u003ccode\u003ebash\u003c/code\u003e,\n see the \u003ca href=\"#guidelines\"\u003esource guidelines\u003c/a\u003e.\n\n \u003c!-- ====================================================== --\u003e\n \u003chr\u003e\n \u003ch3\u003e\u003ca name=\"setup\"\u003eSystem Setup\u003c/a\u003e\u003c/h3\u003e\n \u003cblockquote\u003e\n Before even attempting to use a system to build the OpenJDK\n there are some very basic system setups needed.\n For all systems:\n \u003cul\u003e\n \u003cli\u003e\n Be sure the GNU make utility is version 3.81 or newer,\n e.g. run \"\u003ccode\u003emake -version\u003c/code\u003e\"\n \u003c/li\u003e\n \u003cli\u003e\n Install a\n \u003ca name=\"bootjdk\"\u003eBootstrap JDK\u003c/a\u003e.\n All OpenJDK builds require access to a previously released\n JDK called the \u003ci\u003ebootstrap JDK\u003c/i\u003e or \u003ci\u003eboot JDK.\u003c/i\u003e\n The general rule is that the bootstrap JDK\n must be an instance of the previous major\n release of the JDK. In addition, there may be\n a requirement to use a release at or beyond a\n particular update level.\n \u003cbr\u003e\u0026nbsp;\u003cbr\u003e\n\n \u003cb\u003e\u003ci\u003eBuilding JDK 8 requires use of a version\n of JDK 7 that is at Update 7 or newer. JDK 8\n developers should not use JDK 8 as the boot\n JDK, to ensure that JDK 8 dependencies are\n not introduced into the parts of the system\n that are built with JDK 7.\u003c/i\u003e\u003c/b\u003e\n\n \u003cbr\u003e\u0026nbsp;\u003cbr\u003e\n The JDK 7 binaries can be downloaded from Oracle's \n \u003ca href=\"http://www.oracle.com/technetwork/java/javase/downloads/index.html\"\n target=\"_blank\"\u003eJDK 7 download site\u003c/a\u003e.\n For build performance reasons\n is very important that this bootstrap JDK be made available \n on the local disk of the machine doing the build.\n You should add its \u003ccode\u003ebin\u003c/code\u003e directory\n to the \u003ccode\u003ePATH\u003c/code\u003e environment variable.\n If \u003ccode\u003econfigure\u003c/code\u003e has any issues finding this JDK, you may\n need to use the \u003ccode\u003econfigure\u003c/code\u003e option\n \u003ccode\u003e--with-boot-jdk\u003c/code\u003e.\n \u003c/li\u003e\n \u003cli\u003e\n Ensure that GNU make, the Bootstrap JDK,\n and the compilers are all\n in your PATH environment variable\n \u003c/li\u003e\n \u003c/ul\u003e\n And for specific systems:\n \u003ctable border=\"1\"\u003e\n \u003cthead\u003e\n \u003ctr\u003e\n \u003cth\u003eLinux\u003c/th\u003e\n \u003cth\u003eSolaris\u003c/th\u003e\n \u003cth\u003eWindows\u003c/th\u003e\n \u003cth\u003eMac OS X\u003c/th\u003e\n \u003c/tr\u003e\n \u003c/thead\u003e \n \u003ctbody\u003e\n \u003ctr\u003e\n \u003ctd\u003e\n Install all the software development\n packages needed including\n \u003ca href=\"#alsa\"\u003ealsa\u003c/a\u003e,\n \u003ca href=\"#freetype\"\u003efreetype\u003c/a\u003e,\n \u003ca href=\"#cups\"\u003ecups\u003c/a\u003e, and\n \u003ca href=\"#xrender\"\u003exrender\u003c/a\u003e.\n \u003cbr\u003e\n See\n \u003ca href=\"#SDBE\"\u003especific system packages\u003c/a\u003e.\n \u003c/td\u003e\n \u003ctd\u003e\n Install all the software development\n packages needed including\n \u003ca href=\"#studio\"\u003eStudio Compilers\u003c/a\u003e,\n \u003ca href=\"#freetype\"\u003efreetype\u003c/a\u003e,\n \u003ca href=\"#cups\"\u003ecups\u003c/a\u003e, and\n \u003ca href=\"#xrender\"\u003exrender\u003c/a\u003e.\n \u003cbr\u003e\n See\n \u003ca href=\"#SDBE\"\u003especific system packages\u003c/a\u003e.\n \u003c/td\u003e\n \u003ctd\u003e\n \u003cul\u003e\n \u003cli\u003e\n Install one of\n \u003ca href=\"#cygwin\"\u003eCYGWIN\u003c/a\u003e or\n \u003ca href=\"#msys\"\u003eMinGW/MSYS\u003c/a\u003e\n \u003c/li\u003e\n \u003cli\u003e\n Install\n \u003ca href=\"#vs2010\"\u003eVisual Studio 2010\u003c/a\u003e\n \u003c/li\u003e\n \u003c/ul\u003e\n \u003c/td\u003e\n \u003ctd\u003e\n Install \n \u003ca href=\"https://developer.apple.com/xcode/\"\u003eXCode 4.5.2\u003c/a\u003e \n and also install the \"Command line tools\" found under the\n preferences pane \"Downloads\"\n \u003c/td\u003e\n \u003c/tr\u003e\n \u003c/tbody\u003e\n \u003c/table\u003e\n\n \u003ch4\u003e\u003ca name=\"linux\"\u003eLinux\u003c/a\u003e\u003c/h4\u003e\n \u003cblockquote\u003e\n With Linux, try and favor the system packages over \n building your own\n or getting packages from other areas.\n Most Linux builds should be possible with the system's\n available packages.\n \u003cbr\u003e\n Note that some Linux systems have a habit of pre-populating\n your environment variables for you, for example \u003ccode\u003eJAVA_HOME\u003c/code\u003e\n might get pre-defined for you to refer to the JDK installed on\n your Linux system.\n You will need to unset \u003ccode\u003eJAVA_HOME\u003c/code\u003e.\n It's a good idea to run \u003ccode\u003eenv\u003c/code\u003e and verify the\n environment variables you are getting from the default system\n settings make sense for building the OpenJDK.\n\n \u003c/blockquote\u003e\n\n \u003ch4\u003e\u003ca name=\"solaris\"\u003eSolaris\u003c/a\u003e\u003c/h4\u003e\n \u003cblockquote\u003e\n \u003ch5\u003e\u003ca name=\"studio\"\u003eStudio Compilers\u003c/a\u003e\u003c/h5\u003e\n \u003cblockquote\u003e\n At a minimum, the\n \u003ca href=\"http://www.oracle.com/technetwork/server-storage/solarisstudio/downloads/index.htm\" target=\"_blank\"\u003e\n Studio 12 Update 1 Compilers\u003c/a\u003e\n (containing version 5.10 of the C and C++ compilers) is required,\n including specific patches.\n \u003cp\u003e\n The Solaris SPARC patch list is:\n \u003cul\u003e\n \u003cli\u003e\n 118683-05: SunOS 5.10: Patch for profiling libraries and assembler\n \u003c/li\u003e\n \u003cli\u003e\n 119963-21: SunOS 5.10: Shared library patch for C++\n \u003c/li\u003e\n \u003cli\u003e\n 120753-08: SunOS 5.10: Microtasking libraries (libmtsk) patch\n \u003c/li\u003e\n \u003cli\u003e\n 128228-09: Sun Studio 12 Update 1: Patch for Sun C++ Compiler\n \u003c/li\u003e\n \u003cli\u003e\n 141860-03: Sun Studio 12 Update 1: Patch for Compiler Common patch for Sun C C++ F77 F95\n \u003c/li\u003e\n \u003cli\u003e\n 141861-05: Sun Studio 12 Update 1: Patch for Sun C Compiler\n \u003c/li\u003e\n \u003cli\u003e\n 142371-01: Sun Studio 12.1 Update 1: Patch for dbx\n \u003c/li\u003e\n \u003cli\u003e\n 143384-02: Sun Studio 12 Update 1: Patch for debuginfo handling\n \u003c/li\u003e\n \u003cli\u003e\n 143385-02: Sun Studio 12 Update 1: Patch for Compiler Common patch for Sun C C++ F77 F95\n \u003c/li\u003e\n \u003cli\u003e\n 142369-01: Sun Studio 12.1: Patch for Performance Analyzer Tools\n \u003c/li\u003e\n \u003c/ul\u003e\n \u003cp\u003e\n The Solaris X86 patch list is:\n \u003cul\u003e\n \u003cli\u003e\n 119961-07: SunOS 5.10_x86, x64, Patch for profiling libraries and assembler\n \u003c/li\u003e\n \u003cli\u003e\n 119964-21: SunOS 5.10_x86: Shared library patch for C++_x86\n \u003c/li\u003e\n \u003cli\u003e\n 120754-08: SunOS 5.10_x86: Microtasking libraries (libmtsk) patch\n \u003c/li\u003e\n \u003cli\u003e\n 141858-06: Sun Studio 12 Update 1_x86: Sun Compiler Common patch for x86 backend\n \u003c/li\u003e\n \u003cli\u003e\n 128229-09: Sun Studio 12 Update 1_x86: Patch for C++ Compiler\n \u003c/li\u003e\n \u003cli\u003e\n 142363-05: Sun Studio 12 Update 1_x86: Patch for C Compiler\n \u003c/li\u003e\n \u003cli\u003e\n 142368-01: Sun Studio 12.1_x86: Patch for Performance Analyzer Tools\n \u003c/li\u003e\n \u003c/ul\u003e\n \u003cp\u003e \n Place the \u003ccode\u003ebin\u003c/code\u003e directory in \u003ccode\u003ePATH\u003c/code\u003e.\n \u003cp\u003e\n The Oracle Solaris Studio Express compilers at:\n \u003ca href=\"http://www.oracle.com/technetwork/server-storage/solarisstudio/downloads/index-jsp-142582.html\" target=\"_blank\"\u003e\n Oracle Solaris Studio Express Download site\u003c/a\u003e\n are also an option, although these compilers have not\n been extensively used yet.\n \u003c/blockquote\u003e\n\n \u003c/blockquote\u003e \u003c!-- Solaris --\u003e\n\n \u003ch4\u003e\u003ca name=\"windows\"\u003eWindows\u003c/a\u003e\u003c/h4\u003e\n \u003cblockquote\u003e\n\n \u003ch5\u003e\u003ca name=\"toolkit\"\u003eWindows Unix Toolkit\u003c/a\u003e\u003c/h5\u003e\n \u003cblockquote\u003e\n Building on Windows requires a Unix-like environment, notably a \n Unix-like shell.\n There are several such environments available of which \n \u003ca href=\"http://www.cygwin.com/\"\u003eCygwin\u003c/a\u003e and \n \u003ca href=\"http://www.mingw.org/wiki/MSYS\"\u003eMinGW/MSYS\u003c/a\u003e are \n currently supported for\n the OpenJDK build. One of the differences of these \n systems from standard Windows tools is the way\n they handle Windows path names, particularly path names which contain\n spaces, backslashes as path separators and possibly drive letters. \n Depending\n on the use case and the specifics of each environment these path \n problems can\n be solved by a combination of quoting whole paths, translating \n backslashes to\n forward slashes, escaping backslashes with additional backslashes and\n translating the path names to their \n \u003ca href=\"http://en.wikipedia.org/wiki/8.3_filename\"\u003e\n \"8.3\" version\u003c/a\u003e.\n\n \u003ch6\u003e\u003ca name=\"cygwin\"\u003eCYGWIN\u003c/a\u003e\u003c/h6\u003e\n \u003cblockquote\u003e\n CYGWIN is an open source, Linux-like environment which tries to emulate\n a complete POSIX layer on Windows. It tries to be smart about path names\n and can usually handle all kinds of paths if they are correctly quoted\n or escaped although internally it maps drive letters \u003ccode\u003e\u0026lt;drive\u0026gt;:\u003c/code\u003e \n to a virtual directory \u003ccode\u003e/cygdrive/\u0026lt;drive\u0026gt;\u003c/code\u003e.\n \u003cp\u003e\n You can always use the \u003ccode\u003ecygpath\u003c/code\u003e utility to map pathnames with spaces\n or the backslash character into the \u003ccode\u003eC:/\u003c/code\u003e style of pathname\n (called 'mixed'), e.g. \u003ccode\u003ecygpath -s -m \"\u003ci\u003epath\u003c/i\u003e\"\u003c/code\u003e.\n \u003c/p\u003e\n \u003cp\u003e\n Note that the use of CYGWIN creates a unique problem with regards to\n setting \u003ca href=\"#path\"\u003e\u003ccode\u003ePATH\u003c/code\u003e\u003c/a\u003e. Normally on Windows\n the \u003ccode\u003ePATH\u003c/code\u003e variable contains directories\n separated with the \";\" character (Solaris and Linux use \":\").\n With CYGWIN, it uses \":\", but that means that paths like \"C:/path\"\n cannot be placed in the CYGWIN version of \u003ccode\u003ePATH\u003c/code\u003e and\n instead CYGWIN uses something like \u003ccode\u003e/cygdrive/c/path\u003c/code\u003e\n which CYGWIN understands, but only CYGWIN understands.\n \u003c/p\u003e\n \u003cp\u003e\n The OpenJDK build requires CYGWIN version 1.7.16 or newer.\n Information about CYGWIN can\n be obtained from the CYGWIN website at\n \u003ca href=\"http://www.cygwin.com\" target=\"_blank\"\u003ewww.cygwin.com\u003c/a\u003e.\n \u003c/p\u003e\n \u003cp\u003e\n By default CYGWIN doesn't install all the tools required for building\n the OpenJDK.\n Along with the default installation, you need to install\n the following tools.\n \u003cblockquote\u003e\n \u003ctable border=\"1\"\u003e\n \u003cthead\u003e\n \u003ctr\u003e\n \u003ctd\u003eBinary Name\u003c/td\u003e\n \u003ctd\u003eCategory\u003c/td\u003e\n \u003ctd\u003ePackage\u003c/td\u003e\n \u003ctd\u003eDescription\u003c/td\u003e\n \u003c/tr\u003e\n \u003c/thead\u003e\n \u003ctbody\u003e\n \u003ctr\u003e\n \u003ctd\u003ear.exe\u003c/td\u003e\n \u003ctd\u003eDevel\u003c/td\u003e\n \u003ctd\u003ebinutils\u003c/td\u003e\n \u003ctd\u003e\n The GNU assembler, linker and binary utilities\n \u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003emake.exe\u003c/td\u003e\n \u003ctd\u003eDevel\u003c/td\u003e\n \u003ctd\u003emake\u003c/td\u003e\n \u003ctd\u003e\n The GNU version of the 'make' utility built for CYGWIN\n \u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003em4.exe\u003c/td\u003e\n \u003ctd\u003eInterpreters\u003c/td\u003e\n \u003ctd\u003em4\u003c/td\u003e\n \u003ctd\u003e\n GNU implementation of the traditional Unix macro\n processor\n \u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003ecpio.exe\u003c/td\u003e\n \u003ctd\u003eUtils\u003c/td\u003e\n \u003ctd\u003ecpio\u003c/td\u003e\n \u003ctd\u003e\n A program to manage archives of files\n \u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003egawk.exe\u003c/td\u003e\n \u003ctd\u003eUtils\u003c/td\u003e\n \u003ctd\u003eawk\u003c/td\u003e\n \u003ctd\u003e\n Pattern-directed scanning and processing language\n \u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003efile.exe\u003c/td\u003e\n \u003ctd\u003eUtils\u003c/td\u003e\n \u003ctd\u003efile\u003c/td\u003e\n \u003ctd\u003e\n Determines file type using 'magic' numbers\n \u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003ezip.exe\u003c/td\u003e\n \u003ctd\u003eArchive\u003c/td\u003e\n \u003ctd\u003ezip\u003c/td\u003e\n \u003ctd\u003e\n Package and compress (archive) files\n \u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003eunzip.exe\u003c/td\u003e\n \u003ctd\u003eArchive\u003c/td\u003e\n \u003ctd\u003eunzip\u003c/td\u003e\n \u003ctd\u003e\n Extract compressed files in a ZIP archive\n \u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003efree.exe\u003c/td\u003e\n \u003ctd\u003eSystem\u003c/td\u003e\n \u003ctd\u003eprocps\u003c/td\u003e\n \u003ctd\u003e\n Display amount of free and used memory in the system\n \u003c/td\u003e\n \u003c/tr\u003e\n \u003c/tbody\u003e\n \u003c/table\u003e\n \u003c/blockquote\u003e\n Note that the CYGWIN software can conflict with other non-CYGWIN\n software on your Windows system.\n CYGWIN provides a\n \u003ca href=\"http://cygwin.com/faq/faq.using.html\" target=\"_blank\"\u003eFAQ\u003c/a\u003e for\n known issues and problems, of particular interest is the\n section on\n \u003ca href=\"http://cygwin.com/faq/faq.using.html#faq.using.bloda\" target=\"_blank\"\u003e\n BLODA (applications that interfere with CYGWIN)\u003c/a\u003e.\n \u003c/blockquote\u003e\n\n \u003ch6\u003e\u003ca name=\"msys\"\u003eMinGW/MSYS\u003c/a\u003e\u003c/h6\u003e \n \u003cblockquote\u003e\n MinGW (\"Minimalist GNU for Windows\") is a collection of free Windows\n specific header files and import libraries combined with GNU toolsets that\n allow one to produce native Windows programs that do not rely on any\n 3rd-party C runtime DLLs. MSYS is a supplement to MinGW which allows building\n applications and programs which rely on traditional UNIX tools to\n be present. Among others this includes tools like \u003ccode\u003ebash\u003c/code\u003e\n and \u003ccode\u003emake\u003c/code\u003e.\n See \u003ca href=\"http://www.mingw.org/wiki/MSYS\" target=\"_blank\"\u003eMinGW/MSYS\u003c/a\u003e\n for more information.\n \u003cp\u003e\n Like Cygwin, MinGW/MSYS can handle different types of path formats. They\n are internally converted to paths with forward slashes and drive letters\n \u003ccode\u003e\u0026lt;drive\u0026gt;:\u003c/code\u003e replaced by a virtual\n directory \u003ccode\u003e/\u0026lt;drive\u0026gt;\u003c/code\u003e. Additionally, MSYS automatically\n detects binaries compiled for the MSYS environment and feeds them with the\n internal, Unix-style path names. If native Windows applications are called\n from within MSYS programs their path arguments are automatically converted\n back to Windows style path names with drive letters and backslashes as\n path separators. This may cause problems for Windows applications which\n use forward slashes as parameter separator (e.g. \u003ccode\u003ecl /nologo /I\u003c/code\u003e)\n because MSYS may wrongly \u003ca href=\"http://mingw.org/wiki/Posix_path_conversion\"\u003e\n replace such parameters by drive letters\u003c/a\u003e.\n \u003c/p\u003e\n \u003cp\u003e\n In addition to the tools which will be installed\n by default, you have\n to manually install the\n \u003ccode\u003emsys-zip\u003c/code\u003e and\n \u003ccode\u003emsys-unzip\u003c/code\u003e packages.\n This can be easily done with the MinGW command line installer:\n \u003cblockquote\u003e \n \u003ccode\u003emingw-get.exe install msys-zip\u003c/code\u003e\n \u003cbr\u003e\n \u003ccode\u003emingw-get.exe install msys-unzip\u003c/code\u003e\n \u003c/blockquote\u003e \n \u003c/blockquote\u003e\n\n \u003c/blockquote\u003e\n\n \u003ch5\u003e\u003ca name=\"vs2010\"\u003eVisual Studio 2010 Compilers\u003c/a\u003e\u003c/h5\u003e\n \u003cblockquote\u003e\n \u003cp\u003e\n The 32-bit and 64-bit OpenJDK Windows build requires\n Microsoft Visual Studio C++ 2010 (VS2010) Professional\n Edition or Express compiler.\n The compiler and other tools are expected to reside\n in the location defined by the variable\n \u003ccode\u003eVS100COMNTOOLS\u003c/code\u003e which\n is set by the Microsoft Visual Studio installer.\n \u003c/p\u003e\n \u003cp\u003e\n Only the C++ part of VS2010 is needed.\n Try to let the installation go to the default \n install directory.\n Always reboot your system after installing VS2010.\n The system environment variable VS100COMNTOOLS \n should be\n set in your environment.\n \u003c/p\u003e\n \u003cp\u003e\n Make sure that TMP and TEMP are also set \n in the environment\n and refer to Windows paths that exist, \n like \u003ccode\u003eC:\\temp\u003c/code\u003e,\n not \u003ccode\u003e/tmp\u003c/code\u003e, not \u003ccode\u003e/cygdrive/c/temp\u003c/code\u003e, \n and not \u003ccode\u003eC:/temp\u003c/code\u003e.\n \u003ccode\u003eC:\\temp\u003c/code\u003e is just an example, \n it is assumed that this area is\n private to the user, so by default \n after installs you should\n see a unique user path in these variables.\n \u003c/p\u003e\n \u003c/blockquote\u003e\n\n\n \u003c/blockquote\u003e \u003c!-- Windows --\u003e\n\n \u003ch4\u003e\u003ca name=\"macosx\"\u003eMac OS X\u003c/a\u003e\u003c/h4\u003e\n \u003cblockquote\u003e\n Make sure you get the right XCode version.\n \u003c/blockquote\u003e \u003c!-- Mac OS X --\u003e\n\n \u003c/blockquote\u003e\n\n \u003c!-- ====================================================== --\u003e\n \u003chr\u003e\n \u003ch3\u003e\u003ca name=\"configure\"\u003eConfigure\u003c/a\u003e\u003c/h3\u003e\n \u003cblockquote\u003e\n The basic invocation of the \u003ccode\u003econfigure\u003c/code\u003e script\n looks like:\n \u003cblockquote\u003e\n \u003cb\u003e\u003ccode\u003ebash ./configure [\u003ci\u003eoptions\u003c/i\u003e]\u003c/code\u003e\u003c/b\u003e\n \u003c/blockquote\u003e\n This will create an output directory containing the\n \"configuration\" and setup an area for the build result.\n This directory typically looks like:\n \u003cblockquote\u003e\n \u003cb\u003e\u003ccode\u003ebuild/linux-x64-normal-server-release\u003c/code\u003e\u003c/b\u003e\n \u003c/blockquote\u003e\n \u003ccode\u003econfigure\u003c/code\u003e will try to figure out what system you are running on \n and where all necessary build components are.\n If you have all prerequisites for building installed,\n it should find everything.\n If it fails to detect any component automatically,\n it will exit and inform you about the problem.\n When this happens, read more below in\n \u003ca href=\"#configureoptions\"\u003ethe \u003ccode\u003econfigure\u003c/code\u003e options\u003c/a\u003e.\n \u003cp\u003e\n Some examples:\n \u003c/p\u003e\n \u003ctable border=\"1\"\u003e\n \u003cthead\u003e\n \u003ctr\u003e\n \u003cth\u003eDescription\u003c/th\u003e\n \u003cth\u003eConfigure Command Line\u003c/th\u003e\n \u003c/tr\u003e\n \u003c/thead\u003e \n \u003ctbody\u003e\n \u003ctr\u003e\n \u003ctd\u003eWindows 32bit build with freetype specified\u003c/td\u003e\n \u003ctd\u003e\n \u003ccode\u003ebash ./configure --with-freetype=/cygdrive/c/freetype-i586 --with-target-bits=32\u003c/code\u003e \n \u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003eDebug 64bit Build\u003c/td\u003e\n \u003ctd\u003e\n \u003ccode\u003ebash ./configure --enable-debug --with-target-bits=64\u003c/code\u003e \n \u003c/td\u003e\n \u003c/tr\u003e\n \u003c/tbody\u003e\n \u003c/table\u003e\n\n \u003c!-- ====================================================== --\u003e\n \u003ch4\u003e\u003ca name=\"configureoptions\"\u003eConfigure Options\u003c/a\u003e\u003c/h4\u003e\n \u003cblockquote\u003e\n Complete details on all the OpenJDK \u003ccode\u003econfigure\u003c/code\u003e options can\n be seen with:\n \u003cblockquote\u003e\n \u003cb\u003e\u003ccode\u003ebash ./configure --help=short\u003c/code\u003e\u003c/b\u003e\n \u003c/blockquote\u003e\n Use \u003ccode\u003e-help\u003c/code\u003e to see all the \u003ccode\u003econfigure\u003c/code\u003e options\n available.\n\n You can generate any number of different configurations,\n e.g. debug, release, 32, 64, etc.\n\n Some of the more commonly used \u003ccode\u003econfigure\u003c/code\u003e options are:\n\n \u003ctable border=\"1\"\u003e\n \u003cthead\u003e\n \u003ctr\u003e\n \u003cth width=\"300\"\u003eOpenJDK Configure Option\u003c/th\u003e\n \u003cth\u003eDescription\u003c/th\u003e\n \u003c/tr\u003e\n \u003c/thead\u003e \n \u003ctbody\u003e\n \u003ctr\u003e\n \u003ctd\u003e\u003cb\u003e\u003ccode\u003e--enable-debug\u003c/code\u003e\u003c/b\u003e\u003c/td\u003e\n \u003ctd\u003e\n set the debug level to fastdebug (this is a shorthand for\n \u003ccode\u003e--with-debug-level=fastdebug\u003c/code\u003e)\n \u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003e\u003cb\u003e\u003ccode\u003e--with-alsa=\u003c/code\u003e\u003c/b\u003e\u003ci\u003epath\u003c/i\u003e\u003c/td\u003e\n \u003ctd\u003e\n select the location of the\n \u003ca name=\"alsa\"\u003eAdvanced Linux Sound Architecture (ALSA)\u003c/a\u003e\n \u003cbr\u003e \n Version 0.9.1 or newer of the ALSA files are\n required for building the OpenJDK on Linux.\n These Linux files are usually available from an \"alsa\"\n of \"libasound\"\n development package,\n and it's highly recommended that you try and use\n the package provided by the particular version of Linux that\n you are using.\n \u003c/td\u003e\n \u003c/tr\u003e \n \u003ctr\u003e\n \u003ctd\u003e\u003cb\u003e\u003ccode\u003e--with-boot-jdk=\u003c/code\u003e\u003c/b\u003e\u003ci\u003epath\u003c/i\u003e\u003c/td\u003e\n \u003ctd\u003e\n select the \u003ca href=\"#bootjdk\"\u003eBootstrap JDK\u003c/a\u003e\n \u003c/td\u003e\n \u003c/tr\u003e \n \u003ctr\u003e\n \u003ctd\u003e\u003cb\u003e\u003ccode\u003e--with-boot-jdk-jvmargs=\u003c/code\u003e\u003c/b\u003e\"\u003ci\u003eargs\u003c/i\u003e\"\u003c/td\u003e\n \u003ctd\u003e\n provide the JVM options to be used to run the \n \u003ca href=\"#bootjdk\"\u003eBootstrap JDK\u003c/a\u003e\n \u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003e\u003cb\u003e\u003ccode\u003e--with-cacerts=\u003c/code\u003e\u003c/b\u003e\u003ci\u003epath\u003c/i\u003e\u003c/td\u003e\n \u003ctd\u003e\n select the path to the cacerts file.\n \u003cbr\u003e\n See \u003ca href=\"http://en.wikipedia.org/wiki/Certificate_Authority\" target=\"_blank\"\u003e\n http://en.wikipedia.org/wiki/Certificate_Authority\u003c/a\u003e\n for a better understanding of the Certificate Authority (CA).\n A certificates file named \"cacerts\"\n represents a system-wide keystore with CA certificates. \n In JDK and JRE\n binary bundles, the \"cacerts\" file contains root CA certificates from\n several public CAs (e.g., VeriSign, Thawte, and Baltimore).\n The source contain a cacerts file\n without CA root certificates. \n Formal JDK builders will need to secure\n permission from each public CA and include the certificates into their\n own custom cacerts file. \n Failure to provide a populated cacerts file\n will result in verification errors of a certificate chain during runtime.\n By default an empty cacerts file is provided and that should be\n fine for most JDK developers.\n \u003c/td\u003e\n \u003c/tr\u003e \n \u003ctr\u003e\n \u003ctd\u003e\u003cb\u003e\u003ccode\u003e--with-cups=\u003c/code\u003e\u003c/b\u003e\u003ci\u003epath\u003c/i\u003e\u003c/td\u003e\n \u003ctd\u003e\n select the CUPS install location\n \u003cbr\u003e\n The\n \u003ca name=\"cups\"\u003eCommon UNIX Printing System (CUPS) Headers\u003c/a\u003e\n are required for building the \n OpenJDK on Solaris and Linux.\n The Solaris header files can be obtained by installing \n the package \u003cstrong\u003eSFWcups\u003c/strong\u003e from the Solaris Software\n Companion CD/DVD, these often will be installed into the\n directory \u003ccode\u003e/opt/sfw/cups\u003c/code\u003e.\n \u003cbr\u003e\n The CUPS header files can always be downloaded from\n \u003ca href=\"http://www.cups.org\" target=\"_blank\"\u003ewww.cups.org\u003c/a\u003e.\n \u003c/td\u003e\n \u003c/tr\u003e \n \u003ctr\u003e\n \u003ctd\u003e\u003cb\u003e\u003ccode\u003e--with-cups-include=\u003c/code\u003e\u003c/b\u003e\u003ci\u003epath\u003c/i\u003e\u003c/td\u003e\n \u003ctd\u003e\n select the CUPS include directory location\n \u003c/td\u003e\n \u003c/tr\u003e \n \u003ctr\u003e\n \u003ctd\u003e\u003cb\u003e\u003ccode\u003e--with-debug-level=\u003c/code\u003e\u003c/b\u003e\u003ci\u003elevel\u003c/i\u003e\u003c/td\u003e\n \u003ctd\u003e\n select the debug information level of release,\n fastdebug, or slowdebug\n \u003c/td\u003e\n \u003c/tr\u003e \n \u003ctr\u003e\n \u003ctd\u003e\u003cb\u003e\u003ccode\u003e--with-dev-kit=\u003c/code\u003e\u003c/b\u003e\u003ci\u003epath\u003c/i\u003e\u003c/td\u003e\n \u003ctd\u003e\n select location of the compiler install or\n developer install location\n \u003c/td\u003e\n \u003c/tr\u003e \n \u003ctr\u003e\n \u003ctd\u003e\u003cb\u003e\u003ccode\u003e--with-freetype=\u003c/code\u003e\u003c/b\u003e\u003ci\u003epath\u003c/i\u003e\u003c/td\u003e\n \u003ctd\u003e\n select the freetype files to use.\n \u003cbr\u003e\n Expecting the\n \u003ca name=\"freetype\"\u003efreetype\u003c/a\u003e libraries under\n \u003ccode\u003elib/\u003c/code\u003e and the\n headers under \u003ccode\u003einclude/\u003c/code\u003e.\n \u003cbr\u003e\n Version 2.3 or newer of FreeType is required.\n On Unix systems required files can be available as part of your\n distribution (while you still may need to upgrade them).\n Note that you need development version of package that \n includes both the FreeType library and header files.\n \u003cbr\u003e\n You can always download latest FreeType version from the\n \u003ca href=\"http://www.freetype.org\" target=\"_blank\"\u003eFreeType website\u003c/a\u003e.\n \u003cbr\u003e\n Building the freetype 2 libraries from scratch is also possible,\n however on Windows refer to the\n \u003ca href=\"http://freetype.freedesktop.org/wiki/FreeType_DLL\"\u003e\n Windows FreeType DLL build instructions\u003c/a\u003e.\n \u003cbr\u003e\n Note that by default FreeType is built with byte code hinting\n support disabled due to licensing restrictions.\n In this case, text appearance and metrics are expected to\n differ from Sun's official JDK build.\n See\n \u003ca href=\"http://freetype.sourceforge.net/freetype2/index.html\"\u003e\n the SourceForge FreeType2 Home Page\n \u003c/a\u003e\n for more information.\n \u003c/td\u003e\n \u003c/tr\u003e \n \u003ctr\u003e\n \u003ctd\u003e\u003cb\u003e\u003ccode\u003e--with-import-hotspot=\u003c/code\u003e\u003c/b\u003e\u003ci\u003epath\u003c/i\u003e\u003c/td\u003e\n \u003ctd\u003e\n select the location to find hotspot\n binaries from a previous build to avoid building\n hotspot\n \u003c/td\u003e\n \u003c/tr\u003e \n \u003ctr\u003e\n \u003ctd\u003e\u003cb\u003e\u003ccode\u003e--with-target-bits=\u003c/code\u003e\u003c/b\u003e\u003ci\u003earg\u003c/i\u003e\u003c/td\u003e\n \u003ctd\u003e\n select 32 or 64 bit build\n \u003c/td\u003e\n \u003c/tr\u003e \n \u003ctr\u003e\n \u003ctd\u003e\u003cb\u003e\u003ccode\u003e--with-jvm-variants=\u003c/code\u003e\u003c/b\u003e\u003ci\u003evariants\u003c/i\u003e\u003c/td\u003e\n \u003ctd\u003e\n select the JVM variants to build from, comma\n separated list that can include:\n server, client, kernel, zero and zeroshark\n \u003c/td\u003e\n \u003c/tr\u003e \n \u003ctr\u003e\n \u003ctd\u003e\u003cb\u003e\u003ccode\u003e--with-memory-size=\u003c/code\u003e\u003c/b\u003e\u003ci\u003esize\u003c/i\u003e\u003c/td\u003e\n \u003ctd\u003e\n select the RAM size that GNU make will think\n this system has\n \u003c/td\u003e\n \u003c/tr\u003e \n \u003ctr\u003e\n \u003ctd\u003e\u003ca name=\"msvcrNN\"\u003e\u003cb\u003e\u003ccode\u003e--with-msvcr-dll=\u003c/code\u003e\u003c/b\u003e\u003ci\u003epath\u003c/i\u003e\u003c/a\u003e\u003c/td\u003e\n \u003ctd\u003e\n select the \u003ccode\u003emsvcr100.dll\u003c/code\u003e\n file to include in the\n Windows builds (C/C++ runtime library for\n Visual Studio).\n \u003cbr\u003e\n This is usually picked up automatically\n from the redist\n directories of Visual Studio 2010.\n \u003c/td\u003e\n \u003c/tr\u003e \n \u003ctr\u003e\n \u003ctd\u003e\u003cb\u003e\u003ccode\u003e--with-num-cores=\u003c/code\u003e\u003c/b\u003e\u003ci\u003ecores\u003c/i\u003e\u003c/td\u003e\n \u003ctd\u003e\n select the number of cores to use (processor\n count or CPU count)\n \u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003e\u003cb\u003e\u003ccode\u003e--with-x=\u003c/code\u003e\u003c/b\u003e\u003ci\u003epath\u003c/i\u003e\u003c/td\u003e\n \u003ctd\u003e\n select the location of the X11 and xrender files.\n \u003cbr\u003e\n The\n \u003ca name=\"xrender\"\u003eXRender Extension Headers\u003c/a\u003e\n are required for building the\n OpenJDK on Solaris and Linux.\n \u003cbr\u003e\n The Linux header files are usually available from a \"Xrender\"\n development package, it's recommended that you try and use\n the package provided by the particular distribution of Linux that\n you are using.\n \u003cbr\u003e\n The Solaris XRender header files is\n included with the other X11 header files\n in the package \u003cstrong\u003eSFWxwinc\u003c/strong\u003e\n on new enough versions of\n Solaris and will be installed in\n \u003ccode\u003e/usr/X11/include/X11/extensions/Xrender.h\u003c/code\u003e or\n \u003ccode\u003e/usr/openwin/share/include/X11/extensions/Xrender.h\u003c/code\u003e\n \u003c/td\u003e\n \u003c/tr\u003e\n \u003c/tbody\u003e\n \u003c/table\u003e\n \u003c/blockquote\u003e\n\n \u003c/blockquote\u003e\n\n \u003c!-- ====================================================== --\u003e\n \u003chr\u003e\n \u003ch3\u003e\u003ca name=\"make\"\u003eMake\u003c/a\u003e\u003c/h3\u003e\n \u003cblockquote\u003e\n The basic invocation of the \u003ccode\u003emake\u003c/code\u003e utility\n looks like:\n \u003cblockquote\u003e\n \u003cb\u003e\u003ccode\u003emake all\u003c/code\u003e\u003c/b\u003e\n \u003c/blockquote\u003e\n This will start the build to the output directory containing the\n \"configuration\" that was created by the \u003ccode\u003econfigure\u003c/code\u003e\n script. Run \u003ccode\u003emake help\u003c/code\u003e for more information on\n the available targets.\n \u003cbr\u003e\n There are some of the make targets that\n are of general interest:\n \u003ctable border=\"1\"\u003e\n \u003cthead\u003e\n \u003ctr\u003e\n \u003cth\u003eMake Target\u003c/th\u003e\n \u003cth\u003eDescription\u003c/th\u003e\n \u003c/tr\u003e\n \u003c/thead\u003e \n \u003ctbody\u003e\n \u003ctr\u003e\n \u003ctd\u003e\u003ci\u003eempty\u003c/i\u003e\u003c/td\u003e\n \u003ctd\u003ebuild everything but no images\u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003e\u003cb\u003e\u003ccode\u003eall\u003c/code\u003e\u003c/b\u003e\u003c/td\u003e\n \u003ctd\u003ebuild everything including images\u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003e\u003cb\u003e\u003ccode\u003eall-conf\u003c/code\u003e\u003c/b\u003e\u003c/td\u003e\n \u003ctd\u003ebuild all configurations\u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003e\u003cb\u003e\u003ccode\u003eimages\u003c/code\u003e\u003c/b\u003e\u003c/td\u003e\n \u003ctd\u003ecreate complete j2sdk and j2re images\u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003e\u003cb\u003e\u003ccode\u003einstall\u003c/code\u003e\u003c/b\u003e\u003c/td\u003e\n \u003ctd\u003einstall the generated images locally, \n typically in \u003ccode\u003e/usr/local\u003c/code\u003e\u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003e\u003cb\u003e\u003ccode\u003eclean\u003c/code\u003e\u003c/b\u003e\u003c/td\u003e\n \u003ctd\u003eremove all files generated by make, \n but not those generated by \u003ccode\u003econfigure\u003c/code\u003e\u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003e\u003cb\u003e\u003ccode\u003edist-clean\u003c/code\u003e\u003c/b\u003e\u003c/td\u003e\n \u003ctd\u003eremove all files generated by both \n and \u003ccode\u003econfigure\u003c/code\u003e (basically killing the configuration)\u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003e\u003cb\u003e\u003ccode\u003ehelp\u003c/code\u003e\u003c/b\u003e\u003c/td\u003e\n \u003ctd\u003egive some help on using \u003ccode\u003emake\u003c/code\u003e, \n including some interesting make targets\u003c/td\u003e\n \u003c/tr\u003e\n \u003c/tbody\u003e\n \u003c/table\u003e\n \u003c/blockquote\u003e\n \u003c/blockquote\u003e\n\n \u003c!-- ====================================================== --\u003e\n \u003chr\u003e\n \u003ch2\u003e\u003ca name=\"testing\"\u003eTesting\u003c/a\u003e\u003c/h2\u003e\n \u003cblockquote\u003e\n When the build is completed, you should see the generated\n binaries and associated files in the \u003ccode\u003ej2sdk-image\u003c/code\u003e \n directory in the output directory. \n In particular, the \n \u003ccode\u003ebuild/\u003ci\u003e*\u003c/i\u003e/images/j2sdk-image/bin\u003c/code\u003e\n directory should contain executables for the \n OpenJDK tools and utilities for that configuration.\n The testing tool \u003ccode\u003ejtreg\u003c/code\u003e will be needed\n and can be found at:\n \u003ca href=\"http://openjdk.java.net/jtreg/\" target=\"_blank\"\u003e\n the jtreg site\u003c/a\u003e.\n The provided regression tests in the repositories\n can be run with the command:\n \u003cblockquote\u003e\n \u003ccode\u003e\u003cb\u003ecd test \u0026amp;\u0026amp; make PRODUCT_HOME=`pwd`/../build/*/images/j2sdk-image all\u003c/b\u003e\u003c/code\u003e\n \u003c/blockquote\u003e\n \u003c/blockquote\u003e\n\n \u003c!-- ====================================================== --\u003e\n \u003c!-- ====================================================== --\u003e\n \u003c!-- ====================================================== --\u003e\n \u003c!-- ====================================================== --\u003e\n \u003c!-- ====================================================== --\u003e\n \u003c!-- ====================================================== --\u003e\n \u003c!-- ====================================================== --\u003e\n \u003c!-- ====================================================== --\u003e\n \u003c!-- ====================================================== --\u003e\n\n \u003c!-- ====================================================== --\u003e\n \u003chr\u003e\n \u003ch2\u003e\u003ca name=\"hints\"\u003eAppendix A: Hints and Tips\u003c/a\u003e\u003c/h2\u003e\n \u003cblockquote\u003e\n\n \u003ch3\u003e\u003ca name=\"faq\"\u003eFAQ\u003c/a\u003e\u003c/h3\u003e\n \u003cblockquote\u003e\n\n \u003cp\u003e\n \u003cb\u003eQ:\u003c/b\u003e The \u003ccode\u003egenerated-configure.sh\u003c/code\u003e file looks horrible! \n How are you going to edit it?\n \u003cbr\u003e\n \u003cb\u003eA:\u003c/b\u003e The \u003ccode\u003egenerated-configure.sh\u003c/code\u003e file is generated (think\n \"compiled\") by the autoconf tools. The source code is\n in \u003ccode\u003econfigure.ac\u003c/code\u003e and various .m4 files in common/autoconf,\n which are much more readable.\n \u003c/p\u003e\n\n \u003cp\u003e\n \u003cb\u003eQ:\u003c/b\u003e \n Why is the \u003ccode\u003egenerated-configure.sh\u003c/code\u003e file checked in, \n if it is generated?\n \u003cbr\u003e\n \u003cb\u003eA:\u003c/b\u003e \n If it was not generated, every user would need to have the autoconf \n tools installed, and re-generate the \u003ccode\u003econfigure\u003c/code\u003e file\n as the first step. \n Our goal is to minimize the work needed to be done by the user \n to start building OpenJDK, and to minimize\n the number of external dependencies required.\n \u003c/p\u003e\n\n \u003cp\u003e\n \u003cb\u003eQ:\u003c/b\u003e\n Do you require a specific version of autoconf for regenerating\n \u003ccode\u003egenerated-configure.sh\u003c/code\u003e?\n \u003cbr\u003e\n \u003cb\u003eA:\u003c/b\u003e\n Yes, version 2.69 is required and should be easy\n enough to aquire on all supported operating\n systems. The reason for this is to avoid\n large spurious changes in \u003ccode\u003egenerated-configure.sh\u003c/code\u003e.\n \u003c/p\u003e\n\n \u003cp\u003e\n \u003cb\u003eQ:\u003c/b\u003e\n How do you regenerate \u003ccode\u003egenerated-configure.sh\u003c/code\u003e\n after making changes to the input files?\n \u003cbr\u003e\n \u003cb\u003eA:\u003c/b\u003e\n Regnerating \u003ccode\u003egenerated-configure.sh\u003c/code\u003e\n should always be done using the\n script \u003ccode\u003ecommon/autoconf/autogen.sh\u003c/code\u003e to\n ensure that the correct files get updated. This\n script should also be run after mercurial tries to\n merge \u003ccode\u003egenerated-configure.sh\u003c/code\u003e as a\n merge of the generated file is not guaranteed to\n be correct.\n \u003c/p\u003e\n\n \u003cp\u003e\n \u003cb\u003eQ:\u003c/b\u003e \n What are the files in \u003ccode\u003ecommon/makefiles/support/*\u003c/code\u003e for? \n They look like gibberish.\n \u003cbr\u003e\n \u003cb\u003eA:\u003c/b\u003e\n They are a somewhat ugly hack to compensate for command line length\n limitations on certain platforms (Windows, Solaris).\n Due to a combination of limitations in make and the shell, \n command lines containing too many files will not work properly. \n These\n helper files are part of an elaborate hack that will compress the\n command line in the makefile and then uncompress it safely. \n We're\n not proud of it, but it does fix the problem. \n If you have any better suggestions, we're all ears! :-)\n \u003c/p\u003e\n\n \u003cp\u003e\n \u003cb\u003eQ:\u003c/b\u003e \n I want to see the output of the commands that make runs, \n like in the old build. How do I do that?\n \u003cbr\u003e\n \u003cb\u003eA:\u003c/b\u003e \n You specify the \u003ccode\u003eLOG\u003c/code\u003e variable to make. There are\n several log levels:\n \u003c/p\u003e\n \u003cblockquote\u003e\n \u003cul\u003e\n \u003cli\u003e\n \u003cb\u003e\u003ccode\u003ewarn\u003c/code\u003e\u003c/b\u003e \u0026mdash; Default and very quiet.\n \u003c/li\u003e\n \u003cli\u003e\n \u003cb\u003e\u003ccode\u003einfo\u003c/code\u003e\u003c/b\u003e \u0026mdash; Shows more progress information\n than warn.\n \u003c/li\u003e\n \u003cli\u003e\n \u003cb\u003e\u003ccode\u003edebug\u003c/code\u003e\u003c/b\u003e \u0026mdash; Echos all command lines and\n prints all macro calls for compilation definitions.\n \u003c/li\u003e\n \u003cli\u003e\n \u003cb\u003e\u003ccode\u003etrace\u003c/code\u003e\u003c/b\u003e \u0026mdash; Echos all $(shell) command\n lines as well.\n \u003c/li\u003e\n \u003c/ul\u003e\n \u003c/blockquote\u003e\n\n \u003cp\u003e\n \u003cb\u003eQ:\u003c/b\u003e \n When do I have to re-run \u003ccode\u003econfigure\u003c/code\u003e?\n \u003cbr\u003e\n \u003cb\u003eA:\u003c/b\u003e \n Normally you will run \u003ccode\u003econfigure\u003c/code\u003e only once for creating a \n configuration. \n You need to re-run configuration only if you want to change any\n configuration options, \n or if you pull down changes to the \u003ccode\u003econfigure\u003c/code\u003e script.\n \u003c/p\u003e\n\n \u003cp\u003e\n \u003cb\u003eQ:\u003c/b\u003e \n I have added a new source file. Do I need to modify the makefiles?\n \u003cbr\u003e\n \u003cb\u003eA:\u003c/b\u003e \n Normally, no. If you want to create e.g. a new native\n library, \n you will need to modify the makefiles. But for normal file\n additions or removals, no changes are needed. There are certan\n exceptions for some native libraries where the source files are spread\n over many directories which also contain sources for other\n libraries. In these cases it was simply easier to create include lists\n rather than excludes.\n \u003c/p\u003e\n\n \u003cp\u003e\n \u003cb\u003eQ:\u003c/b\u003e\n When I run \u003ccode\u003econfigure --help\u003c/code\u003e, I see many strange options, \n like \u003ccode\u003e--dvidir\u003c/code\u003e. What is this?\n \u003cbr\u003e\n \u003cb\u003eA:\u003c/b\u003e \n Configure provides a slew of options by default, to all projects \n that use autoconf. Most of them are not used in OpenJDK,\n so you can safely ignore them. To list only OpenJDK specific features, \n use \u003ccode\u003econfigure --help=short\u003c/code\u003e instead.\n \u003c/p\u003e\n\n \u003cp\u003e\n \u003cb\u003eQ:\u003c/b\u003e \n \u003ccode\u003econfigure\u003c/code\u003e provides OpenJDK-specific features such as\n \u003ccode\u003e--with-builddeps-server\u003c/code\u003e that are not\n described in this document. What about those? \n \u003cbr\u003e\n \u003cb\u003eA:\u003c/b\u003e\n Try them out if you like! But be aware that most of these are \n experimental features. \n Many of them don't do anything at all at the moment; the option \n is just a placeholder. Others depend on\n pieces of code or infrastructure that is currently \n not ready for prime time.\n \u003c/p\u003e\n\n \u003cp\u003e\n \u003cb\u003eQ:\u003c/b\u003e \n How will you make sure you don't break anything?\n \u003cbr\u003e\n \u003cb\u003eA:\u003c/b\u003e \n We have a script that compares the result of the new build system\n with the result of the old. For most part, we aim for (and achieve)\n byte-by-byte identical output. There are however technical issues \n with e.g. native binaries, which might differ in a byte-by-byte \n comparison, even\n when building twice with the old build system. \n For these, we compare relevant aspects \n (e.g. the symbol table and file size). \n Note that we still don't have 100%\n equivalence, but we're close.\n \u003c/p\u003e\n\n \u003cp\u003e\n \u003cb\u003eQ:\u003c/b\u003e \n I noticed this thing X in the build that looks very broken by design. \n Why don't you fix it?\n \u003cbr\u003e\n \u003cb\u003eA:\u003c/b\u003e\n Our goal is to produce a build output that is as close as \n technically possible to the old build output. \n If things were weird in the old build,\n they will be weird in the new build. \n Often, things were weird before due to obscurity, \n but in the new build system the weird stuff comes up to the surface.\n The plan is to attack these things at a later stage, \n after the new build system is established.\n \u003c/p\u003e\n\n \u003cp\u003e\n \u003cb\u003eQ:\u003c/b\u003e \n The code in the new build system is not that well-structured.\n Will you fix this?\n \u003cbr\u003e\n \u003cb\u003eA:\u003c/b\u003e\n Yes! The new build system has grown bit by bit as we converted \n the old system. When all of the old build system is converted,\n we can take a step back and clean up the structure of the new build\n system. Some of this we plan to do before replacing the old build\n system and some will need to wait until after.\n \u003c/p\u003e\n\n \u003cp\u003e\n \u003cb\u003eQ:\u003c/b\u003e \n Is anything able to use the results of the new build's default make target?\n \u003cbr\u003e\n \u003cb\u003eA:\u003c/b\u003e \n Yes, this is the minimal (or roughly minimal) \n set of compiled output needed for a developer to actually \n execute the newly built JDK. The idea is that in an incremental \n development fashion, when doing a normal make, \n you should only spend time recompiling what's changed \n (making it purely incremental) and only do the work that's \n needed to actually run and test your code.\n The packaging stuff that is part of the \u003ccode\u003eimages\u003c/code\u003e\n target is not needed for a normal developer who wants to\n test his new code. Even if it's quite fast, it's still unnecessary. \n We're targeting sub-second incremental rebuilds! ;-) \n (Or, well, at least single-digit seconds...)\n \u003c/p\u003e\n\n \u003cp\u003e\n \u003cb\u003eQ:\u003c/b\u003e\n I usually set a specific environment variable when building, \n but I can't find the equivalent in the new build. \n What should I do?\n \u003cbr\u003e\n \u003cb\u003eA:\u003c/b\u003e\n It might very well be that we have neglected to add support for\n an option that was actually used from outside the build system.\n Email us and we will add support for it!\n \u003c/p\u003e\n\n \u003c/blockquote\u003e\n\n \u003ch3\u003e\u003ca name=\"performance\"\u003eBuild Performance Tips\u003c/a\u003e\u003c/h3\u003e\n \u003cblockquote\u003e\n\n \u003cp\u003eBuilding OpenJDK requires a lot of horsepower. \n Some of the build tools can be adjusted to utilize more or less\n of resources such as\n parallel threads and memory. \n The \u003ccode\u003econfigure\u003c/code\u003e script analyzes your system and selects reasonable \n values for such options based on your hardware.\n If you encounter resource problems, such as out of memory conditions, \n you can modify the detected values with:\u003c/p\u003e\n\n \u003cul\u003e\n \u003cli\u003e\n \u003cb\u003e\u003ccode\u003e--with-num-cores\u003c/code\u003e\u003c/b\u003e \n \u0026mdash; \n number of cores in the build system,\n e.g. \u003ccode\u003e--with-num-cores=8\u003c/code\u003e\n \u003c/li\u003e\n \u003cli\u003e\n \u003cb\u003e\u003ccode\u003e--with-memory-size\u003c/code\u003e\u003c/b\u003e \n \u0026mdash; memory (in MB) available in the build system,\n e.g. \u003ccode\u003e--with-memory-size=1024\u003c/code\u003e\n \u003c/li\u003e\n \u003c/ul\u003e\n\n \u003cp\u003eIt might also be necessary to specify the JVM arguments passed \n to the Bootstrap JDK, using e.g.\n \u003ccode\u003e--with-boot-jdk-jvmargs=\"-Xmx8G -enableassertions\"\u003c/code\u003e. \n Doing this will override the default JVM arguments \n passed to the Bootstrap JDK.\u003c/p\u003e\n\n\n \u003cp\u003eOne of the top goals of the new build system is to improve the\n build performance and decrease the time needed to build. This will\n soon also apply to the java compilation when the Smart Javac wrapper\n is making its way into jdk8. It can be tried in the build-infra\n repository already. You are likely to find that the new build system\n is faster than the old one even without this feature.\u003c/p\u003e\n\n \u003cp\u003eAt the end of a successful execution of \u003ccode\u003econfigure\u003c/code\u003e, \n you will get a performance summary, \n indicating how well the build will perform. Here you will\n also get performance hints. \n If you want to build fast, pay attention to those!\u003c/p\u003e\n\n \u003ch4\u003eBuilding with ccache\u003c/h4\u003e\n\n \u003cp\u003eA simple way to radically speed up compilation of native code\n (typically hotspot and native libraries in JDK) is to install\n ccache. This will cache and reuse prior compilation results, if the\n source code is unchanged. However, ccache versions prior to 3.1.4\n does not work correctly with the precompiled headers used in\n OpenJDK. So if your platform supports ccache at 3.1.4 or later, we\n highly recommend installing it. This is currently only supported on\n linux.\u003c/p\u003e \n\n \u003ch4\u003eBuilding on local disk\u003c/h4\u003e\n\n \u003cp\u003eIf you are using network shares, e.g. via NFS, for your source code, \n make sure the build directory is situated on local disk. \n The performance\n penalty is extremely high for building on a network share, \n close to unusable.\u003c/p\u003e\n\n \u003ch4\u003eBuilding only one JVM\u003c/h4\u003e\n\n \u003cp\u003eThe old build builds multiple JVMs on 32-bit systems (client and\n server; and on Windows kernel as well). In the new build we have\n changed this default to only build server when it's available. This\n improves build times for those not interested in multiple JVMs. To\n mimic the old behavior on platforms that support it, \n use \u003ccode\u003e--with-jvm-variants=client,server\u003c/code\u003e.\u003c/p\u003e\n\n \u003ch4\u003eSelecting the number of cores to build on\u003c/h4\u003e\n\n \u003cp\u003eBy default, \u003ccode\u003econfigure\u003c/code\u003e will analyze your machine and run the make\n process in parallel with as many threads as you have cores. This\n behavior can be overridden, either \"permanently\" (on a \u003ccode\u003econfigure\u003c/code\u003e\n basis) using \u003ccode\u003e--with-num-cores=N\u003c/code\u003e or for a single build\n only (on a make basis), using \u003ccode\u003emake JOBS=N\u003c/code\u003e.\u003c/p\u003e\n\n \u003cp\u003eIf you want to make a slower build just this time, to save some CPU\n power for other processes, you can run\n e.g. \u003ccode\u003emake JOBS=2\u003c/code\u003e. This will force the makefiles\n to only run 2 parallel processes, or even \u003ccode\u003emake JOBS=1\u003c/code\u003e\n which will disable parallelism.\u003c/p\u003e\n\n \u003cp\u003eIf you want to have it the other way round, namely having slow \n builds default and override with fast if you're\n impatient, you should call \u003ccode\u003econfigure\u003c/code\u003e with \n \u003ccode\u003e--with-num-cores=2\u003c/code\u003e, making 2 the default. \n If you want to run with more\n cores, run \u003ccode\u003emake JOBS=8\u003c/code\u003e\u003c/p\u003e\n\n \u003c/blockquote\u003e\n\n \u003ch3\u003e\u003ca name=\"troubleshooting\"\u003eTroubleshooting\u003c/a\u003e\u003c/h3\u003e\n \u003cblockquote\u003e\n\n \u003ch4\u003eSolving build problems\u003c/h4\u003e\n\n \u003cblockquote\u003e\n If the build fails (and it's not due to a compilation error in \n a source file you've changed), the first thing you should do\n is to re-run the build with more verbosity. \n Do this by adding \u003ccode\u003eLOG=debug\u003c/code\u003e to your make command line.\n \u003cbr\u003e\n The build log (with both stdout and stderr intermingled,\n basically the same as you see on your console) can be found as\n \u003ccode\u003ebuild.log\u003c/code\u003e in your build directory.\n \u003cbr\u003e\n You can ask for help on build problems with the new build system \n on either the\n \u003ca href=\"http://mail.openjdk.java.net/mailman/listinfo/build-dev\"\u003e\n build-dev\u003c/a\u003e\n or the\n \u003ca href=\"http://mail.openjdk.java.net/mailman/listinfo/build-infra-dev\"\u003e\n build-infra-dev\u003c/a\u003e\n mailing lists. Please include the relevant parts\n of the build log.\n \u003cbr\u003e\n A build can fail for any number of reasons. \n Most failures\n are a result of trying to build in an environment in which all the\n pre-build requirements have not been met. \n The first step in\n troubleshooting a build failure is to recheck that you have satisfied\n all the pre-build requirements for your platform.\n Scanning the \u003ccode\u003econfigure\u003c/code\u003e log is a good first step, making\n sure that what it found makes sense for your system.\n Look for strange error messages or any difficulties that\n \u003ccode\u003econfigure\u003c/code\u003e had in finding things.\n \u003cbr\u003e\n Some of the more common problems with builds are briefly\n described\n below, with suggestions for remedies.\n \u003cul\u003e\n \u003cli\u003e\n \u003cb\u003eCorrupted Bundles on Windows:\u003c/b\u003e\n \u003cblockquote\u003e\n Some virus scanning software has been known to \n corrupt the\n downloading of zip bundles.\n It may be necessary to disable the 'on access' or \n 'real time'\n virus scanning features to prevent this corruption.\n This type of \"real time\" virus scanning can also \n slow down the\n build process significantly.\n Temporarily disabling the feature, or excluding the build\n output directory may be necessary to get correct and\n faster builds.\n \u003c/blockquote\u003e\n \u003c/li\u003e\n \u003cli\u003e\n \u003cb\u003eSlow Builds:\u003c/b\u003e\n \u003cblockquote\u003e\n If your build machine seems to be overloaded from too many\n simultaneous C++ compiles, try setting the \n \u003ccode\u003eJOBS=1\u003c/code\u003e on the \u003ccode\u003emake\u003c/code\u003e command line.\n Then try increasing the count slowly to an acceptable\n level for your system. Also:\n \u003cblockquote\u003e\n Creating the javadocs can be very slow, \n if you are running\n javadoc, consider skipping that step.\n \u003cbr\u003e\n Faster CPUs, more RAM, and a faster DISK usually helps.\n The VM build tends to be CPU intensive \n (many C++ compiles),\n and the rest of the JDK will often be disk intensive.\n \u003cbr\u003e\n Faster compiles are possible using a tool called\n \u003ca href=\"http://ccache.samba.org/\" target=\"_blank\"\u003eccache\u003c/a\u003e.\n \u003c/blockquote\u003e\n \u003c/blockquote\u003e\n \u003c/li\u003e\n \u003cli\u003e\n \u003cb\u003eFile time issues:\u003c/b\u003e\n \u003cblockquote\u003e\n If you see warnings that refer to file time stamps, e.g.\n \u003cblockquote\u003e\n \u003ci\u003eWarning message:\u003c/i\u003e\u003ccode\u003e \n File `xxx' has modification time in\n the future.\u003c/code\u003e\n \u003cbr\u003e\n \u003ci\u003eWarning message:\u003c/i\u003e \u003ccode\u003e Clock skew detected. \n Your build may\n be incomplete.\u003c/code\u003e\n \u003c/blockquote\u003e\n These warnings can occur when the clock on the build \n machine is out of\n sync with the timestamps on the source files. \n Other errors, apparently\n unrelated but in fact caused by the clock skew, \n can occur along with\n the clock skew warnings. \n These secondary errors may tend to obscure the\n fact that the true root cause of the problem \n is an out-of-sync clock.\n \u003cp\u003e\n If you see these warnings, reset the clock on the\n build\n machine, run \"\u003ccode\u003e\u003ci\u003egmake\u003c/i\u003e clobber\u003c/code\u003e\" \n or delete the directory\n containing the build output, and restart the \n build from the beginning.\n \u003c/blockquote\u003e\n \u003c/li\u003e\n \u003cli\u003e\n \u003cb\u003eError message: \n \u003ccode\u003eTrouble writing out table to disk\u003c/code\u003e\u003c/b\u003e\n \u003cblockquote\u003e\n Increase the amount of swap space on your build machine.\n This could be caused by overloading the system and\n it may be necessary to use:\n \u003cblockquote\u003e\n \u003ccode\u003emake JOBS=1\u003c/code\u003e\n \u003c/blockquote\u003e\n to reduce the load on the system.\n \u003c/blockquote\u003e\n \u003c/li\u003e\n \u003cli\u003e\n \u003cb\u003eError Message: \n \u003ccode\u003elibstdc++ not found:\u003c/code\u003e\u003c/b\u003e\n \u003cblockquote\u003e\n This is caused by a missing libstdc++.a library.\n This is installed as part of a specific package\n (e.g. libstdc++.so.devel.386).\n By default some 64-bit Linux versions (e.g. Fedora)\n only install the 64-bit version of the libstdc++ package.\n Various parts of the JDK build require a static\n link of the C++ runtime libraries to allow for maximum\n portability of the built images.\n \u003c/blockquote\u003e\n \u003c/li\u003e\n \u003cli\u003e\n \u003cb\u003eLinux Error Message:\n \u003ccode\u003ecannot restore segment prot after reloc\u003c/code\u003e\u003c/b\u003e\n \u003cblockquote\u003e\n This is probably an issue with SELinux (See\n \u003ca href=\"http://en.wikipedia.org/wiki/SELinux\" target=\"_blank\"\u003e\n http://en.wikipedia.org/wiki/SELinux\u003c/a\u003e).\n Parts of the VM is built without the \u003ccode\u003e-fPIC\u003c/code\u003e for\n performance reasons.\n \u003cp\u003e\n To completely disable SELinux:\n \u003col\u003e\n \u003cli\u003e\u003ccode\u003e$ su root\u003c/code\u003e\u003c/li\u003e\n \u003cli\u003e\u003ccode\u003e# system-config-securitylevel\u003c/code\u003e\u003c/li\u003e\n \u003cli\u003e\u003ccode\u003eIn the window that appears, select the SELinux tab\u003c/code\u003e\u003c/li\u003e\n \u003cli\u003e\u003ccode\u003eDisable SELinux\u003c/code\u003e\u003c/li\u003e\n \u003c/ol\u003e\n \u003cp\u003e\n Alternatively, instead of completely disabling it you could\n disable just this one check.\n \u003col\u003e\n \u003cli\u003eSelect System-\u003eAdministration-\u003eSELinux Management\u003c/li\u003e\n \u003cli\u003eIn the SELinux Management Tool which appears,\n select \"Boolean\" from the menu on the left\u003c/li\u003e\n \u003cli\u003eExpand the \"Memory Protection\" group\u003c/li\u003e\n \u003cli\u003eCheck the first item, labeled\n \"Allow all unconfined executables to use \n libraries requiring text relocation ...\"\u003c/li\u003e\n \u003c/ol\u003e\n \u003c/blockquote\u003e\n \u003c/li\u003e\n \u003cli\u003e\n \u003cb\u003eWindows Error Messages:\u003c/b\u003e\n \u003cbr\u003e\n \u003ccode\u003e*** fatal error - couldn't allocate heap, ... \u003c/code\u003e\n \u003cbr\u003e\n \u003ccode\u003erm fails with \"Directory not empty\"\u003c/code\u003e\n \u003cbr\u003e\n \u003ccode\u003eunzip fails with \"cannot create ... Permission denied\"\u003c/code\u003e\n \u003cbr\u003e\n \u003ccode\u003eunzip fails with \"cannot create ... Error 50\"\u003c/code\u003e\n \u003cbr\u003e\n \u003cblockquote\u003e\n The CYGWIN software can conflict with other non-CYGWIN\n software. See the CYGWIN FAQ section on\n \u003ca href=\"http://cygwin.com/faq/faq.using.html#faq.using.bloda\" target=\"_blank\"\u003e\n BLODA (applications that interfere with CYGWIN)\u003c/a\u003e.\n \u003c/blockquote\u003e\n \u003c/li\u003e\n \u003cli\u003e\n \u003cb\u003eWindows Error Message: \u003ccode\u003espawn failed\u003c/code\u003e\u003c/b\u003e\n \u003cblockquote\u003e\n Try rebooting the system, or there could be some kind of\n issue with the disk or disk partition being used.\n Sometimes it comes with a \"Permission Denied\" message.\n \u003c/blockquote\u003e\n \u003c/li\u003e\n \u003c/ul\u003e\n \u003c/blockquote\u003e\n\n \u003c/blockquote\u003e \u003c!-- Troubleshooting --\u003e\n\n \u003c/blockquote\u003e \u003c!-- Appendix A --\u003e\n\n \u003c!-- ====================================================== --\u003e\n \u003chr\u003e\n \u003ch2\u003e\u003ca name=\"gmake\"\u003eAppendix B: GNU make\u003c/a\u003e\u003c/h2\u003e\n \u003cblockquote\u003e\n\n The Makefiles in the OpenJDK are only valid when used with the \n GNU version of the utility command \u003ccode\u003emake\u003c/code\u003e\n (usually called \u003ccode\u003egmake\u003c/code\u003e on Solaris).\n A few notes about using GNU make:\n \u003cul\u003e\n \u003cli\u003e\n You need GNU make version 3.81 or newer.\n If the GNU make utility on your systems is not\n 3.81 or newer,\n see \u003ca href=\"#buildgmake\"\u003e\"Building GNU make\"\u003c/a\u003e.\n \u003c/li\u003e\n \u003cli\u003e\n Place the location of the GNU make binary in the\n \u003ccode\u003ePATH\u003c/code\u003e. \n \u003c/li\u003e\n \u003cli\u003e\n \u003cstrong\u003eSolaris:\u003c/strong\u003e\n Do NOT use \u003ccode\u003e/usr/bin/make\u003c/code\u003e on Solaris.\n If your Solaris system has the software\n from the Solaris Developer Companion CD installed, \n you should try and use \u003ccode\u003egmake\u003c/code\u003e\n which will be located in either the\n \u003ccode\u003e/usr/bin\u003c/code\u003e, \u003ccode\u003e/opt/sfw/bin\u003c/code\u003e or \n \u003ccode\u003e/usr/sfw/bin\u003c/code\u003e directory.\n \u003c/li\u003e\n \u003cli\u003e\n \u003cstrong\u003eWindows:\u003c/strong\u003e\n Make sure you start your build inside a bash shell.\n \u003c/li\u003e\n \u003cli\u003e\n \u003cstrong\u003eMac OS X:\u003c/strong\u003e\n The XCode \"command line tools\" must be installed on your Mac.\n \u003c/li\u003e\n \u003c/ul\u003e\n \u003cp\u003e\n Information on GNU make, and access to ftp download sites, are\n available on the\n \u003ca href=\"http://www.gnu.org/software/make/make.html\" target=\"_blank\"\u003e\n GNU make web site\n \u003c/a\u003e.\n The latest source to GNU make is available at\n \u003ca href=\"http://ftp.gnu.org/pub/gnu/make/\" target=\"_blank\"\u003e\n ftp.gnu.org/pub/gnu/make/\u003c/a\u003e.\n \u003c/p\u003e\n\n \u003ch3\u003e\u003ca name=\"buildgmake\"\u003eBuilding GNU make\u003c/a\u003e\u003c/h3\u003e\n \u003cblockquote\u003e\n First step is to get the GNU make 3.81 or newer source from\n \u003ca href=\"http://ftp.gnu.org/pub/gnu/make/\" target=\"_blank\"\u003e\n ftp.gnu.org/pub/gnu/make/\u003c/a\u003e.\n Building is a little different depending on the OS but is\n basically done with:\n \u003cblockquote\u003e\n \u003ccode\u003ebash ./configure\u003c/code\u003e\n \u003cbr\u003e\n \u003ccode\u003emake\u003c/code\u003e\n \u003c/blockquote\u003e\n \u003c/blockquote\u003e\n\n \u003c/blockquote\u003e \u003c!-- Appendix B --\u003e\n\n \u003c!-- ====================================================== --\u003e\n \u003chr\u003e\n \u003ch2\u003e\u003ca name=\"buildenvironments\"\u003eAppendix C: Build Environments\u003c/a\u003e\u003c/h2\u003e\n \u003cblockquote\u003e\n\n \u003ch3\u003e\u003ca name=\"MBE\"\u003eMinimum Build Environments\u003c/a\u003e\u003c/h3\u003e\n \u003cblockquote\u003e\n This file often describes specific requirements for what we \n call the\n \"minimum build environments\" (MBE) for this \n specific release of the JDK.\n What is listed below is what the Oracle Release\n Engineering Team will use to build the Oracle JDK product.\n Building with the MBE will hopefully generate the most compatible\n bits that install on, and run correctly on, the most variations\n of the same base OS and hardware architecture.\n In some cases, these represent what is often called the\n least common denominator, but each Operating System has different\n aspects to it.\n \u003cp\u003e\n In all cases, the Bootstrap JDK version minimum is critical,\n we cannot guarantee builds will work with older Bootstrap JDK's.\n Also in all cases, more RAM and more processors is better,\n the minimums listed below are simply recommendations.\n \u003cp\u003e\n With Solaris and Mac OS X, the version listed below is the\n oldest release we can guarantee builds and works, and the\n specific version of the compilers used could be critical.\n \u003cp\u003e\n With Windows the critical aspect is the Visual Studio compiler\n used, which due to it's runtime, generally dictates what Windows\n systems can do the builds and where the resulting bits can\n be used.\u003cbr\u003e\n \u003cb\u003eNOTE: We expect a change here off these older Windows OS releases\n and to a 'less older' one, probably Windows 2008R2 X64.\u003c/b\u003e\n \u003cp\u003e\n With Linux, it was just a matter of picking a\n stable distribution that is a good representative for Linux\n in general.\u003cbr\u003e\n \u003cb\u003eNOTE: We expect a change here from Fedora 9 to something else,\n but it has not been completely determined yet, possibly\n Ubuntu 12.04 X64, unbiased community feedback would be welcome on\n what a good choice would be here.\u003c/b\u003e\n \u003cp\u003e\n It is understood that most developers will NOT be using these \n specific versions, and in fact creating these specific versions\n may be difficult due to the age of some of this software.\n It is expected that developers are more often using the more\n recent releases and distributions of these operating systems.\n \u003cp\u003e\n Compilation problems with newer or different C/C++ compilers is a\n common problem.\n Similarly, compilation problems related to changes to the\n \u003ccode\u003e/usr/include\u003c/code\u003e or system header files is also a\n common problem with older, newer, or unreleased OS versions.\n Please report these types of problems as bugs so that they\n can be dealt with accordingly.\n \u003c/p\u003e\n \u003ctable border=\"1\"\u003e\n \u003cthead\u003e\n \u003ctr\u003e\n \u003cth\u003eBase OS and Architecture\u003c/th\u003e\n \u003cth\u003eOS\u003c/th\u003e\n \u003cth\u003eC/C++ Compiler\u003c/th\u003e\n \u003cth\u003eBootstrap JDK\u003c/th\u003e\n \u003cth\u003eProcessors\u003c/th\u003e\n \u003cth\u003eRAM Minimum\u003c/th\u003e\n \u003cth\u003eDISK Needs\u003c/th\u003e\n \u003c/tr\u003e\n \u003c/thead\u003e\n \u003ctbody\u003e\n \u003ctr\u003e\n \u003ctd\u003eLinux X86 (32-bit) and X64 (64-bit)\u003c/td\u003e\n \u003ctd\u003eFedora 9\u003c/td\u003e\n \u003ctd\u003egcc 4.3 \u003c/td\u003e\n \u003ctd\u003eJDK 7u7\u003c/td\u003e\n \u003ctd\u003e2 or more\u003c/td\u003e\n \u003ctd\u003e1 GB\u003c/td\u003e\n \u003ctd\u003e6 GB\u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003eSolaris SPARC (32-bit) and SPARCV9 (64-bit)\u003c/td\u003e\n \u003ctd\u003eSolaris 10 Update 6\u003c/td\u003e\n \u003ctd\u003eStudio 12 Update 1 + patches\u003c/td\u003e\n \u003ctd\u003eJDK 7u7\u003c/td\u003e\n \u003ctd\u003e4 or more\u003c/td\u003e\n \u003ctd\u003e4 GB\u003c/td\u003e\n \u003ctd\u003e8 GB\u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003eSolaris X86 (32-bit) and X64 (64-bit)\u003c/td\u003e\n \u003ctd\u003eSolaris 10 Update 6\u003c/td\u003e\n \u003ctd\u003eStudio 12 Update 1 + patches\u003c/td\u003e\n \u003ctd\u003eJDK 7u7\u003c/td\u003e\n \u003ctd\u003e4 or more\u003c/td\u003e\n \u003ctd\u003e4 GB\u003c/td\u003e\n \u003ctd\u003e8 GB\u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003eWindows X86 (32-bit)\u003c/td\u003e\n \u003ctd\u003eWindows XP\u003c/td\u003e\n \u003ctd\u003eMicrosoft Vi","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fitsaky%2Fopenjdk-8-android","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fitsaky%2Fopenjdk-8-android","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fitsaky%2Fopenjdk-8-android/lists"}