Colin Walters wrote:
> On Fri, May 23, 2008 at 8:58 AM, Andrew Haley <aph@xxxxxxxxxx> wrote:
>> Colin Walters wrote:
>>> On Fri, May 23, 2008 at 5:13 AM, Andrew Haley <aph@xxxxxxxxxx> 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"?
That sounds much more likely. OpenJDK already looks in the correct libdir,
and adding "%{_libdir}/jni" would be a simple change.
The code that sets the path is here in java_md.c:
sprintf(new_runpath, "LD_LIBRARY_PATH="
"%s:"
"%s/lib/%s:"
"%s/../lib/%s",
jvmpath,
#ifdef DUAL_MODE
jrepath, ((wanted==64)?BIG_ARCH:SMALL_ARCH),
jrepath, ((wanted==64)?BIG_ARCH:SMALL_ARCH)
#else
jrepath, arch,
jrepath, arch
#endif
);
Andrew.
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
