Re: Error compiling mod_webapp for debian Linux

[Georg Huettenegger]

hi,

for some reason i do not understand the build mechanism does not build a
libwebapp.so shared library. if one does do this by and (and possibly also
building a mod_webapp.so by hand) everything does work fine for me.

apparently the build system still needs some improvement and for the
moment it is possible to build shared libraries by hand.

bye,
 georg

On Thu, 18 Apr 2002, Emil Olovsson wrote:

> I am trying to build mod_webapp for apache 2.0.35 and Tomcat 4.0.3
> 
> I followed the instructions in the README file, and all was fine until I
> issued make. Then I got the following error. Can someone please tell me what
> is wrong.
> 
> ...
> make[1]: Entering directory "apache-2.0"
> make[1]: Invoking "make  build"
> make[2]: Entering directory
> `/opt/webapp/jakarta-tomcat-connectors/webapp/apache-2.0'
> Compiling and Linking Apache 2.0 WebApp Module
> /opt/apache2*/bin/apxs -I../include -c -L ../lib -lwebapp mod_webapp.c
> /opt/apache2.0.35/build/libtool --silent --mode=compile
> c   -DAP_HAVE_DESIGNATED_INITIALIZER -DLINUX=2 -D_RE
> ENTRANT -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -g -O2 -pthread -I/
> opt/apache2.0.35/include -I../incl
> ude  -c -o mod_webapp.lo mod_webapp.c && touch mod_webapp.slo
> mod_webapp.c: In function `wam_invoke':
> mod_webapp.c:482: warning: initialization discards qualifiers from pointer
> target type
> /opt/apache2.0.35/build/libtool --silent --mode=link gcc -o
> mod_webapp.la -rpath /opt/apache2.0.35/modules -mo
> dule -avoid-version -I../include  -L../lib -lwebapp  mod_webapp.lo
> 
> 
> *** Warning: This library needs some functionality provided by -lwebapp.
> *** I have the capability to make that library automatically link in when
> *** you link to this library.  But I can only do this if you have a
> *** shared version of the library, which you do not appear to have.
> 
> *** Warning: libtool could not satisfy all declared inter-library
> *** dependencies of module mod_webapp.  Therefore, libtool will create
> *** a static module, that should work as long as the dlopening
> *** application is linked with the -dlopen flag.
> 
> 
> --
> To unsubscribe:   
> For additional commands: 
> Troubles with the list: 
> 


--
To unsubscribe:   
For additional commands: 
Troubles with the list: 

Re: Error compiling mod_webapp for debian Linux

[Jeffrey Bonevich]

Georg -

You may have seen the other issue (with undefined symbol wa_pool) 
mentioned.  Did you encounter this issue?  Was it not an issue on Solaris?

jeff

Georg Huettenegger wrote:

> hi,
> 
> for some reason i do not understand the build mechanism does not build a
> libwebapp.so shared library. if one does do this by and (and possibly also
> building a mod_webapp.so by hand) everything does work fine for me.
> 
> apparently the build system still needs some improvement and for the
> moment it is possible to build shared libraries by hand.  
> 
> bye,
>  georg
> 
> On Thu, 18 Apr 2002, Emil Olovsson wrote:
> 
> 
>>I am trying to build mod_webapp for apache 2.0.35 and Tomcat 4.0.3
>>
>>I followed the instructions in the README file, and all was fine until I
>>issued make. Then I got the following error. Can someone please tell me what
>>is wrong.
>>
>>...
>>make[1]: Entering directory "apache-2.0"
>>make[1]: Invoking "make  build"
>>make[2]: Entering directory
>>`/opt/webapp/jakarta-tomcat-connectors/webapp/apache-2.0'
>>Compiling and Linking Apache 2.0 WebApp Module
>>/opt/apache2*/bin/apxs -I../include -c -L ../lib -lwebapp mod_webapp.c
>>/opt/apache2.0.35/build/libtool --silent --mode=compile
>>c   -DAP_HAVE_DESIGNATED_INITIALIZER -DLINUX=2 -D_RE
>>ENTRANT -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -g -O2 -pthread -I/
>>opt/apache2.0.35/include -I../incl
>>ude  -c -o mod_webapp.lo mod_webapp.c && touch mod_webapp.slo
>>mod_webapp.c: In function `wam_invoke':
>>mod_webapp.c:482: warning: initialization discards qualifiers from pointer
>>target type
>>/opt/apache2.0.35/build/libtool --silent --mode=link gcc -o
>>mod_webapp.la -rpath /opt/apache2.0.35/modules -mo
>>dule -avoid-version -I../include  -L../lib -lwebapp  mod_webapp.lo
>>
>>
>>*** Warning: This library needs some functionality provided by -lwebapp.
>>*** I have the capability to make that library automatically link in when
>>*** you link to this library.  But I can only do this if you have a
>>*** shared version of the library, which you do not appear to have.
>>
>>*** Warning: libtool could not satisfy all declared inter-library
>>*** dependencies of module mod_webapp.  Therefore, libtool will create
>>*** a static module, that should work as long as the dlopening
>>*** application is linked with the -dlopen flag.
>>
>>
>>--
>>To unsubscribe:   
>>For additional commands: 
>>Troubles with the list: 
>>
> 
> 
> --
> To unsubscribe:   
> For additional commands: 
> Troubles with the list: 
> 
> 
> 


