tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From stephan beal <>
Subject errors building the 1.2.4 jk connectors: tarball missing required files/dirs???
Date Mon, 16 Jun 2003 07:56:36 GMT
Good morning, Tomcatters,

i'm attempting to build the 1.2.4 release of the jk connectors, and i'm 
running into the problems described below. i eventually got the tree to 
build, but only by jumping through a lot of hoops. This post, 
therefore, can be considered both a question about why the build 
process isn't working for me and a partial "how to" for someone having 
similar problems:

- jakarta-tomcat-connectors-jk-1.2.4 source tarball
- Ant 1.5.3
- Tomcat 3.3.1 (sorry, upgrading is not an option)
- Apache 1.3.27
- JDK 1.4.1_02 and 1.4.1_03
- Solaris 8/Sparc (SunOS 5.8) and Linux/x86 (Suse 8.2)
- various autotools/gcc versions (see below)

i've edited the sample to point it to the proper Apache 
and Tomcat paths. When starting the build (via a no-args call to 'ant') 
i get:

Warning: Could not find file 

to copy.

i googled up a copy of tomcat-coyote.jar and dropped it into the 
above-listed dir (which was not part of the tarball). Then i got the 
following error:

does not exist!

Indeed, the build tree has no 'jkant' directory. i get this same error 
when running 'ant' and 'ant native'. Out of curiosity i created 
jkant/java, then got this error:
does not exist!

As you can probably guess, i mkdir'd jk/java. AND IT BUILDS, or at least 
builds some jars. Now when running 'ant native' i get a new error:

Warning: Could not find file 
to copy.

Of course it can't find ant.tasks: the jkant dir isn't in the tarball:
stephan@zeus[~/upgrade/jakarta-tomcat-connectors-jk-1.2.4-src] $ find . 
-name ant.tasks

The build process says it recognizes that i have Tomcat 3.3.1 and Apache 
1.3.27, so i'm assuming i can rule out any misdetection-related 
     [echo] Tomcat33: true /u/www/tomcat3.3.1
     [echo] Apache13: true /u/www/apache

After doing a system-wide upgrade to the latest autotool/autoconf, plus 
a down-grade of gcc (3.2 --> 2.95.2), i was finally able to get the 
'native' tree to build using the autotools process, but not before 
forcefully removing about half of my hair.

Okay, so i've finally got it built, but i'm still stumped as to why the 
ant-based process fails, and would really prefer to get that process 
working. Are the missing files/dirs ommissions from the tarball, 
omissions from the README, or omissions in my understanding of how to 
build the tree? (Feel free to answer in language appropriate for a 
seasoned autotools/ant user. In the case of an obvious screw-up on my 
part, please go gentle on me - it's been a very long night ;)

Thanks in advance for your time,

----- stephan
The Guy With No Job Title -
Student: "Master, you must teach me the way of liberation!"
Master:  "Tell me who it is that binds you."
Student: "No one binds me!"
Master:  "Then why do you seek liberation?"

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message