You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Glenn Nielsen <gl...@mail.more.net> on 2003/06/11 01:58:41 UTC
[ANN] Apache Tomcat mod_jk 1.2.4 Web Server Connector released
The Tomcat team has released version 1.2.4 of the Tomcat mod_jk web server connector.
This version fixes a number of minor bugs and ports all features from the Apache 1.3 version
to the Apache 2 version of mod_jk 1.2.
See the file CHANGES.txt in the source distribution for a complete list of changes.
The source distribution is available at:
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.4/src/
Binary distributions for different web servers and operating systems will become available
in the next week for download at:
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.4/bin/
Linux RPM's can be found when they become available at:
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.4/rpms/
Documentation for the release is available at:
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.4/doc/
Glenn
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: [ANN] Apache Tomcat mod_jk 1.2.4 Web Server Connector released
Posted by jean-frederic clere <jf...@fujitsu-siemens.com>.
Henri Gomez wrote:
> jean-frederic clere wrote:
>
>> Henri Gomez wrote:
>>
>>>>>
>>>>> BTW, the JF-Clere fix in configure.in to use the libtool in Apache
>>>>> 2.0 case, don't works with Redhat 8.0/9.0 where there is an Apache
>>>>> 2.0.40 with post 2.0.40 security fixes.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> And what is the error? It works with a vanilla Apache-2.0.40.
>>>
>>>
>>>
>>>
>>> I don't know what they do with their 2.0.40 version but here is what
>>> I've got :
>>
>>
>>
>> I don't think that changes in apxs are the problem.
>> But I think that there must be something weird in build/config_vars.mk
>> What does apxs -q LIBTOOL returns?
>
>
> It didn't works :
>
> Use of uninitialized value in concatenation (.) or string at
> /usr/sbin/apxs line 261.
I think I have got it: That is a bug in apxs due to:
LIBTOOL = /bin/sh /usr/bin/libtool $(LTFLAGS)
apxs does not like the $(LTFLAGS).
I have the same error when I do bin/apxs -q EXTRA_INCLUDES in my vanilla Apache!
(even with 2.0.46!)
>
>> And:
>> $APXS -q PREFIX
>> $APXS -q INCLUDEDIR
>> $APXS -q CFLAGS
>> $APXS -q EXTRA_CFLAGS
>> $APXS -q EXTRA_CPPFLAGS
>
>
> All of them works.
>
>> Could you send me the build/config_vars.mk?
>
>
> attached.
>
>>
>> The basic problem is that we use 2 LIBTOOL: In some places (like
>> commons) LIBTOOL is the result of `apxs -q LIBTOOL` and in other
>> places (like apache-2.0) LIBTOOL is the make variable included from
>> build/config_vars.mk. I do not understand why they are different
>> because apxs reads from build/config_vars.mk!!!
>
>
> Yes we should unify.
>
> PS: Some beers on July/August ;-)
Sure!
>
>
>
>
> ------------------------------------------------------------------------
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: [ANN] Apache Tomcat mod_jk 1.2.4 Web Server Connector released
Posted by Henri Gomez <hg...@apache.org>.
jean-frederic clere wrote:
> Henri Gomez wrote:
>
>>>>
>>>> BTW, the JF-Clere fix in configure.in to use the libtool in Apache
>>>> 2.0 case, don't works with Redhat 8.0/9.0 where there is an Apache
>>>> 2.0.40 with post 2.0.40 security fixes.
>>>
>>>
>>>
>>>
>>> And what is the error? It works with a vanilla Apache-2.0.40.
>>
>>
>>
>> I don't know what they do with their 2.0.40 version but here is what
>> I've got :
>
>
> I don't think that changes in apxs are the problem.
> But I think that there must be something weird in build/config_vars.mk
> What does apxs -q LIBTOOL returns?
It didn't works :
Use of uninitialized value in concatenation (.) or string at
/usr/sbin/apxs line 261.
> And:
> $APXS -q PREFIX
> $APXS -q INCLUDEDIR
> $APXS -q CFLAGS
> $APXS -q EXTRA_CFLAGS
> $APXS -q EXTRA_CPPFLAGS
All of them works.
> Could you send me the build/config_vars.mk?
attached.
>
> The basic problem is that we use 2 LIBTOOL: In some places (like
> commons) LIBTOOL is the result of `apxs -q LIBTOOL` and in other places
> (like apache-2.0) LIBTOOL is the make variable included from
> build/config_vars.mk. I do not understand why they are different because
> apxs reads from build/config_vars.mk!!!
Yes we should unify.
PS: Some beers on July/August ;-)
Re: [ANN] Apache Tomcat mod_jk 1.2.4 Web Server Connector released
Posted by jean-frederic clere <jf...@fujitsu-siemens.com>.
Henri Gomez wrote:
>>>
>>> BTW, the JF-Clere fix in configure.in to use the libtool in Apache
>>> 2.0 case, don't works with Redhat 8.0/9.0 where there is an Apache
>>> 2.0.40 with post 2.0.40 security fixes.
>>
>>
>>
>> And what is the error? It works with a vanilla Apache-2.0.40.
>
>
> I don't know what they do with their 2.0.40 version but here is what
> I've got :
I don't think that changes in apxs are the problem.
But I think that there must be something weird in build/config_vars.mk
What does apxs -q LIBTOOL returns?
And:
$APXS -q PREFIX
$APXS -q INCLUDEDIR
$APXS -q CFLAGS
$APXS -q EXTRA_CFLAGS
$APXS -q EXTRA_CPPFLAGS
Could you send me the build/config_vars.mk?
The basic problem is that we use 2 LIBTOOL: In some places (like commons)
LIBTOOL is the result of `apxs -q LIBTOOL` and in other places (like apache-2.0)
LIBTOOL is the make variable included from build/config_vars.mk. I do not
understand why they are different because apxs reads from build/config_vars.mk!!!
>
> ... configure time (note the error reported line 261) :
>
> checking if the linker (/usr/bin/ld) is GNU ld... (cached) yes
> checking for test... /usr/bin/test
> checking for rm... /bin/rm
> checking for grep... /bin/grep
> checking for echo... /bin/echo
> checking for sed... /bin/sed
> checking for cp... /bin/cp
> checking for mkdir... /bin/mkdir
> checking for libtool... /usr/bin/libtool
> need to check for Perl first, apxs depends on it...
> checking for perl... /usr/bin/perl
> Use of uninitialized value in concatenation (.) or string at
> /usr/sbin/apxs line 261.
> building connector for "apache-2.0"
> checking for target platform... unix
> no apache given
> configure: creating ./config.status
> config.status: creating Makefile
> config.status: creating apache-1.3/Makefile
> config.status: creating apache-1.3/Makefile.apxs
> config.status: creating apache-2.0/Makefile
> config.status: creating apache-2.0/Makefile.apxs
> config.status: creating common/Makefile
> config.status: creating common/list.mk
> config.status: creating jni/Makefile
> config.status: executing depfiles commands
>
> ... build time :
>
> Making all in common
> make[1]: Entering directory
> `/home/admin/jakarta-tomcat-connectors-jk-1.2.4-src/jk/native/common'
> mode=compile gcc -I/usr/include/httpd -g -O2 -O2 -g -march=i386
> -mcpu=i686 -pthread -DNO_DBM_REWRITEMAP -g -O2 -DLINUX=2 -D_REENTRANT
> -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -I
> /opt/IBMJava2-131/include -I /opt/IBMJava2-131/include/ -c
> jk_ajp12_worker.c
> mode=compile gcc -I/usr/include/httpd -g -O2 -O2 -g -march=i386
> -mcpu=i686 -pthread -DNO_DBM_REWRITEMAP -g -O2 -DLINUX=2 -D_REENTRANT
> -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -I
> /opt/IBMJava2-131/include -I /opt/IBMJava2-131/include/ -c jk_connect.c
> mode=compile gcc -I/usr/include/httpd -g -O2 -O2 -g -march=i386
> -mcpu=i686 -pthread -DNO_DBM_REWRITEMAP -g -O2 -DLINUX=2 -D_REENTRANT
> -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -I
> /opt/IBMJava2-131/include -I /opt/IBMJava2-131/include/ -c jk_msg_buff.c
> mode=compile gcc -I/usr/include/httpd -g -O2 -O2 -g -march=i386
> -mcpu=i686 -pthread -DNO_DBM_REWRITEMAP -g -O2 -DLINUX=2 -D_REENTRANT
> -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -I
> /opt/IBMJava2-131/include -I /opt/IBMJava2-131/include/ -c jk_util.c
> mode=compile gcc -I/usr/include/httpd -g -O2 -O2 -g -march=i386
> -mcpu=i686 -pthread -DNO_DBM_REWRITEMAP -g -O2 -DLINUX=2 -D_REENTRANT
> -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -I
> /opt/IBMJava2-131/include -I /opt/IBMJava2-131/include/ -c jk_ajp13.c
> mode=compile gcc -I/usr/include/httpd -g -O2 -O2 -g -march=i386
> -mcpu=i686 -pthread -DNO_DBM_REWRITEMAP -g -O2 -DLINUX=2 -D_REENTRANT
> -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -I
> /opt/IBMJava2-131/include -I /opt/IBMJava2-131/include/ -c jk_pool.c
> mode=compile gcc -I/usr/include/httpd -g -O2 -O2 -g -march=i386
> -mcpu=i686 -pthread -DNO_DBM_REWRITEMAP -g -O2 -DLINUX=2 -D_REENTRANT
> -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -I
> /opt/IBMJava2-131/include -I /opt/IBMJava2-131/include/ -c jk_worker.c
> mode=compile gcc -I/usr/include/httpd -g -O2 -O2 -g -march=i386
> -mcpu=i686 -pthread -DNO_DBM_REWRITEMAP -g -O2 -DLINUX=2 -D_REENTRANT
> -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -I
> /opt/IBMJava2-131/include -I /opt/IBMJava2-131/include/ -c
> jk_ajp13_worker.c
> mode=compile gcc -I/usr/include/httpd -g -O2 -O2 -g -march=i386
> -mcpu=i686 -pthread -DNO_DBM_REWRITEMAP -g -O2 -DLINUX=2 -D_REENTRANT
> -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -I
> /opt/IBMJava2-131/include -I /opt/IBMJava2-131/include/ -c jk_lb_worker.c
> mode=compile gcc -I/usr/include/httpd -g -O2 -O2 -g -march=i386
> -mcpu=i686 -pthread -DNO_DBM_REWRITEMAP -g -O2 -DLINUX=2 -D_REENTRANT
> -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -I
> /opt/IBMJava2-131/include -I /opt/IBMJava2-131/include/ -c jk_sockbuf.c
> mode=compile gcc -I/usr/include/httpd -g -O2 -O2 -g -march=i386
> -mcpu=i686 -pthread -DNO_DBM_REWRITEMAP -g -O2 -DLINUX=2 -D_REENTRANT
> -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -I
> /opt/IBMJava2-131/include -I /opt/IBMJava2-131/include/ -c jk_map.c
>
> ...
>
> -O2 -g -march=i386 -mcpu=i686 -pthread -DNO_DBM_REWRITEMAP -g -O2
> -pthread -DNO_DBM_REWRITEMAP -DLINUX=2 -D_REENTRANT -D_XOPEN_SOURCE=500
> -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -c ../common/jk_ajp_common.c
> /bin/sh /usr/bin/libtool --silent --mode=compile gcc
> -I/usr/include/httpd -g -O2 -DUSE_APACHE_MD5 -I ../common -I
> /opt/IBMJava2-131/include -I /opt/IBMJava2-131/include/unix -DLINUX=2
> -D_REENTRANT -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE
> -D_GNU_SOURCE -O2 -g -march=i386 -mcpu=i686 -pthread -DNO_DBM_REWRITEMAP
> -g -O2 -pthread -DNO_DBM_REWRITEMAP -DLINUX=2 -D_REENTRANT
> -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -c
> ../common/jk_context.c
> /bin/sh /usr/bin/libtool --silent --mode=link gcc -I/usr/include/httpd
> -g -O2 -DUSE_APACHE_MD5 -I ../common -I /opt/IBMJava2-131/include -I
> /opt/IBMJava2-131/include/unix -DLINUX=2 -D_REENTRANT
> -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -O2 -g
> -march=i386 -mcpu=i686 -pthread -DNO_DBM_REWRITEMAP -g -O2 -pthread
> -DNO_DBM_REWRITEMAP -DLINUX=2 -D_REENTRANT -D_XOPEN_SOURCE=500
> -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -o mod_jk.la -module -rpath
> /usr/lib/httpd/modules -avoid-version mod_jk.lo
> ../common/jk_ajp12_worker.lo ../common/jk_connect.lo
> ../common/jk_msg_buff.lo ../common/jk_util.lo ../common/jk_ajp13.lo
> ../common/jk_pool.lo ../common/jk_worker.lo ../common/jk_ajp13_worker.lo
> ../common/jk_lb_worker.lo ../common/jk_sockbuf.lo ../common/jk_map.lo
> ../common/jk_uri_worker_map.lo ../common/jk_ajp14.lo
> ../common/jk_ajp14_worker.lo ../common/jk_md5.lo
> ../common/jk_ajp_common.lo ../common/jk_context.lo
> gcc: ../common/jk_ajp12_worker.lo: No such file or directory
> gcc: ../common/jk_connect.lo: No such file or directory
> gcc: ../common/jk_msg_buff.lo: No such file or directory
> gcc: ../common/jk_util.lo: No such file or directory
> gcc: ../common/jk_ajp13.lo: No such file or directory
> gcc: ../common/jk_pool.lo: No such file or directory
> gcc: ../common/jk_worker.lo: No such file or directory
> gcc: ../common/jk_ajp13_worker.lo: No such file or directory
> gcc: ../common/jk_lb_worker.lo: No such file or directory
> gcc: ../common/jk_sockbuf.lo: No such file or directory
> gcc: ../common/jk_map.lo: No such file or directory
> gcc: ../common/jk_uri_worker_map.lo: No such file or directory
> gcc: ../common/jk_ajp14.lo: No such file or directory
> gcc: ../common/jk_ajp14_worker.lo: No such file or directory
> gcc: ../common/jk_md5.lo: No such file or directory
> gcc: ../common/jk_ajp_common.lo: No such file or directory
> gcc: ../common/jk_context.lo: No such file or directory
> make[1]: *** [mod_jk.la] Error 1
> make[1]: Leaving directory
> `/home/admin/jakarta-tomcat-connectors-jk-1.2.4-src/jk/native/apache-2.0'
> make: *** [all-recursive] Error 1
>
> It seems we loose the /bin/sh /usr/bin/libtool --silent in the first
> part of the build (certainly related to the 'customized' Redhat apxs and
> the strange error line 261 of APXS (attached).
Here is the result of a diff:
+++
jfclere@vtxclere:~ > diff -u apxs /home/apache20/apache40/bin/apxs
--- apxs Tue Jun 17 09:02:19 2003
+++ /home/apache20/apache40/bin/apxs Tue Sep 10 16:03:42 2002
@@ -63,7 +63,7 @@
my %config_vars = ();
-my $installbuilddir = "/usr/lib/httpd/build";
+my $installbuilddir = "/home/apache20/apache40/build";
get_config_vars("$installbuilddir/config_vars.mk",\%config_vars);
# read the configuration variables once
@@ -236,6 +236,19 @@
($httpd = $0) =~ s:support/apxs$::;
}
+unless (-x "$httpd") {
+ error("$httpd not found or not executable");
+ exit 1;
+}
+
+unless (grep /mod_so/, `. $envvars && $httpd -l`) {
+ error("Sorry, no shared object support for Apache");
+ error("available under your platform. Make sure");
+ error("the Apache module mod_so is compiled into");
+ error("your server binary `$httpd'.");
+ exit 1;
+}
+
sub get_config_vars{
my ($file, $rh_config) = @_;
@@ -700,5 +713,4 @@
NULL, /* table of config file commands */
%NAME%_register_hooks /* register hooks */
};
-
>
>
>
>
>
> ------------------------------------------------------------------------
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: [ANN] Apache Tomcat mod_jk 1.2.4 Web Server Connector released
Posted by Henri Gomez <hg...@apache.org>.
>>
>> BTW, the JF-Clere fix in configure.in to use the libtool in Apache 2.0
>> case, don't works with Redhat 8.0/9.0 where there is an Apache 2.0.40
>> with post 2.0.40 security fixes.
>
>
> And what is the error? It works with a vanilla Apache-2.0.40.
I don't know what they do with their 2.0.40 version but here is what
I've got :
... configure time (note the error reported line 261) :
checking if the linker (/usr/bin/ld) is GNU ld... (cached) yes
checking for test... /usr/bin/test
checking for rm... /bin/rm
checking for grep... /bin/grep
checking for echo... /bin/echo
checking for sed... /bin/sed
checking for cp... /bin/cp
checking for mkdir... /bin/mkdir
checking for libtool... /usr/bin/libtool
need to check for Perl first, apxs depends on it...
checking for perl... /usr/bin/perl
Use of uninitialized value in concatenation (.) or string at
/usr/sbin/apxs line 261.
building connector for "apache-2.0"
checking for target platform... unix
no apache given
configure: creating ./config.status
config.status: creating Makefile
config.status: creating apache-1.3/Makefile
config.status: creating apache-1.3/Makefile.apxs
config.status: creating apache-2.0/Makefile
config.status: creating apache-2.0/Makefile.apxs
config.status: creating common/Makefile
config.status: creating common/list.mk
config.status: creating jni/Makefile
config.status: executing depfiles commands
... build time :
Making all in common
make[1]: Entering directory
`/home/admin/jakarta-tomcat-connectors-jk-1.2.4-src/jk/native/common'
mode=compile gcc -I/usr/include/httpd -g -O2 -O2 -g -march=i386
-mcpu=i686 -pthread -DNO_DBM_REWRITEMAP -g -O2 -DLINUX=2 -D_REENTRANT
-D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -I
/opt/IBMJava2-131/include -I /opt/IBMJava2-131/include/ -c
jk_ajp12_worker.c
mode=compile gcc -I/usr/include/httpd -g -O2 -O2 -g -march=i386
-mcpu=i686 -pthread -DNO_DBM_REWRITEMAP -g -O2 -DLINUX=2 -D_REENTRANT
-D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -I
/opt/IBMJava2-131/include -I /opt/IBMJava2-131/include/ -c jk_connect.c
mode=compile gcc -I/usr/include/httpd -g -O2 -O2 -g -march=i386
-mcpu=i686 -pthread -DNO_DBM_REWRITEMAP -g -O2 -DLINUX=2 -D_REENTRANT
-D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -I
/opt/IBMJava2-131/include -I /opt/IBMJava2-131/include/ -c jk_msg_buff.c
mode=compile gcc -I/usr/include/httpd -g -O2 -O2 -g -march=i386
-mcpu=i686 -pthread -DNO_DBM_REWRITEMAP -g -O2 -DLINUX=2 -D_REENTRANT
-D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -I
/opt/IBMJava2-131/include -I /opt/IBMJava2-131/include/ -c jk_util.c
mode=compile gcc -I/usr/include/httpd -g -O2 -O2 -g -march=i386
-mcpu=i686 -pthread -DNO_DBM_REWRITEMAP -g -O2 -DLINUX=2 -D_REENTRANT
-D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -I
/opt/IBMJava2-131/include -I /opt/IBMJava2-131/include/ -c jk_ajp13.c
mode=compile gcc -I/usr/include/httpd -g -O2 -O2 -g -march=i386
-mcpu=i686 -pthread -DNO_DBM_REWRITEMAP -g -O2 -DLINUX=2 -D_REENTRANT
-D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -I
/opt/IBMJava2-131/include -I /opt/IBMJava2-131/include/ -c jk_pool.c
mode=compile gcc -I/usr/include/httpd -g -O2 -O2 -g -march=i386
-mcpu=i686 -pthread -DNO_DBM_REWRITEMAP -g -O2 -DLINUX=2 -D_REENTRANT
-D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -I
/opt/IBMJava2-131/include -I /opt/IBMJava2-131/include/ -c jk_worker.c
mode=compile gcc -I/usr/include/httpd -g -O2 -O2 -g -march=i386
-mcpu=i686 -pthread -DNO_DBM_REWRITEMAP -g -O2 -DLINUX=2 -D_REENTRANT
-D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -I
/opt/IBMJava2-131/include -I /opt/IBMJava2-131/include/ -c
jk_ajp13_worker.c
mode=compile gcc -I/usr/include/httpd -g -O2 -O2 -g -march=i386
-mcpu=i686 -pthread -DNO_DBM_REWRITEMAP -g -O2 -DLINUX=2 -D_REENTRANT
-D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -I
/opt/IBMJava2-131/include -I /opt/IBMJava2-131/include/ -c jk_lb_worker.c
mode=compile gcc -I/usr/include/httpd -g -O2 -O2 -g -march=i386
-mcpu=i686 -pthread -DNO_DBM_REWRITEMAP -g -O2 -DLINUX=2 -D_REENTRANT
-D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -I
/opt/IBMJava2-131/include -I /opt/IBMJava2-131/include/ -c jk_sockbuf.c
mode=compile gcc -I/usr/include/httpd -g -O2 -O2 -g -march=i386
-mcpu=i686 -pthread -DNO_DBM_REWRITEMAP -g -O2 -DLINUX=2 -D_REENTRANT
-D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -I
/opt/IBMJava2-131/include -I /opt/IBMJava2-131/include/ -c jk_map.c
...
-O2 -g -march=i386 -mcpu=i686 -pthread -DNO_DBM_REWRITEMAP -g -O2
-pthread -DNO_DBM_REWRITEMAP -DLINUX=2 -D_REENTRANT -D_XOPEN_SOURCE=500
-D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -c ../common/jk_ajp_common.c
/bin/sh /usr/bin/libtool --silent --mode=compile gcc
-I/usr/include/httpd -g -O2 -DUSE_APACHE_MD5 -I ../common -I
/opt/IBMJava2-131/include -I /opt/IBMJava2-131/include/unix -DLINUX=2
-D_REENTRANT -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE
-D_GNU_SOURCE -O2 -g -march=i386 -mcpu=i686 -pthread -DNO_DBM_REWRITEMAP
-g -O2 -pthread -DNO_DBM_REWRITEMAP -DLINUX=2 -D_REENTRANT
-D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -c
../common/jk_context.c
/bin/sh /usr/bin/libtool --silent --mode=link gcc -I/usr/include/httpd
-g -O2 -DUSE_APACHE_MD5 -I ../common -I /opt/IBMJava2-131/include -I
/opt/IBMJava2-131/include/unix -DLINUX=2 -D_REENTRANT
-D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -O2 -g
-march=i386 -mcpu=i686 -pthread -DNO_DBM_REWRITEMAP -g -O2 -pthread
-DNO_DBM_REWRITEMAP -DLINUX=2 -D_REENTRANT -D_XOPEN_SOURCE=500
-D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -o mod_jk.la -module -rpath
/usr/lib/httpd/modules -avoid-version mod_jk.lo
../common/jk_ajp12_worker.lo ../common/jk_connect.lo
../common/jk_msg_buff.lo ../common/jk_util.lo ../common/jk_ajp13.lo
../common/jk_pool.lo ../common/jk_worker.lo ../common/jk_ajp13_worker.lo
../common/jk_lb_worker.lo ../common/jk_sockbuf.lo ../common/jk_map.lo
../common/jk_uri_worker_map.lo ../common/jk_ajp14.lo
../common/jk_ajp14_worker.lo ../common/jk_md5.lo
../common/jk_ajp_common.lo ../common/jk_context.lo
gcc: ../common/jk_ajp12_worker.lo: No such file or directory
gcc: ../common/jk_connect.lo: No such file or directory
gcc: ../common/jk_msg_buff.lo: No such file or directory
gcc: ../common/jk_util.lo: No such file or directory
gcc: ../common/jk_ajp13.lo: No such file or directory
gcc: ../common/jk_pool.lo: No such file or directory
gcc: ../common/jk_worker.lo: No such file or directory
gcc: ../common/jk_ajp13_worker.lo: No such file or directory
gcc: ../common/jk_lb_worker.lo: No such file or directory
gcc: ../common/jk_sockbuf.lo: No such file or directory
gcc: ../common/jk_map.lo: No such file or directory
gcc: ../common/jk_uri_worker_map.lo: No such file or directory
gcc: ../common/jk_ajp14.lo: No such file or directory
gcc: ../common/jk_ajp14_worker.lo: No such file or directory
gcc: ../common/jk_md5.lo: No such file or directory
gcc: ../common/jk_ajp_common.lo: No such file or directory
gcc: ../common/jk_context.lo: No such file or directory
make[1]: *** [mod_jk.la] Error 1
make[1]: Leaving directory
`/home/admin/jakarta-tomcat-connectors-jk-1.2.4-src/jk/native/apache-2.0'
make: *** [all-recursive] Error 1
It seems we loose the /bin/sh /usr/bin/libtool --silent in the first
part of the build (certainly related to the 'customized' Redhat apxs and
the strange error line 261 of APXS (attached).
Re: [ANN] Apache Tomcat mod_jk 1.2.4 Web Server Connector released
Posted by jean-frederic clere <jf...@fujitsu-siemens.com>.
Henri Gomez wrote:
> Glenn Nielsen wrote:
>
>> The Tomcat team has released version 1.2.4 of the Tomcat mod_jk web
>> server connector.
>>
>> This version fixes a number of minor bugs and ports all features from
>> the Apache 1.3 version
>> to the Apache 2 version of mod_jk 1.2.
>>
>> See the file CHANGES.txt in the source distribution for a complete
>> list of changes.
>>
>> The source distribution is available at:
>>
>> http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.4/src/
>>
>>
>> Binary distributions for different web servers and operating systems
>> will become available
>> in the next week for download at:
>>
>> http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.4/bin/
>>
>>
>> Linux RPM's can be found when they become available at:
>>
>> http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.4/rpms/
>
>
>
> There is no more RPM for Linux, since there is just too many Linux
> distributions todays with too many differents level of :
>
> - Apache 1.3, Apache 2.0, GLIBC, Apache layout and Apache config.
>
>> Documentation for the release is available at:
>>
>> http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.4/doc/
>
>
>
> BTW, the JF-Clere fix in configure.in to use the libtool in Apache 2.0
> case, don't works with Redhat 8.0/9.0 where there is an Apache 2.0.40
> with post 2.0.40 security fixes.
And what is the error? It works with a vanilla Apache-2.0.40.
>
> For such case, what about adding a --with-libtool to specify WHICH
> LIBTOOL to be used (and as such could be use in place of Apache post
> 2.0.45 libtool)
>
> Regards
>
> BTW, iSeries binaries will be uploaded today
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: [5.0.3] Tag soon, 5.0 release plan
Posted by Remy Maucherat <re...@apache.org>.
Tim Funk wrote:
> +1. Sounds good. I'll try to keep track of common topics from
> tomcat-user land to indicate what documentation areas need most help.
>
> A feature I want to add (post tagging and haven't started yet) is
> integrating lucene into the tomcat-docs.
Done in a convincing way, that looks like a very good idea :)
Remy
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: [5.0.3] Tag soon, 5.0 release plan
Posted by Tim Funk <fu...@joedog.org>.
+1. Sounds good. I'll try to keep track of common topics from tomcat-user
land to indicate what documentation areas need most help.
A feature I want to add (post tagging and haven't started yet) is integrating
lucene into the tomcat-docs.
-Tim
Remy Maucherat wrote:
> Hi,
>
> I am nearly done with the features I wanted to add for 5.0.3 (and the
> changelog is pretty big), so I plan to tag 5.0.3 at the end of this week
> (friday, but more likely saturday).
>
> I don't know if there are some more major features that people would
> like to see in 5.0.x (if that's the case, please add items to the status
> page in the docs), but as far as I am concerned, 5.0.x is nearly feature
> complete. What's missing is better docs, and lots of tweaks and fixes.
>
> Because of that, I plan to write a release plan for Tomcat 5.0.x,
> outlining a tentative schedule and objective for betas and eventually a
> stable release (which as a reminder won't happen until the new specs are
> final).
>
> Note: the rationale behind the "no final before the specs" is beacause:
> - if the specs change and modify a behavior that was introduced in the
> new specs, we'd have to break our API / behavior, which is not really
> acceptable
> - it's a chicken and egg problem: if there's no spec, people will
> (likely) prefer using Tomcat 4.1.x, and so Tomcat 5.0.x wouldn't get
> enough testing to warrant the "stable" label
> Given the last point, the best IMO would be to make a "RC"-like release
> when the specs are released, followed a few weeks later by a final.
>
> Comments ?
>
> Remy
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
[5.0.3] Tag soon, 5.0 release plan
Posted by Remy Maucherat <re...@apache.org>.
Hi,
I am nearly done with the features I wanted to add for 5.0.3 (and the
changelog is pretty big), so I plan to tag 5.0.3 at the end of this week
(friday, but more likely saturday).
I don't know if there are some more major features that people would
like to see in 5.0.x (if that's the case, please add items to the status
page in the docs), but as far as I am concerned, 5.0.x is nearly feature
complete. What's missing is better docs, and lots of tweaks and fixes.
Because of that, I plan to write a release plan for Tomcat 5.0.x,
outlining a tentative schedule and objective for betas and eventually a
stable release (which as a reminder won't happen until the new specs are
final).
Note: the rationale behind the "no final before the specs" is beacause:
- if the specs change and modify a behavior that was introduced in the
new specs, we'd have to break our API / behavior, which is not really
acceptable
- it's a chicken and egg problem: if there's no spec, people will
(likely) prefer using Tomcat 4.1.x, and so Tomcat 5.0.x wouldn't get
enough testing to warrant the "stable" label
Given the last point, the best IMO would be to make a "RC"-like release
when the specs are released, followed a few weeks later by a final.
Comments ?
Remy
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: [ANN] Apache Tomcat mod_jk 1.2.4 Web Server Connector released
Posted by Henri Gomez <hg...@apache.org>.
Glenn Nielsen wrote:
> The Tomcat team has released version 1.2.4 of the Tomcat mod_jk web
> server connector.
>
> This version fixes a number of minor bugs and ports all features from
> the Apache 1.3 version
> to the Apache 2 version of mod_jk 1.2.
>
> See the file CHANGES.txt in the source distribution for a complete list
> of changes.
>
> The source distribution is available at:
>
> http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.4/src/
>
>
> Binary distributions for different web servers and operating systems
> will become available
> in the next week for download at:
>
> http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.4/bin/
>
>
> Linux RPM's can be found when they become available at:
>
> http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.4/rpms/
There is no more RPM for Linux, since there is just too many Linux
distributions todays with too many differents level of :
- Apache 1.3, Apache 2.0, GLIBC, Apache layout and Apache config.
> Documentation for the release is available at:
>
> http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.4/doc/
BTW, the JF-Clere fix in configure.in to use the libtool in Apache 2.0
case, don't works with Redhat 8.0/9.0 where there is an Apache 2.0.40
with post 2.0.40 security fixes.
For such case, what about adding a --with-libtool to specify WHICH
LIBTOOL to be used (and as such could be use in place of Apache post
2.0.45 libtool)
Regards
BTW, iSeries binaries will be uploaded today
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org