On Aug 24, 2009, at 11:53 PM, Kelly O'Hair wrote:
The sanity check on the BOOTDIR and IMPORT jdk too are not very good.
They don't even verify it is 1.6.0 much less checking for a javac.
I'm surprised these are not full jdk images.
Where did the OS install come from? With the machine?
It's a new opensolaris 2009.06 installed by lab guys here.
In fact, you can see this "JDK" installation from a LiveCD of
opensolaris. Just like a normal JDK, there are bin/ and jre/ (no lib/)
under /usr/jdk/instances/jdk1.6.0. But the bin/ directory only
includes those files.
I'll try adding developer packages.
Thanks
Max
It used to be that there was Solaris end-user installs and developer
installs, it was always important to get a full developer install of
Solaris, including all the 'companion cd' bits, which I think they
renamed.
I'd be tempted to install a fresh OpenSolaris image on this
machine, and go 'open' ;^)
-kto
David Holmes - Sun Microsystems wrote:
I don't know what installed that "JDK" on your system so I don't
know where the problem might lie - ie you may have a JRE
impersonating a JDK.
But the sanity check might need strengthening too.
David
Weijun Wang said the following on 08/24/09 16:38:
But the path name is /usr/jdk/instances/jdk1.6.0/bin/. I guess the
sanity check should choose an alternative path, or, just report an
error.
Max
David Holmes - Sun Microsystems wrote:
Max,
That looks more like a JRE install than a JDK install.
David
Weijun Wang said the following on 08/24/09 16:06:
I'm trying to build openjdk on a new ultra-24. The sanity check
shows
BOOTDIR = /usr/jdk/instances/jdk1.6.0
but fails at the very beginning:
BUILD FAILED
/net/bounty.prc/j2se-jsn/max/work/myjdk/langtools/make/build.xml:
600:
Error running /usr/jdk/instances/jdk1.6.0/bin/javac compiler
since there's no javac there:
$ ls /usr/jdk/instances/jdk1.6.0/bin/
ControlPanel jcontrol pack200 rmiregistry unpack200
java keytool policytool servertool
javaws orbd rmid tnameserv
Is this normal?
Thanks
Max
