----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files.  Don't make us guess your problem!!!
----------------------------------------------------------------

I trying to build on Solaris 2.7, Apache 1.3.9 and JServ1.1b3.

Configure fails with the following message:

checking JSDK... /usr/bin/find: bad option -or
/usr/bin/find: path-list predicate-list
configure: error: no javax.servlet.Servlet class or jar with it in
/usr/jsdk2.0/lib

I am assuming that something weird is happening to the variable strings
used to create the find command referred to above, but I tried to
eliminate things I had under my direct control: 

The configure cmd looked like:

./configure \
                --prefix=/usr/local/jserv \
                --with-apxs=/usr/local/apache/bin/apxs \
                --with-jdk-home=/usr/java \
                --with-java-platform=2 \
                --with-JSDK=/usr/jsdk2.0/lib \
                --disable-debugging

I have also tried a pretty minimal configure with just the
 --with-apxs=/usr/local/apache/bin/apxs 

input (I created a symbolic link from /usr/local/JSDK2.0 to where my
real one is so the configure scripts last resort looking for JSDK would
find it)  with the same results.  My binary search path is:

/usr/local/bin /u1/OraHome/bin /usr/bin /usr/sbin /usr/ucb

and find is only in /usr/bin.

I have tried this in csh, ksh and sh with same results.
I have no alias for find set up.

I also get this same configure error with 1.1b2.

I am sure something stupid has gone wrong or someone else would have
posted about this, but I can't figure it out.


--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Archives and Other:  <http://java.apache.org/main/mail.html>
Problems?:           [EMAIL PROTECTED]

Reply via email to