Building jakarta-tomcat-connectors-jk2-2.0.2-src [HOW?] 2004-01-09 - By Shapira, Yoav
Back
Howdy,
I don't deal with the connectors, much less building them, but just from
a generic unix point of view isn't Makefile.in a feeder into a configure
script to be run before make? You need to run configure, which will
diagnose your system and create a normal Makefile from the Makefile.in
template, with the variables properly substituted. Just a guess.
Yoav Shapira
Millennium ChemInformatics
>-- --Original Message-- --
>From: Carlos Cajina - Hotmail [mailto:cecajina@(protected)]
>Sent: Friday, January 09, 2004 3:14 PM
>To: Tomcat Users List
>Subject: Building jakarta-tomcat-connectors-jk2-2.0.2-src [HOW?]
>
>Hi everyone.
>
>Tryin' to build mod_jk2 for my Slackware box (version 9.1 with
reiserfs)
>I've come to a dead-end, and I would appreciate any help since the
>documentation I've looked into (including the mailing lists) seems to
be
>out of date regarding the building process for version 2.0.2 of the
>Jakarta-Tomcat-Connectors.
>
>Please consider the necessary enviroment variables set up as follows:
>
>JTC_HOME = /usr/src/jakarta-tomcat-connectors-jk2-2.0.2-src/
>JAVA_HOME = /usr/local/java/j2sdk1.4.2_03
>TOMCAT_HOME = /usr/local/tomcat/jakarta-tomcat-4 (See http://cat-4.ora-code.com).1.29
>APACHE2_HOME = /usr/local/apache2
>ANT_HOME = /usr/local/ant/apache-ant-1 (See http://ant-1.ora-code.com).5.4
>
>In order to successfully run the Ant build file I had to:
>
>1. Modify the provided $JTC_HOME/jk/build.properties.sample to match my
>enviroment (set up paths, basically)
>2. Create an empty 'java' directory inside $JTC_HOME/jk
>3. Create the following directory structure inside $JTC_HOME:
>'coyote/build/lib'
>4. Copy every $TOMCAT_HOME/server/lib/*.jar file into
>$JTC_HOME/coyote/build/lib
>
>After the build process, the necessary files to actually generate the
*.so
>module file for the JK2 connector are left in
>$JTC_HOME/jk/native2/server/apache2
>
>I assumed that the 'Makefile.in' file was the one to be renamed as
>'Makefile' in order tu run make, so I did renamed it and executed make
but
>got the following output:
>
>mkdir -p ../../../build/jk2/apache2
>make: APACHE2_HOME@/build/libtool: Command not found
>make: *** [../../../build/jk2/apache2/jk_channel.lo] Error 127
>
>Apparently, the APACHE2_HOME@ variable was the source of the problem,
so I
>went and modified the Makefile changing APACHE2_HOME=@(protected)@
>into APACHE2_HOME=/usr/local/apache2
>
>That solved the problem, but then another one came up. When executing
make
>again, I got the folling output:
>
>mkdir -p ../../../build/jk2/apache2
>/usr/local/apache2/build/libtool --mode=compile @(protected)@ @(protected)@
>@(protected)@ -I../../include @(protected)@ @(protected)@ -I
>@(protected)@/include -I @(protected)@/include/@(protected)@ -DCHUNK_SIZE@(protected) -
>DUSE_APACHE_MD5 -DHAS_APR @(protected)@ @(protected)@ -c
./../common/jk_channel.c
>-o ../../../build/jk2/apache2/jk_channel.lo
>rm -f ../../../build/jk2/apache2/.libs/jk_channel.lo
>@(protected)@ @(protected)@ @(protected)@ -I../../include @(protected)@
>@(protected)@ -I @(protected)@/include -I @(protected)@/include/@(protected)@ -
>DCHUNK_SIZE@(protected) -DUSE_APACHE_MD5 -DHAS_APR @(protected)@ @(protected)@ -c
>./../common/jk_channel.c -fPIC -DPIC -o
>./../../build/jk2/apache2/.libs/jk_channel.lo
>/usr/local/apache2/build/libtool: line 1: @(protected)@: command not found
>make: *** [../../../build/jk2/apache2/jk_channel.lo] Error 1
>
>Its seemed that the problem was now with the @(protected)@ variable -which I
think
>should point to /usr/bin/cc. I used the same reasoning as before I
changed
>CC=@(protected)@ for CC=/usr/bin/cc, but got an error message pretty much like
the
>last one except for the two last lines:
>
>..
>cc: cannot specify -o with -c or -S and multiple compilations
>make: *** [../../../build/jk2/apache2/jk_channel.lo] Error 1
>
>...And finally.... Here's where I'm stalled :-(
>
>Any help will be geratly appreciated.
>
>Regards,
>
> Carlos
This e-mail, including any attachments, is a confidential business
communication, and may contain information that is confidential, proprietary
and/or privileged. This e-mail is intended only for the individual(s) to whom
it is addressed, and may not be saved, copied, printed, disclosed or used by
anyone else. If you are not the(an) intended recipient, please immediately
delete this e-mail from your computer system and notify the sender. Thank you.
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)
|
|
