[Bug 2764] Not able to find JDK during ./configure on ppc64el

[bugzilla-daemon at icedtea.classpath.org]

http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=2764

--- Comment #7 from Tiago Stürmer Daitx <tdaitx at gmail.com> ---
(In reply to Andrew John Hughes from comment #6)
Thanks for the quick reply.

> Other platforms use /usr/lib and /usr/lib64 to support this and
> we already detect both:
> 
> /usr/lib/jvm/icedtea-7
> /usr/lib/jvm/icedtea7
> /usr/lib/jvm/java-1.7.0-openjdk
> /usr/lib/jvm/java-1.7.0-openjdk.x86_64
> /usr/lib64/jvm/java-1.7.0-openjdk
> 
> We could try checking for /usr/lib/jvm/java-7-openjdk-${host_cpu} but it
> doesn't help that Debian is using a non-standard naming for this (amd64
> instead of x86_64, ppc64el instead of ppc64le)

Yes, it is non-standard - meaning it relies on debian's dpkg-architecture
binary output.

> This is no good. We need specific versions of OpenJDK, not whatever random
> JVM the user has selected. 

The /usr/lib/jvm/default-java directory is not set or defined by the user, the
package maintainer does that.

> Besides, we already have
> /etc/alternatives/java_sdk_openjdk as a last resort. Don't tell me, Debian
> doesn't provide this either?

No, it does not. There is no entry in alternatives to provide anything similar
to that - the closest option is the default-java directory above, but the user
can't change it.

I will check what can be done. For now it only affects users building upstream
icedtea in a debian environment and - fortunately - has an easy workaround. If
/usr/lib/jvm/default-java is not an acceptable solution I recommend opening a
bug in debian for further discussion.

Thanks!

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/distro-pkg-dev/attachments/20151216/538e87cc/attachment-0001.html>