On 1/08/2013 9:49 PM, matchew wrote:
Thanks. How about build number. Setting variable BUILD_NUMBER does to have any effect - b00 is taken by default.
JDK_BUILD_NUMBER David
Thanks in advance -- Mateusz 2013/7/31 David Holmes <[email protected] <mailto:[email protected]>> On 31/07/2013 6:46 PM, matchew wrote: Hey All, I try to build above version. Since i want to provide custom cacert file as well as java compiler I set this env variables (that is how it worked for 6 & 7): export ALT_BOOTDIR=[JAVA_COMPILER___DIR] export ALT_CACERTS_FILE=[CUSTOM___CACERTS_FILE] Configure script passes and proper java compiler is taken (i have specified java7 / default on my box is java6), but got this warning anyway: WARNING: You have old-style ALT_ environment variables set. These are not respected, and will be ignored. It is recommended that you clean your environment. The following variables are set: ALT_BOOTDIR=/usr/lib/jvm/java-__7-openjdk-amd64 ALT_CACERTS_FILE=/etc/ssl/__certs/java/cacerts sh configure --help shows: --with-cacerts-file specify alternative cacerts file --with-boot-jdk path to Boot JDK (used to bootstrap build) [probed] Cheers, David ------ WARNING: You have the following ALT_ variables set: ALT_CACERTS_FILE=/etc/ssl/__certs/java/cacerts ALT_BOOTDIR=/usr/lib/jvm/java-__7-openjdk-amd64 ALT_ variables are deprecated and will be ignored. Please clean your environment. If these variables are deprecated and ignored how is it possible that java-7 was used for the compilation instead of default one? Anyway to build process continues and will check if cacert file was included. If not, what is the alternative way to provide it? Best Regards -- Mateusz
