tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henri Gomez <hgo...@apache.org>
Subject Re: [ANNOUNCEMENT] JK2-2.0.2 released
Date Thu, 28 Nov 2002 15:33:46 GMT
jean-frederic clere wrote:
> Henri Gomez wrote:
> 
>>> Very weird.
>>>
>>> Send me the complete output of make.
>>
>>
>>
>> here it is :
>>
>> httpd2/lib -lcrypt -lapr-0 -lpcre -lpcreposix 
>> ../../../build/jk2/apache2/jk_jni_aprImpl.lo 
>> ../../../build/jk2/apache2/jk_channel_apr_socket.lo 
>> ../../../build/jk2/apache2/jk_channel.lo 
>> ../../../build/jk2/apache2/jk_channel_jni.lo 
>> ../../../build/jk2/apache2/jk_channel_socket.lo 
>> ../../../build/jk2/apache2/jk_channel_un.lo 
>> ../../../build/jk2/apache2/jk_config.lo 
>> ../../../build/jk2/apache2/jk_config_file.lo 
>> ../../../build/jk2/apache2/jk_endpoint.lo 
>> ../../../build/jk2/apache2/jk_env.lo 
>> ../../../build/jk2/apache2/jk_handler_logon.lo 
>> ../../../build/jk2/apache2/jk_handler_response.lo 
>> ../../../build/jk2/apache2/jk_logger_file.lo 
>> ../../../build/jk2/apache2/jk_logger_win32.lo 
>> ../../../build/jk2/apache2/jk_map.lo 
>> ../../../build/jk2/apache2/jk_md5.lo 
>> ../../../build/jk2/apache2/jk_msg_ajp.lo 
>> ../../../build/jk2/apache2/jk_mutex.lo 
>> ../../../build/jk2/apache2/jk_mutex_proc.lo 
>> ../../../build/jk2/apache2/jk_mutex_thread.lo 
>> ../../../build/jk2/apache2/jk_nwmain.lo 
>> ../../../build/jk2/apache2/jk_objCache.lo 
>> ../../../build/jk2/apache2/jk_pool_apr.lo 
>> ../../../build/jk2/apache2/jk_pool.lo 
>> ../../../build/jk2/apache2/jk_registry.lo 
>> ../../../build/jk2/apache2/jk_requtil.lo 
>> ../../../build/jk2/apache2/jk_shm.lo 
>> ../../../build/jk2/apache2/jk_signal.lo 
>> ../../../build/jk2/apache2/jk_uriEnv.lo 
>> ../../../build/jk2/apache2/jk_uriMap.lo 
>> ../../../build/jk2/apache2/jk_user.lo 
>> ../../../build/jk2/apache2/jk_vm_default.lo 
>> ../../../build/jk2/apache2/jk_worker_ajp13.lo 
>> ../../../build/jk2/apache2/jk_workerEnv.lo 
>> ../../../build/jk2/apache2/jk_worker_jni.lo 
>> ../../../build/jk2/apache2/jk_worker_lb.lo 
>> ../../../build/jk2/apache2/jk_worker_run.lo 
>> ../../../build/jk2/apache2/jk_worker_status.lo
>> rm -fr ../../../build/jk2/apache2/.libs/jkjni.la 
>> ../../../build/jk2/apache2/.libs/jkjni.* 
>> ../../../build/jk2/apache2/.libs/jkjni.*
>>
>> *** Warning: This library needs some functionality provided by -lapr-0.
>> *** I have the capability to make that library automatically link in when
>> *** you link to this library.  But I can only do this if you have a
>> *** shared version of the library, which you do not appear to have.
>>
>> *** Warning: libtool could not satisfy all declared inter-library
>> *** dependencies of module jkjni.  Therefore, libtool will create
>> *** a static module, that should work as long as the dlopening
>> *** application is linked with the -dlopen flag.
>> ar cru ../../../build/jk2/apache2/.libs/jkjni.a 
>> ../../../build/jk2/apache2/jk_jni_aprImpl.lo 
>> ../../../build/jk2/apache2/jk_channel_apr_socket.lo 
>> ../../../build/jk2/apache2/jk_channel.lo 
>> ../../../build/jk2/apache2/jk_channel_jni.lo 
>> ../../../build/jk2/apache2/jk_channel_socket.lo 
>> ../../../build/jk2/apache2/jk_channel_un.lo 
>> ../../../build/jk2/apache2/jk_config.lo 
>> ../../../build/jk2/apache2/jk_config_file.lo 
>> ../../../build/jk2/apache2/jk_endpoint.lo 
>> ../../../build/jk2/apache2/jk_env.lo 
>> ../../../build/jk2/apache2/jk_handler_logon.lo 
>> ../../../build/jk2/apache2/jk_handler_response.lo 
>> ../../../build/jk2/apache2/jk_logger_file.lo 
>> ../../../build/jk2/apache2/jk_logger_win32.lo 
>> ../../../build/jk2/apache2/jk_map.lo 
>> ../../../build/jk2/apache2/jk_md5.lo 
>> ../../../build/jk2/apache2/jk_msg_ajp.lo 
>> ../../../build/jk2/apache2/jk_mutex.lo 
>> ../../../build/jk2/apache2/jk_mutex_proc.lo 
>> ../../../build/jk2/apache2/jk_mutex_thread.lo 
>> ../../../build/jk2/apache2/jk_nwmain.lo 
>> ../../../build/jk2/apache2/jk_objCache.lo 
>> ../../../build/jk2/apache2/jk_pool_apr.lo 
>> ../../../build/jk2/apache2/jk_pool.lo 
>> ../../../build/jk2/apache2/jk_registry.lo 
>> ../../../build/jk2/apache2/jk_requtil.lo 
>> ../../../build/jk2/apache2/jk_shm.lo 
>> ../../../build/jk2/apache2/jk_signal.lo 
>> ../../../build/jk2/apache2/jk_uriEnv.lo 
>> ../../../build/jk2/apache2/jk_uriMap.lo 
>> ../../../build/jk2/apache2/jk_user.lo 
>> ../../../build/jk2/apache2/jk_vm_default.lo 
>> ../../../build/jk2/apache2/jk_worker_ajp13.lo 
>> ../../../build/jk2/apache2/jk_workerEnv.lo 
>> ../../../build/jk2/apache2/jk_worker_jni.lo 
>> ../../../build/jk2/apache2/jk_worker_lb.lo 
>> ../../../build/jk2/apache2/jk_worker_run.lo 
>> ../../../build/jk2/apache2/jk_worker_status.lo
>> ranlib ../../../build/jk2/apache2/.libs/jkjni.a
>> creating ../../../build/jk2/apache2/jkjni.la
>> (cd ../../../build/jk2/apache2/.libs && rm -f jkjni.la && ln -s 
>> ../jkjni.la jkjni.la)
>> /etc/httpd2/build/libtool  --mode=install  cp 
>> ../../../build/jk2/apache2/jkjni.la `pwd`/../../../build/jk2/apache2
>> cp ../../../build/jk2/apache2/.libs/jkjni.lai 
>> /home/root/jakarta-tomcat-connectors-jk2-2.0.2-src/jk/native2/server/apache2/../../../build/jk2/apache2/jkjni.la

