Re: mod_jk vs. statically linked Apache
It's something I'm interested in... do tell! THe only reason I have DSO enabled currently is for mod_jk.so (I have php,ssl, and all others statically compiled for speed increase) David. At 02:15 PM 12/2/00 +1100, you wrote: I've noticed that there aren't any instructions about compiling and then statically linking mod_jk.so into Apache (mod_jk HOWTO from Tomcat 3.2). Is this intentional (ie. do you want to move people away from doing that) or is it just missing because most people prefer DSO? I've been able to compile and statically link mod_jk.o into Apache (on RedHat Linux 7.0), but it requires some fiddling. Would this be something others would like to know about? Bojan David Bussenschutt Email: [EMAIL PROTECTED] Senior Computing Support Officer Systems Administrator/Programmer Location: Griffith University. Information Technology Services Brisbane Qld. Aust. (TEN bldg. rm 1.33) Ph: (07)38757079
Re: mod_jk vs. statically linked Apache
Bojan Smojver wrote: I've noticed that there aren't any instructions about compiling and then statically linking mod_jk.so into Apache (mod_jk HOWTO from Tomcat 3.2). Is this intentional (ie. do you want to move people away from doing that) or is it just missing because most people prefer DSO? I've been able to compile and statically link mod_jk.o into Apache (on RedHat Linux 7.0), but it requires some fiddling. Would this be something others would like to know about? Static linking was not an intended supported configuration, so there was no need to document it. The fact that it works at all means you are lucky. Bojan Craig McClanahan
Re: mod_jk vs. statically linked Apache
I didn't actually say that the configuration works. It'll be some time before I know that for sure. But it does compile and link :-) If I understand correctly, DSO is described in Apache INSTALL file as optional. I have seen references in the jk code to dl related functions (and actually -ldl needs to be specified to link mod_jk into Apache successfully) and now I'm not sure if statically linking the module would affect it (and my limited knowledge suggests it shouldn't, but I could be dead wrong here). If it's not too much trouble, would you be able to explain why (technically) static linking isn't supported in mod_jk before I waste too much time on testing. Regards, Bojan Static linking was not an intended supported configuration, so there was no need to document it. The fact that it works at all means you are lucky. Craig McClanahan
mod_jk vs. statically linked Apache
I've noticed that there aren't any instructions about compiling and then statically linking mod_jk.so into Apache (mod_jk HOWTO from Tomcat 3.2). Is this intentional (ie. do you want to move people away from doing that) or is it just missing because most people prefer DSO? I've been able to compile and statically link mod_jk.o into Apache (on RedHat Linux 7.0), but it requires some fiddling. Would this be something others would like to know about? Bojan
Re: mod_jk vs. statically linked Apache (under AIX 4.3.3)
Bojan Smojver wrote: I've noticed that there aren't any instructions about compiling and then statically linking mod_jk.so into Apache (mod_jk HOWTO from Tomcat 3.2). Is this intentional (ie. do you want to move people away from doing that) or is it just missing because most people prefer DSO? I've been able to compile and statically link mod_jk.o into Apache (on RedHat Linux 7.0), but it requires some fiddling. Would this be something others would like to know about? Bojan I have done the same. Building mod_jk statically linked with apache under AIX 4.3.3.25. Just to let to you known that it works fine... Franco Fiorese
