On Sun, Feb 27, 2005, Jim Helm 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.
Hi. Look at this: http://marc.theaimsgroup.com/?l=openpkg-dev&m=110633840325505&w=2 http://marc.theaimsgroup.com/?l=openpkg-dev&m=110633850330396&w=2 http://marc.theaimsgroup.com/?l=openpkg-dev&m=110633762502643&w=2 One has to build apache2 with shared core, in the first place. The PHP stuff works for me. Well, mostly. When i use some options (e.g. with_pdflib, with_gd, ... cannot remember more, because it was some time ago) apache2 crashes with "unresolved symbol" or just "silently" with a segfault. Did not investigate further, because i only need this stuff later. Also, when one does not make sure, that the shared library is only built from PIC code, it could be less efficient than a statically linked binary. The code of a statically linked binary is fully sharable. When a shared library is loaded that has references that need relocation, it will be necessary to copy pages. This costs time and space. (mk) -- Matthias Kurz; Fuldastr. 3; D-28199 Bremen; VOICE +49 421 53 600 47 >> Im prämotorischen Cortex kann jeder ein Held sein. (bdw) << ______________________________________________________________________ The OpenPKG Project www.openpkg.org Developer Communication List openpkg-dev@openpkg.org