>>
>> cp ../../../build/jk2/apache2/.libs/jkjni.a 
>> /home/root/jakarta-tomcat-connectors-jk2-2.0.2-src/jk/native2/server/apache2/../../../build/jk2/apache2/jkjni.a

>>
>> ranlib 
>> /home/root/jakarta-tomcat-connectors-jk2-2.0.2-src/jk/native2/server/apache2/../../../build/jk2/apache2/jkjni.a

>>
>> chmod 644 
>> /home/root/jakarta-tomcat-connectors-jk2-2.0.2-src/jk/native2/server/apache2/../../../build/jk2/apache2/jkjni.a

>>
>> libtool: install: warning: remember to run `libtool --finish 
>> /usr/lib/apache2'
>> make[1]: Leaving directory 
>> `/home/root/jakarta-tomcat-connectors-jk2-2.0.2-src/jk/native2/server/apache2' 
>>
>>
>>
>> NB, my libapr is /usr/lib/libapr.so.0.9.2
>>
>> And the server/apache2/Makefile.in have a -lapr-0 !!!!
> 
> 
> Oops... I have to port a patch I have done for mod_webapp.
> 
>>
>> My next question will be, should we have a libapr-0.so
>> or libapr.so ????
> 
> 
> libapr-0.so

Well it's not the case in my box and I found why (something to be
investigated or explained by apr team).

In fact I used in my build a custom layout and this layout DIDN'T
SET libsuffix which seems to be at -${APR_MAJOR_VERSION} when no
special layout is provided.

So it's normal in my case to have libapr.so instead of libapr-0.so.

Question should we have libapr-0.so when you dont' want to have parallel
installs ?

For example the windows version of Apache 2.0.43 came with libapr.dll
and not libapr-0.dll.

On Linux, Mandrake use libapr-0, Redhat use libapr,

> I have the following on my machine:
> +++
> -rw-r--r--    1 apache20 users        6343 Nov 28 13:41 apr.exp
> -rw-r--r--    1 apache20 users     2792234 Nov 28 13:41 libapr-0.a
> -rw-r--r--    1 apache20 users         725 Nov 28 13:41 libapr-0.la
> lrwxrwxrwx    1 apache20 users          17 Nov 28 13:41 libapr-0.so -> 
> libapr-0.so.0.9.2
> lrwxrwxrwx    1 apache20 users          17 Nov 28 13:41 libapr-0.so.0 -> 
> libapr-0.so.0.9.2
> -rwxr-xr-x    1 apache20 users      531868 Nov 28 13:41 libapr-0.so.0.9.2
> +++
> 
> BTW: How did you build the mod_jk2.so for Apache-2.0?

> 



--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>


Mime
View raw message