We finally got tomcat 3.2 + apache + mod_jk setup and running under HPUX11.
>From what we had to do i'm not sure if it had been tested under this
environment or not. Our setup is using the binary 3.2 release, but the work
below had to be done on the source distribution of tomcat. 

the apxs line we used : 
------
/usr/local/apache/bin/apxs -o mod_jk.so -DHPUX11 -I../jk
-I/opt/java1.2/include -I/opt/java1.2/include/hp-ux -c *.c ../jk/*.c
------

1.) Edited the file <path to tomcat src>/src/native/jk/jk_global.h
------jk_global.h--------------
/* <sys/select> */
-----------------------------------
commented out the above section, due to the fact that HP's select is now in
<sys/time>. This line was in the if statement checking for netware. 

- otherwise upon running apxs would die with compile errors. 

2.) Edited file <path to tomcat src>/src/native/jk/jk_pool.h

- Added code to following section, 

HPUX11,HPUX, or HPUX10 are not checked for, AND there is no else for a
default value, so we added an elif for HP to defiine the type of
jk_pool_atom and also a default value. (btw, shouldn't they all just be set
to long and just check for MS to set it on it's own?)

--------------------jk_pool.h---------------------------
#elif(HPUX11) a
        #elif defined(HPUX11)
    typedef long long   jk_pool_atom_t;
#else
    typedef long long   jk_pool_atom_t;
#endif
-------------------------------------------------------------

after making these changes the above apxs command was used, mod_jk compiled,
and now apache + tomcat3.2+ mod+jk are running fine on our HPUX11 box..  (as
per following all the other directions in the great docs included)

hope this helps someone else.

thanks, 

-charlie.

p.s.  I'm not subscribed to the dev list any longer, not sure if you want
this passed on to them or not. 



--------------------------------------------------
Charles Fulton
Computational Chemistry
Union Carbide Corp. 
[EMAIL PROTECTED]
304-747-3175

Reply via email to