2013/5/26 Jaroslav Fikker <fik...@atlas.cz>:
> Hello.
>
> To Chris: Thank you very much for your comments.
>
> Is there anyone who knows why Tomcat 7.0.25 (commons-daemon-1.0.8-native-src) 
> started to use jni_md.h which is not part of IBM Java? I didn't encounter any 
> problem with compilation of Tomcat Unix daemon (jsvc) until version Tomcat 
> 7.0.23 (commons-daemon-1.0.7-native-src). Is it bug or intention? Thank you 
> very much for your help.
>

The daemon is a subproject of Apache Commons, not of Tomcat,
http://commons.apache.org/proper/commons-daemon/

http://svn.apache.org/viewvc?diff_format=l&view=revision&revision=1194902

I would guess that you cannot compile JNI code with Oracle Java,
unless you have the directory containing jni_md.h (machine-dependent
part of jni.h) on your include path. The file is not in "JDK/include/"
directory, but in "JDK/include/<os>/" where <os> name varies.

> -classpath /opt/tomcat/lib/tomcat-api.
jar,/opt/tomcat/lib/tomcat-api.jar,/opt/tomcat/lib/tomcat-util.jar,..

Why?? You are trying to place those libraries into System classloader.

The recommended configuration is to put only several jars there.
The Tomcat's Bootstrap class will configure the Common classloader as
appropriate.
It is documented here:
http://tomcat.apache.org/tomcat-7.0-doc/class-loader-howto.html

> 6. When replying, please write your text below the quoted one.
As written here:
http://tomcat.apache.org/lists.html#tomcat-users

Best regards,
Konstantin Kolinko

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to