----------------------------------------------------------------
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 1:16 PM -0700 7/3/00, Jon Stevens wrote:
>ok...that should work because you have --enable-apache-config. maybe that is
>broken with apache 1.3.12 (it used to work with 1.3.9)?
After looking at it some more and trying a variety of things I think
that, yes, --enable-apache-config isn't working right.
If I leave it enabled, and do:
./config.status --activate-module=src/modules/jserv/libjserv.a
just before the second build of apache, the build will succeed, but
Apache reports that it's enabling jserv twice, which looks strange.
(I didn't actually test whether this configuration runs correctly or
not.)
Two things that do work right are:
1) set --enable-apache-config=no and activate the module
manually as listed above, before the second build of Apache.
2) leave --enable-apache-config on and just run ./config.status
with no arguments before the second build of Apache.
I'll almost certainly settle for one of the above solutions; either
one is fine for my purposes.
> > To reiterate the question, does anyone know why I seem to need to
>> re-run Apache's configure script after building JServ?
>
>nope. take a look at the configure.in file and let me know if you can figure
>out why --enable-apache-config stopped working. i never use that method
>except for testing and i haven' tested against 1.3.12...
I sort of wondered that... if I was doing this install by hand, I
would have just dismissed it as a weird glitch, but I'm writing a
script for other people in my group to use, so when something weird
happens I blow the whole installation away and try to make the
weirdness go away.
The script we used for JServ 1.0/Apache 1.3.6 used
--enable-apache-config (well, --enable-apache-conf) and didn't
require a separate call to configure script to activate the module,
which is why this seemed weird to me.
I did look at configure.in, and noticed something that seemed strange to me:
if ${TEST} ! -x "${apache_dir}/config.status" ; then
conf_cmd="./configure --activate-module=src/modules/jserv/libjserv.a"
elif (cd $apache_dir && ${GREP} mod_jserv config.status) ; then
conf_cmd="./config.status"
else
conf_cmd="./config.status --activate-module=src/modules/jserv/libjserv.a"
fi
Shouldn't this be grepping for libjserv instead of mod_jserv?
Since this code doesn't run when --enable-apache-config is off, it's
easy to work around, anyway.
Other than that, I didn't notice anything immediately obvious in
configure.in that explained why it wasn't working. I'll look at it a
little more closely if I get the opportunity.
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]
