The vmhome variable in the ebuild is set like the following: local vmhome="/usr/$(get_libdir)/jvm/${vm}" while in fact JDKs are installed in /usr/lib/jvm (there's no /usr/$(get_libdir)/jvm). So, either JDK install location should change, or the ebuild be corrected to use: local vmhome="/usr/lib/jvm/${vm}"
You're right, but usually this is no problem as usr/lib is symlink to /usr/$(get_libdir) : lrwxrwxrwx 1 root root 5 Aug 6 2009 /usr/lib -> lib64 Under what conditions did you encounter this to be a problem?
(In reply to comment #1) > You're right, but usually this is no problem as usr/lib is symlink to > /usr/$(get_libdir) : > > lrwxrwxrwx 1 root root 5 Aug 6 2009 /usr/lib -> lib64 > > Under what conditions did you encounter this to be a problem? Simply: under the opposite conditions, where lib and lib64 are separate dirs. This matches the other multilib profile as well, I think.
Fixed, thanks.
