Why do we have to check for JNI Headers.  When JDK is installed, the JNI
headers are definitely present
in jdk/include.  Checking the JNI headers extra seems to me adding
uncessary comand to 
configure like

./conifgure --with-jni--header-path=balh --with-jdk--path=blah
--this-is-year-2000=blah and blah blah add 100 more here

checking for javah... javah
checking for java... /usr/bin/java
checking for valid jni headers path... no
configure: warning: JavaDX will be skipped during compilation due to
limitations.
checking for dirent.h that defines DIR... yes


This seems to me idiosyncratic way of supplying 100 commands to
./configure.

In the begining when Pete added JAVADX it was much simplere, that to
check for the presence of only
JDK.

I syggest these extra stuff should be removed, it maked life more
compilcated.

Thanks
Suhaib

Reply via email to