-
Bug
-
Resolution: Fixed
-
P2
-
OpenJDK6
-
b17
-
x86
-
linux_2.6
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2181846 | 7 | Dalibor Topic | P3 | Resolved | Fixed | b72 |
The 6open build README's need to be brought up-to-date with what's there
Observations:
control/make/README differs from jdk/make/README
control/make/README does not say to get a JDK7 for ALT_JDK_IMPORT_PATH
jdk/make/README says
3. Either download and install the latest JDK7 from
http://download.java.net/openjdk/jdk7/, or build your own complete
OpenJDK7 by using the top level Makefile in the OpenJDK Mercurial forest.
Set the environment variable ALT_JDK_IMPORT_PATH to the location of
this latest JDK7 or OpenJDK7 build.
This needs to be clarified to make it clear a JDK7 binary build is sufficient.
We aren't delivering OpenJDK binary builds. The correct URL
is actually http://download.java.net/jdk7/binaries/ or else they
should start from the jdk7.dev.java.net site to find the binaries.
jdk/make/README-builds.html notes:
"Specific Build Environments" .. under Ubuntu there could be a section describing build requirements for 7.10. I found the 7.04 requirements to be mostly useful. However xlibs-dev no longer exists as a package. One of the other packages did bring in a bunch of X packages. However libxtst-dev and libxi-dev did not get pulled in causing build failures. And the build requirements might change again for 8.04.
Under Motif headers for Linux it says "If this package installs the files into /usr/include/Xm, no further action should be needed". On Ubuntu installing libmotif3-dev does leave include files in that directory plus libXm.a in /usr/lib. But 'make sanity' gave these complaints:
ERROR: You do not have access to a valid Motif 2.1 library.
Please check your access to
/NOT-SET/devtools/linux/motif-i586/lib/libXm.a
and/or check your value of ALT_MOTIF_DIR.
ERROR: You do not have access to valid Motif 2.1 header files.
Please check your access to (for example)
/NOT-SET/devtools/linux/motif-i586/include/Xm/AtomMgr.h
and/or check your value of ALT_MOTIF_DIR.
Rather than work that out (maybe I could set ALT_MOTIF_DIR=/usr) I found setting OPENJDK=true bypassed this check.
The OPENJDK variable is not documented.
Neither ant nor findbugs are mentioned in README-builds.html. 'make sanity' gave these messages:
/bin/sh: /NOT-SET/devtools/share/ant/latest/bin/ant: not found
/bin/sh: /NOT-SET/devtools/share/findbugs/latest/bin/findbugs: not found
For 'ant' Ubuntu has a package which installs ant, and it looks like ANT_HOME could be set to /usr/share/ant. I didn't check that as I already had an ant distribution unpacked elsewhere. The other variable to document is FINDBUGS_HOME.
The section starting 'Certificate Authority File (cacert)' .. sounds like OpenJDK will be including an empty CACERT file. Sounds like an empty file is not a problem.
Observations:
control/make/README differs from jdk/make/README
control/make/README does not say to get a JDK7 for ALT_JDK_IMPORT_PATH
jdk/make/README says
3. Either download and install the latest JDK7 from
http://download.java.net/openjdk/jdk7/, or build your own complete
OpenJDK7 by using the top level Makefile in the OpenJDK Mercurial forest.
Set the environment variable ALT_JDK_IMPORT_PATH to the location of
this latest JDK7 or OpenJDK7 build.
This needs to be clarified to make it clear a JDK7 binary build is sufficient.
We aren't delivering OpenJDK binary builds. The correct URL
is actually http://download.java.net/jdk7/binaries/ or else they
should start from the jdk7.dev.java.net site to find the binaries.
jdk/make/README-builds.html notes:
"Specific Build Environments" .. under Ubuntu there could be a section describing build requirements for 7.10. I found the 7.04 requirements to be mostly useful. However xlibs-dev no longer exists as a package. One of the other packages did bring in a bunch of X packages. However libxtst-dev and libxi-dev did not get pulled in causing build failures. And the build requirements might change again for 8.04.
Under Motif headers for Linux it says "If this package installs the files into /usr/include/Xm, no further action should be needed". On Ubuntu installing libmotif3-dev does leave include files in that directory plus libXm.a in /usr/lib. But 'make sanity' gave these complaints:
ERROR: You do not have access to a valid Motif 2.1 library.
Please check your access to
/NOT-SET/devtools/linux/motif-i586/lib/libXm.a
and/or check your value of ALT_MOTIF_DIR.
ERROR: You do not have access to valid Motif 2.1 header files.
Please check your access to (for example)
/NOT-SET/devtools/linux/motif-i586/include/Xm/AtomMgr.h
and/or check your value of ALT_MOTIF_DIR.
Rather than work that out (maybe I could set ALT_MOTIF_DIR=/usr) I found setting OPENJDK=true bypassed this check.
The OPENJDK variable is not documented.
Neither ant nor findbugs are mentioned in README-builds.html. 'make sanity' gave these messages:
/bin/sh: /NOT-SET/devtools/share/ant/latest/bin/ant: not found
/bin/sh: /NOT-SET/devtools/share/findbugs/latest/bin/findbugs: not found
For 'ant' Ubuntu has a package which installs ant, and it looks like ANT_HOME could be set to /usr/share/ant. I didn't check that as I already had an ant distribution unpacked elsewhere. The other variable to document is FINDBUGS_HOME.
The section starting 'Certificate Authority File (cacert)' .. sounds like OpenJDK will be including an empty CACERT file. Sounds like an empty file is not a problem.
- backported by
-
JDK-2181846 6-open: Bring build readme's up-to-date
- Resolved
- relates to
-
JDK-6662830 OpenJDK build testing results
- Resolved
-
JDK-6667532 Update OpenJDK 6 make/README
- Resolved
-
JDK-6872735 Further update build readme for new platforms
- Resolved