Thanks, As it turned out I ignored the dependency and installed. What I note is that RPMs are very useful in determining your dependencies. It listed a bunch of rpms I needed, I sought them out and now have the dependencies for being able to build connectors for Apache 1.3 (not that I need them, I am concentrating on 2.0 at the mo. although would be happy with any version that actually worked), I was missing apxs for 1.3 before when I built the connectors from source.
But it does not replace you config files, so I still have exactly the same errors I had before, see my other email from an hour ago. It does give me some assurance that it was not my build of the connectors that caused the problem. So it must be the config, if only I could see what is wrong with the config! David -----Original Message----- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: 27 September 2002 16:37 To: 'Tomcat Users List' Subject: RE: New Release JK 1.2.0 not installing All due respect to the RPM managers, but I honestly, truly feel that you can get up and running much quicker without using RPMs, and just using the Tomcat binary install and a connector binary. I'm not bragging, but I can do a Tomcat+connector install on RedHat now almost quicker than an RPM could do it...it's that easy. Tomcat is so self-contained, I find it difficult to understand the need for an RPM at all, unless it is because the RPM creates a new user (tomcat4) and adds some startup scripts to /etc/init.d (does it even do that much?). Try a binary install of Tomcat, not an RPM. Here are the steps, on any Linux: - download Tomcat - unpack Tomcat - symlink /usr/local/tomcat to /usr/local/jakarta-tomcat-some-version - set CATALINA_HOME (or is it TOMCAT_HOME now in 4.1.12?) - make sure JAVA_HOME is set - stick the mod_jk binary in /path/to/apache/modules - edit httpd.conf with JK directives or use auto-conf - start Tomcat - start Apache It's essentially fool-proof, in my experience, anyway. I have no experience with Mandrake, but I can't see how it would break a binary install. Note that the steps above have Tomcat running as root, and that adding start-on-boot scripts to /etc/init.d has to be done manually. John > -----Original Message----- > From: David Wynter [mailto:[EMAIL PROTECTED]] > Sent: Friday, September 27, 2002 11:27 AM > To: 'Tomcat Users List' > Subject: New Release JK 1.2.0 not installing > > > Hi, > > In desperation at not having a working setup and problems > with mod_jk I > thought it cannot get worse and may even get better if I > install the latest > release from RPM (what luxury not having to build it!). > Anyway it tells me > that I need Apache 2.0.42. If I run " > /usr/local/apache2/apachectl status" > it tells me I DO have 2.0.42. So how do I get PAckage Manager > to detect that > it is 2.0.42? What mechanism does it use to determine what version is > installed? > > Mandrake 8.2 distro > > Thanks > > David Wynter > Director > roamware Ltd. > (+44) (0) 208 922 7539 B. > (+44) (0) 7879 605 706 M. > [EMAIL PROTECTED] > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
