RE: Redhat9 / mod_jk2 builds from source

2004-01-19 Thread Brennon Obst
Subject: Re: Redhat9 / mod_jk2 builds from source Hi Mark, Oscar Sorry I now realise you want the ssl feature in apache 2 build. try the following ./configure --with-ssl=shared --enable-modules=all --enable-shared=max remember I'm running things on Linux 9 by default OpenSSH running as a daemon

Re: Redhat9 / mod_jk2 builds from source

2004-01-17 Thread George Shafik
ssl.conf files right - can you e-mail any that work Cheers, George - Original Message - From: George Shafik [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Thursday, January 15, 2004 8:39 PM Subject: Re: Redhat9 / mod_jk2 builds from source Opps typo ./configure

Re: Redhat9 / mod_jk2 builds from source

2004-01-15 Thread George Shafik
: Mark Eggers [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Thursday, January 15, 2004 1:05 PM Subject: Re: Redhat9 / mod_jk2 builds from source Oscar - set $JAVA_HOME if you get configure errors with include-os-type=include/linux. The configure script will tack

Re: Redhat9 / mod_jk2 builds from source

2004-01-15 Thread George Shafik
: Redhat9 / mod_jk2 builds from source Hi Mark, Oscar, and anyone interested: I found the following always works: make make install I think I've could the eXtrem functionality - I call is Xapache while drinking lots of Pepsi :-) enjoy, George - Original Message - From

Re: Redhat9 / mod_jk2 builds from source

2004-01-15 Thread OUTTERS Guillaume
George Shafik wrote: I found the following always works: ./configure --enable-module=all --enabled-shared=max make make install I personaly had (on Solaris 9 with the gcc suite) to explicitely add: --enable-so --enable-rule=SHARED_CORE --enable-static=no --enable-shared=yes I don't know which

Redhat9 / mod_jk2 builds from source

2004-01-14 Thread Oscar Carrillo
Hi, The info I've seen on this list about building mod_jk2 has been for rpm installation. Here's the info I gathered so far trying to do Apache and the connector all from source. Building Apache2.0.48 and mod_jk2 (2.0.2) works seamlessly the following way: If you built Apache from source, such

Re: Redhat9 / mod_jk2 builds from source

2004-01-14 Thread Oscar Carrillo
My apologies, I did find some good info on the list just awhile back, particularly by Mark Eggers. This just mostly shows it indeed is repeatable :-) Oscar On Wed, 14 Jan 2004, Oscar Carrillo wrote: Hi, The info I've seen on this list about building mod_jk2 has been for rpm

Re: Redhat9 / mod_jk2 builds from source

2004-01-14 Thread Mark Eggers
Oscar, Not a problem :-) I do have some additions to my original post. The changes get UNIX sockets working as well as IP sockets. Set the following environment variables: export LDFLAGS=-lgdbm -lldap -lexpat -ldb export CPPFLAGS=-I/usr/kerberos/include -I/usr/openssl/include (all on one

Re: Redhat9 / mod_jk2 builds from source

2004-01-14 Thread Oscar Carrillo
Cool. Questions inside. On Wed, 14 Jan 2004, Mark Eggers wrote: Oscar, Not a problem :-) I do have some additions to my original post. The changes get UNIX sockets working as well as IP sockets. Set the following environment variables: export LDFLAGS=-lgdbm -lldap -lexpat -ldb

Re: Redhat9 / mod_jk2 builds from source

2004-01-14 Thread Mark Eggers
Oscar, This is all pretty much in a bug I posted to on naygoya.apache.org (#17762). If you build Apache with all shared modules, then there are some dependencies in apr and aprutil. An ldd from 2.0.46 on Redhat 9 (2.4.20-9) shows the following: ldd /home/apache/lib/libapr-0.so.0.9.4

Re: Redhat9 / mod_jk2 builds from source

2004-01-14 Thread Oscar Carrillo
Interesting... I only get this with apache 2.0.48 from ldd /usr/local/apache2/lib/libapr-0.so.9.5: libc.so.6 = /lib/tls/libc.so.6(0x4200) /lib/ld-linux.so.2 = /lib/ld-linux.so.2 (0x8000) I guess that means I didn't build with the LD_FLAGS that you mentioned. The

Re: Redhat9 / mod_jk2 builds from source

2004-01-14 Thread Mark Eggers
Oscar - set $JAVA_HOME if you get configure errors with include-os-type=include/linux. The configure script will tack on the $JAVA_HOME value. If you don't, then give the full path to the header files. I think I get all the extra info because I build Apache with: ./configure --with-ssl=shared