On Fri, May 23, 2008 at 8:58 AM, Andrew Haley <aph(a)redhat.com> wrote:
Colin Walters wrote:
> On Fri, May 23, 2008 at 5:13 AM, Andrew Haley <aph(a)redhat.com> wrote:
>> Interesting. What multilib-awareness do you think we need? It's not
>> immediately clear to me where the beinefit would be.
>
> Code calling System.loadLibrary (i.e. most software out there that
> wants to dlopen) would work.
Well yes, obviously, but in what way would multilib-awareness help?
Even if you have a mixture of 32-bit and 64-bit VMs in the same system,
the VMs themselves wouldn't need to be multilib-aware.
I didn't write that section of the Java guidelines, so perhaps I'm
misinterpreting it. But I read "...modifying IcedTea to look for JNI
shared objects in %{_libdir}/jni" as "multilib-aware". But maybe the
operative change is the /jni and not the %{libdir}, so the
IcedTea/OpenJDK change is really to be "JPackage layout aware"?