[TC4] mod_webapp.so compilation failure

2001-09-30 Thread Eirik Dentz

I'm struggling to get apache 1.3.20 working with Tomcat 4.0
First I tried the linux binary, but I got this message when I did
"apachectl configtest" 

[warn] Loaded DSO /usr/lib/apache/1.3/mod_webapp.so uses plain Apache
1.3 API, this module might crash under EAPI! (please recompile it with -DEAPI)

So I checked the mod_webapp source from CVS and followed README.txt
instructions for compilation on the following set up.

Debian/Unstable
libc6  2.2.4-2 
libc6-dev  2.2.4-2
Apache 1.3.20
mod_ssl 2.8.4-1

And the build fails with the following error message:


make[1]: Entering directory "apache-1.3"
make[1]: Invoking "make  build"
make[2]: Entering directory 
`/home/eirik/tomcat4_build/jakarta-tomcat-connectors/webapp/apache-1.3'
{ APXS_LDFLAGS_SHLIB="`/usr/bin/apxs -q LDFLAGS_SHLIB` \
 \
-lm -lcrypt -lnsl -ldl" ; \
APXS_LDFLAGS_SHLIB=`/bin/echo ${APXS_LDFLAGS_SHLIB}` ; \
APXS_CFLAGS="`/usr/bin/apxs -q CFLAGS` \
-g -O2 \
-g -O2 \
 \
-DLINUX=2 -D_REENTRANT \
   
-I/home/eirik/tomcat4_build/jakarta-tomcat-connectors/webapp/apr/include \
   
-I/home/eirik/tomcat4_build/jakarta-tomcat-connectors/webapp/include \
" ; \
APXS_CFLAGS=`/bin/echo ${APXS_CFLAGS}` ; \
/usr/bin/apxs \
-S CFLAGS="${APXS_CFLAGS}" \
-S LDFLAGS_SHLIB="${APXS_LDFLAGS_SHLIB}" \
-o "mod_webapp.so" \
-c "mod_webapp.c" \
   
"/home/eirik/tomcat4_build/jakarta-tomcat-connectors/webapp/lib/libwebapp.a" \
   
"/home/eirik/tomcat4_build/jakarta-tomcat-connectors/webapp/lib/libapr.a"
; \
}
Bareword found where operator expected at (eval 6) line 1, near
""-DLINUX=22 -DEAPI -DTARGET="apache"
(Missing operator before apache?)
String found where operator expected at (eval 6) line 1, at end of line
gcc -DLINUX=22 -DEAPI -DTARGET="apache" -I/usr/include/db1 -DUSE_HSREGEX
-DUSE_EXPAT -I../lib/expat-lite -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -fpic -DSHARED_MODULE -I/usr/include/apache-1.3 
-c mod_webapp.c
mod_webapp.c:70: wa.h: No such file or directory
apxs:Break: Command failed with rc=1
make[2]: *** [mod_webapp.so] Error 1
make[2]: Leaving directory 
`/home/eirik/tomcat4_build/jakarta-tomcat-connectors/webapp/apache-1.3'
make[1]: Exiting directory "apache-1.3"
make[1]: *** [template] Error 2
make[1]: Leaving directory `/home/eirik/tomcat4_build/jakarta-tomcat-connectors/webapp'
make: *** [apache-1.3-build] Error 2



I took a quick look through the archive and noticed that a few others
have run into this problem as well, but I didn't see any follow-ups or
responses.  Has anybody else encountered this problem, and found a solution?

Thanks in Advance

eirik



Re: mod_ssl?

2001-05-29 Thread Eirik Dentz


Normally you can get it here:

www.modssl.org

but it looks like the server is down right now.  Try a google search?

> From: Lessault Jean-Luc <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> Date: Tue, 29 May 2001 15:49:06 +0200
> To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
> Subject: mod_ssl?
> 
> 
> Hi all!
> 
> Would someone be able to tell me where to find mod_ssl?
> Thanks.
> 
> 




Re: Becoming a CA Authority

2001-05-28 Thread Eirik Dentz

If you are using openssl the following FAQ should do the trick.  (It worked
for me YMMV)

http://www.modssl.org/docs/2.8/ssl_faq.html#ToC29

You should also be able to find this under the docs for mod_ssl on your
system.

-- 
Eirik Dentz

> From: François Andromaque <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> Date: Mon, 28 May 2001 16:06:15 +0200
> To: <[EMAIL PROTECTED]>
> Subject: Re: Becoming a CA Authority
> 
> Where can i find the instructions create and sign a ca?
> 
> - Original Message -
> From: "Tim O'Neil" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, May 25, 2001 5:38 PM
> Subject: Re: Becoming a CA Authority
> 
> 
>> At 04:45 PM 5/25/2001 +0200, you wrote:
>>> Can someone tell me all the steps to become a CA Authority, create a new
>>> certificate and configure tomcat to use this certificate
>> 
>> Self sign your cert, and your a ca. Of course,
>> your clients will all get dialogs on their
>> browsers asking them if they want to trust your
>> unknown ca unless you can make them all add your
>> ca to their list of known ca's...
> 
>