On 01/02/2011 06:28 PM, David Herron wrote:
yes..but..
Setting JAVA_HOME and export PATH=${JAVA_HOME}/bin:${PATH} is an excess
step to installing software implemented in Java that is not normally
required for other software.
On a Linux system, to run a Python program (for example), are you
Kelly O'Hair wrote:
Need reviewer: OpenJDK7 2010 copyright year changes
Any sources changed in 2010 need to have their copyright year adjusted.
I suspect you might have to run this again once the changes from all the
group forests are pushed to master. That is, there might be a few files
The jdk install image can be located anywhere, but cannot be split up.
All the executables and shared libraries have appropriate RUNPATH/
RPATH entries using the $ORIGIN feature
so that at runtime, it locates itself and locates all other shared
libraries from that location.
It can be built
On Jan 3, 2011, at 7:17 AM, Alan Bateman wrote:
Kelly O'Hair wrote:
Need reviewer: OpenJDK7 2010 copyright year changes
Any sources changed in 2010 need to have their copyright year
adjusted.
I suspect you might have to run this again once the changes from all
the group forests are
On Jan 2, 2011, at 6:09 PM, Lussier, Denis wrote:
The differentiation you describe below for /opt and /usr/local also pretty
well jibes with my understanding.
I think that a local build of OpenJDK6 would reasonably be copied to
/usr/local/openjdk6 for usage. Perhaps I'm a bit old
There were some recent changes to make/linux/makefiles/launcher.make,
so my patch no longer applies. Here is an updated patch.
I've verified that the patch is still needed (on Fedora 14 with
SELinux enabled), and that it is complete, in the sense that
top-level make clean make completes
Need reviewer: Misc fixes related to binary file checks
This started out as fixing a rebase bug but we also needed to verify
that our libraries were
built properly, so the binary_file_verification define was created to
do this.
The checks are not nailed down yet, but I need to get the calls
