problems building on HP-UX with gcc, static libraries, dynamic apache module

[ma...@zeelandnet.nl]

I want to use subversion as apache modules on a HP-UX 11.11 machine.

In order to make that happen I need subversion's static libraries
(and all other relevant libraries static as well) and then make the
svn apache2 dso modules that have all those relevant libraries
linked in as well as libgcc such that at start up time I won't get
complaints (and an abort) about missing symbols. 

In principle this should work - it's how php for example works too.
But how can I make this happen with subversion? I have tried many 
variations on configure with all kinds of options. But I always end
up either with dso modules that are linked to shared libraries - 
which I don't want because it doesn't work - or with static modules
(which I don't want at all, and, in order to be used also have to be
linked with other libraries).

Does anyone have some insight on this problem?


Thanks,

Mart





---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: problems building on HP-UX with gcc, static libraries, dynamic apache module

[Branko Čibej <br...@xbc.nu>]

martr@zeelandnet.nl wrote:

>I want to use subversion as apache modules on a HP-UX 11.11 machine.
>
>In order to make that happen I need subversion's static libraries
>(and all other relevant libraries static as well) and then make the
>svn apache2 dso modules that have all those relevant libraries
>linked in as well as libgcc such that at start up time I won't get
>complaints (and an abort) about missing symbols. 
>
>In principle this should work - it's how php for example works too.
>But how can I make this happen with subversion? I have tried many 
>variations on configure with all kinds of options. But I always end
>up either with dso modules that are linked to shared libraries - 
>which I don't want because it doesn't work - or with static modules
>(which I don't want at all, and, in order to be used also have to be
>linked with other libraries).
>
>Does anyone have some insight on this problem?
>  
>
AFAIK our build simply doesn't support this configuration. Basically we 
have three ways of building on Unix:

    * shared: all SVN libraries are shared libs, Apache modules link to
      the shared libs
    * static: all SVN libraries are static libs, Apache modules don't
      get built at all (there seemed to have been support for
      --static-apache at some time, but it's probably gone to pot)
    * --enable-all-static: supposed to build completely statically
      linked SVN binaries, but it doesn't work on HP-UX because some of
      the system libraries only come in shared versions. Of course,
      Apache modules don't get build here, either.

I suppose someone could change the static build to produce loadable 
statically linkesd Apache modules.

-- Brane


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org