Ok, I compiled apache2 from CURRENT (rather then 2.3 RELEASE which I was using before), and modified it's libtool to allow shared libs, and everything is working now. Specifically, in share/apache2/build/libtool, I set build_libtool_libs=yes.
Since that libtool is only used for apache modules, can I assume it's safe to just leave shared libs enabled? You might want to consider patching apache2's libtool so that 3rd part modules can be added via DSO without changing anything by hand. This one was really going to be a show stopper for using OpenPKG - I can't tell you how grateful I was to find a 1 line fix. I'm evaluating it's possible use to deploy standard tools into an 800+ server production environment. Apache isn't going to be one of them, but I figured if I couldn't do something so basic as to build a 3rd party DSO for apache, I wasn't going to take any chances. Jim On Sun, 27 Feb 2005 17:15:23 -0800, Jim Helm <[EMAIL PROTECTED]> wrote: > Ok, I think I know the answer already, but I had to ask... > > Is it possible to build dso modules using either apache or apache2 > apxs under OpenPKG 2.3? I'd like to use fastcgi under apache2 (or > even apache, if you'd add mod_proxy to the list of with_ options). > But it seems because of your preference for statically linking (which > I agree with) - apxs will only build .a and .la files, which are > useless unless I rebuild apache by hand, which defeats the purpose of > using OpenPKG in the first place. > > If I'm missing something obvious, please, don't hesitate to point it > out, then berate me for it. :) > > Thanks, > > Jim > ______________________________________________________________________ The OpenPKG Project www.openpkg.org Developer Communication List openpkg-dev@openpkg.org