-- 
Jeffrey Bonevich
Ann Arbor, Michigan
[EMAIL PROTECTED]
http://www.bonevich.com

Hwæt! Wë Gär-Dena   in geär-dagum,
peod-cyninga,   prym gefrünon,
hü ða aepelingas   ellen fremedon!


--
To unsubscribe:   
For additional commands: 
Troubles with the list: 

Re: Error compiling mod_webapp for debian Linux

[Jeffrey Bonevich]

Exellent!

Georg - this worked beautifully.  Thank you very much!

For purposes of recording this on the user group so that others may 
benefit (if they bother to check first that is ;-> ), here is exactly 
what I did:

#
# Assumptions
# * You have already installed Apache 2.0.35
# * You have downloaded and unpacked the Jakarta Tomcat Connectors
#   source package (jakarta-tomcat-connectors-4.0.2-01-src.tar.gz)
#

#
# Procedure
#
cd ${TOMCAT_CONNECTORS_SRC_HOME}/webapp
chmod +x support/*.sh
./support/buildconf.sh
./configure --with-apxs=/usr/local/apache2/bin/apxs
make

#
# Here is where it gets non-standard
#
cd lib
gcc -shared -o libwebapp.so *.lo
cd ../apache-2.0/
/usr/local/apache2/build/libtool --silent --mode=link \
   gcc -shared -o mod_webapp.so -rpath /usr/local/apache2/modules \
   -module -avoid-version -I../include  -L../lib -lwebapp  mod_webapp.lo
cp mod_webapp.so /usr/local/apache2/modules/
cp ../lib/libwebapp.so /usr/local/apache2/modules/

#
# Add the following to /usr/local/apache2/conf/httpd.conf:
#
# LoadModule webapp_module   modules/mod_webapp.so
#
/usr/local/apache2/bin/apachectl configtest


Wonder if this has been corrected in the CVS source yet?  Maybe worth 
doing some searches on tomcat-dev and poking around in CVS, etc. 
Suppose I will look into that next!

jeff



Georg Huettenegger wrote:

> hi,
> 
> while playing around with mod_jk/mod_webapp/binaries i did get undefined
> symbols (e.g. i tried to issue gcc -shared -o mod_webapp.so mod_webapp.o
> -L../lib -lwebapp in the apache-2.0 directory; the result did not work.
> 
> nevertheless the following steps gave me a working version:
> 
> i just manually compiled a libwebapp.so using:
> 'gcc -o libwebapp.so *.lo' in the lib directory.
> 
> then i used the last line that links together mod_webapp.la in the
> apache-2.0 directory and added -shared before -o and changed the suffix to
> .so from .la. otherwise the line (something with .../libtool --mode=link
> gcc -o )
> 
> after copying mod_webapp.so and libwebapp.so to $APACHE_HOME/modules it
> worked without any problem
> 
> bye,
>  georg
> 
> On Thu, 18 Apr 2002, Jeffrey Bonevich wrote:
> 
> 
>>Georg -
>>
>>You may have seen the other issue (with undefined symbol wa_pool) 
>>mentioned.  Did you encounter this issue?  Was it not an issue on Solaris?
>>
>>jeff
>>
>>Georg Huettenegger wrote:
>>
>>
>>>hi,
>>>
>>>for some reason i do not understand the build mechanism does not build a
>>>libwebapp.so shared library. if one does do this by and (and possibly also
>>>building a mod_webapp.so by hand) everything does work fine for me.
>>>
>>>apparently the build system still needs some improvement and for the
>>>moment it is possible to build shared libraries by hand. 
>>>
>>>bye,
>>> georg
>>>
>>>On Thu, 18 Apr 2002, Emil Olovsson wrote:
>>>
>>>
>>>
I am trying to build mod_webapp for apache 2.0.35 and Tomcat 4.0.3

I followed the instructions in the README file, and all was fine until I
issued make. Then I got the following error. Can someone please tell me what
is wrong.

...
make[1]: Entering directory "apache-2.0"
make[1]: Invoking "make  build"
make[2]: Entering directory
`/opt/webapp/jakarta-tomcat-connectors/webapp/apache-2.0'
Compiling and Linking Apache 2.0 WebApp Module
/opt/apache2*/bin/apxs -I../include -c -L ../lib -lwebapp mod_webapp.c
/opt/apache2.0.35/build/libtool --silent --mode=compile
c   -DAP_HAVE_DESIGNATED_INITIALIZER -DLINUX=2 -D_RE
ENTRANT -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -g -O2 -pthread -I/
opt/apache2.0.35/include -I../incl
ude  -c -o mod_webapp.lo mod_webapp.c && touch mod_webapp.slo
mod_webapp.c: In function `wam_invoke':
mod_webapp.c:482: warning: initialization discards qualifiers from pointer
target type
/opt/apache2.0.35/build/libtool --silent --mode=link gcc -o
mod_webapp.la -rpath /opt/apache2.0.35/modules -mo
dule -avoid-version -I../include  -L../lib -lwebapp  mod_webapp.lo


*** Warning: This library needs some functionality provided by -lwebapp.
*** I have the capability to make that library automatically link in when
*** you link to this library.  But I can only do this if you have a
*** shared version of the library, which you do not appear to have.

*** Warning: libtool could not satisfy all declared inter-library
*** dependencies of module mod_webapp.  Therefore, libtool will create
*** a static module, that should work as long as the dlopening
*** application is linked with the -dlopen flag.


--
To unsubscribe:   
For additional commands: 
Troubles with the list: 

>>>
>>>--
>>>To unsubscribe:   
>>>For additional commands: 
>>>Troubles with the list: 
>>>
>>>
>>>
>>
>>-- 
>>Jeffrey Bonevich
>>An

Re: Error compiling mod_webapp for debian Linux

[Andy Carlisle]

>For purposes of recording this on the user group so that others may 
>benefit (if they bother to check first that is ;-> ), here is exactly 
>what I did:

Thank you, Jeffrey, for posting the steps needed to get mod_webapp built
for Debian. I was able to walk through the steps and (for the first time)
got everything installed. I could not start the httpd server, however, as
the following complaint occurs:

Syntax error on line 126 of /opt/apache-2.0.35/conf/ssl.conf:
Invalid port number (p<1) No "Port" statement found

Line 126 is the first WebAppDeploy statement and it sits in the ssl.conf
file (I want to run the web applications over an SSL connection). Of
course, under apache-2.0.x there is no Port statement as it's been
replaced by Listen. There is a Listen 443 statement in the file. 

Here's some other basic information about my setup:

- using Debian Woody on an H-P NetServer LC 3 (x86)
- compiled mod_webapp from CVS as of this afternoon
- Tomcat 4.0.3

Question: Has anyone got mod_webapp working on a 2.0.35 server with
mod_ssl built in? Is there some trick I'm missing? I'd appreciate any help
anyone could give me. Many thanks.

Andy

P.S.: I've also tried mod_jk, which I can get to run, but soon after it is
started the httpd processes one by one start consuming all of the CPU
power on the system. I can kill the offending processes, but new ones soon
take back over. I had not had this problem with 1.3.24 + mod_ssl + mod_jk.
Again, if someone has an idea on how to make this work, I would very much
appreciate it. At this point I just need something that runs reliably on a
2.0.35 httpd server. Thanks.


--
To unsubscribe:   
For additional commands: 
Troubles with the list: 

Re: Error compiling mod_webapp for debian Linux

[Jeffrey Bonevich]

Andy Carlisle wrote:

>>For purposes of recording this on the user group so that others may 
>>benefit (if they bother to check first that is ;-> ), here is exactly 
>>what I did:
>>
> 
> Thank you, Jeffrey, for posting the steps needed to get mod_webapp built
> for Debian. I was able to walk through the steps and (for the first time)
> got everything installed. I could not start the httpd server, however, as
> the following complaint occurs:
> 
> Syntax error on line 126 of /opt/apache-2.0.35/conf/ssl.conf:
> Invalid port number (p<1) No "Port" statement found


Let me quess: your WebApp* configs are inside a VirtualHost subsection? 
  Two solutions:
(1) move them outside of the VirtualHost to the main config section (and 
make sure you have a Listen directive specifying at least the port #); or
(2) inside the VirtualHost, also define a ServerName with both the host 
and port (e.g. ServerName www.mydomain.com:80)

Both ways worked for me.  #2 is a workaround for an existing bug in the 
mod_webapp code (Bug #4042).


> 
> Line 126 is the first WebAppDeploy statement and it sits in the ssl.conf
> file (I want to run the web applications over an SSL connection). Of
> course, under apache-2.0.x there is no Port statement as it's been
> replaced by Listen. There is a Listen 443 statement in the file. 
> 
> Here's some other basic information about my setup:
> 
> - using Debian Woody on an H-P NetServer LC 3 (x86)
> - compiled mod_webapp from CVS as of this afternoon
> - Tomcat 4.0.3
> 
> Question: Has anyone got mod_webapp working on a 2.0.35 server with
> mod_ssl built in? Is there some trick I'm missing? I'd appreciate any help
> anyone could give me. Many thanks.
> 
> Andy
> 
> P.S.: I've also tried mod_jk, which I can get to run, but soon after it is
> started the httpd processes one by one start consuming all of the CPU
> power on the system. I can kill the offending processes, but new ones soon
> take back over. I had not had this problem with 1.3.24 + mod_ssl + mod_jk.
> Again, if someone has an idea on how to make this work, I would very much
> appreciate it. At this point I just need something that runs reliably on a
> 2.0.35 httpd server. Thanks.
> 
> 
> --
> To unsubscribe:   
> For additional commands: 
> Troubles with the list: 
> 
> 
> 


-- 
Jeffrey Bonevich
Ann Arbor, Michigan
[EMAIL PROTECTED]
http://www.bonevich.com

Hwæt! Wë Gär-Dena   in geär-dagum,
peod-cyninga,   prym gefrünon,
hü ða aepelingas   ellen fremedon!


--
To unsubscribe:   
For additional commands: 
Troubles with the list: 

Re: Error compiling mod_webapp for debian Linux

[Simon Stewart]

On Wed, Apr 24, 2002 at 03:53:34PM -0400, Andy Carlisle wrote:
> >For purposes of recording this on the user group so that others may 
> >benefit (if they bother to check first that is ;-> ), here is exactly 
> >what I did:
> 
> Thank you, Jeffrey, for posting the steps needed to get mod_webapp built
> for Debian. I was able to walk through the steps and (for the first time)
> got everything installed. I could not start the httpd server, however, as
> the following complaint occurs:
> 
> Syntax error on line 126 of /opt/apache-2.0.35/conf/ssl.conf:
> Invalid port number (p<1) No "Port" statement found

You've done the hard part, but if you include the port that apache
should listen on in the ServerName directive, you'll get rid of this
error:

ServerName localhost:80

is what I have in my httpd.conf

Cheers,

Simon

-- 
"We were informed that the user interface was exactly the same as being at
 the desktop, but using our visual senses we detected a somewhat different
 story." --- The Register

--
To unsubscribe:   
For additional commands: 
Troubles with the list: