Due to the way teapop's configure script checks for java, it will always fail on non-x86 arches. In looking for libjvm.so, it tests for the presence of the file in semi-hardcoded paths with i386 in them (i.e. $java/jre/lib/i386/server/libjvm.so) Right now I'm seeing two ways to handle this (but obviosuly it is up to you folks); 1) Disable java for non-x86 until upstream gets it's testing paths fixed 2) Add in additional checks for where libjvm.so would live for other arches
Anyone alive over in net-mail to comment on this?
I'd say let arches supply their java paths and we can then alter the configure script to include those. Anyone, objections?
commodore64 opt # slocate libjvm.so /opt/blackdown-jdk-1.4.2.01/jre/lib/amd64/server/libjvm.so I think if you substitute i386 for amd64 you should be good for amd64. Blackdown is the only currenly unmasked jre/jdk on amd64.
On SPARC, our libjvm is at either; /opt/blackdown-jdk-1.4.1/jre/lib/sparc/server/libjvm.so /opt/blackdown-jdk-1.4.1/jre/lib/sparc/client/libjvm.so or /opt/blackdown-jre-1.4.1/jre/lib/sparc/server/libjvm.so /opt/blackdown-jre-1.4.1/jre/lib/sparc/client/libjvm.so depending on whether the jre or jdk is installed.
As in 2006.0 SPARC no longer has java support, removing CC
Please reopen if this is still relevant.