----------------------------------------------------------------
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!!!
----------------------------------------------------------------

At 5:19 PM -0700 6/30/00, Jon Stevens wrote:
>on 6/30/2000 4:55 PM, "Scott Kelley" <[EMAIL PROTECTED]> wrote:
>
>>> I had similar problem. Running Apache's configure script with
>>> --activate-module=src/modules/jserv/libjserv.a  option
>>> again after installation of jserv solved the problem.
>>
>> I tried this and you're correct, it does compile properly when I
>> re-run the configure script that way. Thank you!
>>
>> My next question is, of course, why did that work? Why didn't it work
>> the first time around?
>
>Because you didn't follow the directions in the INSTALL file.
>
>"Configure Apache First - IMPORTANT"

I'm sorry, Jon, but I'm not convinced that this is the case.

At 11:53 AM -0400 7/3/00, Boris Niyazov wrote:
>Well, I DID follow instructions and DID configure Apace first,  and then build
>jserv 1.1 ... Anyway, I had to rerun apache's configure script in order to
>create proper makefile in src/modules/jserv and make jserv work ....

I believe I did follow the instructions properly as well. As I 
mentioned, I'm running the whole thing from a script, and the first 
commands the script executes are:

    cd /home/users/sk01/servlet.engine/apache_1.3.12
    ./configure \
       --with-layout=Apache \
       --prefix=/home/users/sk01/servlet.engine/apache
    make

After getting these messages, I did go back and re-examine the 
INSTALL document for probably the 20th time, and I noticed one 
additional bit that I had missed on the previous readings, and added 
an extra

    make install

to my script, run against Apache before attempting to configure 
JServ. It made no difference. src/modules/jserv is still incomplete, 
and the build fails. (I assume this is because the JServ install only 
needs the generated headers mentioned in the INSTALL document, and 
doesn't require Apache to be fully installed.)

Here's an additional bit of information that may prove useful. When 
my script runs, the output I get when JServ run's Apache's configure 
script looks like this:

>./config.status --activate-module=src/modules/jserv/libjserv.a
>Configuring for Apache, Version 1.3.12
> + using installation path layout: Apache (config.layout)
> + activated jserv module (modules/jserv/libjserv.a)
>Creating Makefile
>Creating Configuration.apaci in src
>Creating Makefile in src
> + configured for Solaris 280 platform
> + setting C compiler to gcc
> + setting C pre-processor to gcc -E
> + checking for system header files
> + adding selected modules
> + checking sizeof various data types
> + doing sanity check on compiler and options
>Creating Makefile in src/support
>Creating Makefile in src/os/unix
>Creating Makefile in src/ap
>Creating Makefile in src/main
>Creating Makefile in src/lib/expat-lite
>Creating Makefile in src/modules/standard

If, after my install script finishes, I go back into the Apache 
directory and run config-status again:

    cd apache_1.3.12
    config.status

The results are somewhat different:

>Configuring for Apache, Version 1.3.12
> + using installation path layout: Apache (config.layout)
> + activated jserv module (modules/jserv/libjserv.a)
>Creating Makefile
>Creating Configuration.apaci in src
>Creating Makefile in src
> + configured for Solaris 280 platform
> + setting C compiler to gcc
> + setting C pre-processor to gcc -E
> + checking for system header files
> + adding selected modules
>    o jserv_module uses ConfigStart/End
> + checking sizeof various data types
> + doing sanity check on compiler and options
>Creating Makefile in src/support
>Creating Makefile in src/os/unix
>Creating Makefile in src/ap
>Creating Makefile in src/main
>Creating Makefile in src/lib/expat-lite
>Creating Makefile in src/modules/standard
>Creating Makefile in src/modules/jserv

Notice that while both runs of Apache configure claim to be 
activating the jserv module, only the latter invocation reports that 
it's actually adding the module and creating the necessary Makefile.

Just to make sure I'm not misunderstanding anything, here is the part 
of the INSTALL document that I believe Jon was referring to:

>  3. Configure Apache First - IMPORTANT
>     ----------------------------------
>
>  If you are using a source distribution then you have to configure Apache
>  first (some generated header files are needed for Apache JServ to pass its
>  configure checks).  You do not need to worry about specifying the
>  Apache JServ module for this first run.
>
>  Thus, a first time configure line to build a static version of Apache
>  would look like this:
>
>  ./configure \
>       --prefix=/usr/local/apache
>  make
>  make install

and here, again, are the commands that my script is executing:

>cd /home/users/sk01/servlet.engine/apache_1.3.12
>./configure \
>   --with-layout=Apache
>   --prefix=/home/users/sk01/servlet.engine/apache
>make
>make install
>cd /home/users/sk01/servlet.engine/ApacheJServ-1.1.2
>./configure \
>   --with-apache-src=/home/users/sk01/servlet.engine/apache_1.3.12 \
>   --enable-apache-config \
>   --prefix=/home/users/sk01/servlet.engine/jserv \
>   --with-jdk-home=/usr/java1.2 \
>   --enable-debugging \
>   --with-JSDK=/home/users/sk01/servlet.engine/JSDK2.0/lib/jsdk.jar
>make
>make install
>cd /home/users/sk01/servlet.engine/apache_1.3.12
>make
>make install

and, just for the sake of completeness, here is the relevant portion 
of the script that is generating those commands:

># Initil configure and build of Apache
>echo "CONFIGURING APACHE"
>cd ${APACHE_SRC}
>./configure \
>        "--prefix=${APACHE_DEST}"
>echo "BUILDING APACHE (FIRST BUILD)"
>make
>make install
>
># Inititial configure and build of JServ
>echo "CONFIGURING JSERV"
>cd ${JSERV_SRC}
>./configure \
>        "--with-apache-src=${APACHE_SRC}" \
>        "--enable-apache-config" \
>        "--prefix=${JSERV_DEST}" \
>        "--with-jdk-home=${JDK_DIR}" \
>        "--enable-debugging" \
>        "--with-JSDK=${JSDK_JAR}"
>echo "BUILDING JSERV"
>make
>make install
>
># Second build of Apache; incorporates JServ
>echo "BUILDING APACHE (SECOND BUILD)"
>cd ${APACHE_SRC}
>make
>make install

This script worked great for JServ 1.0, and has been changed only 
minimally for JServ 1.1.2. The changes primarily reflect those 
mentioned in JServ's docs/upgrade.html file.

For my own sake, I hope I am doing something profoundly stupid, or 
that I'm simply misreading the documentation. Mistakes like that tend 
to be easy to fix! :-)

To reiterate the question, does anyone know why I seem to need to 
re-run Apache's configure script after building JServ?

Thanks,

Scott


--------------------------------------------------
Scott Kelley, [EMAIL PROTECTED]
Biology Computing Services, UC San Diego
--------------------------------------------------


--
--------------------------------------------------------------
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