jean-frederic clere <[EMAIL PROTECTED]> wrote:

> Pier Fumagalli wrote:
>> "jean-frederic clere" <[EMAIL PROTECTED]> wrote:
>> 
>> 
>>> [EMAIL PROTECTED] wrote:
>>> 
>>>> Need help and feedback...
>>>> 
>>>> As you know, the new Coyote supports both HTTP/1.1 and JK. And the new
>>>> JK supports some new communication channels and APR functions that need
>>>> JNI.
>>>> 
>>>> The 'idealistic' goal was to do that transparently - using System.load(),
>>>> so that the user will not have to set LD_LIBRARY_PATH. We would set
>>>> aprHome in jk2.properties - and that's it.
>>> 
>>> Something like ld.config or crle also helps.
>>> 
>>> I remember that the JVM does not make the symbols of a library available to
>>> other libraries.
>>> For example my libapr.so needed something in libcrypt.so but
>>> System.load("crypt") before System.load("apr") did not help.
>> 
>> 
>> LD_PRELOAD=/usr/lib/libcrypt.so could make the trick (under solaris... Under
>> Linux I really don't know if their ld supports it).
>> 
>> The problem is that System.load calls dlopen() with the RTLD_LOCAL
>> parameter, so that usually screws up most things.
>> 
>> Conservative approach is to reverse the library loading process: link a
>> binary to your libapr (and consequently to libcrypt), and then use
>> JNI_CreateJavaVM to create the VM...
> 
> Or calling a native dlopen(RTLD_GLOBAL) instead System.load()?

Then it won't work... BTW, I hope you guys are not trying to load APR from
the VM, right? Because if so, I _really_ want to see how you can do it on
Mach-O kernel based Oses :)

    Pier


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to