RE: [mod-security-users] using libtool for Apache 2 mod_security installation

[Jeff G. <jg...@ad...>]

Hi Ivan,
  I did happen to figure out that there's no point in doing it statically
and went ahead and used the dso method. Thanks
Jeff

-----Original Message-----
From: Ivan Ristic [mailto:iv...@we...] 
Sent: Saturday, November 29, 2003 6:52 PM
To: jg...@ad...
Cc: mod...@li...
Subject: Re: [mod-security-users] using libtool for Apache 2 mod_security
installation

Jeff Gillin wrote:
> Hi,
> 
> I'm trying to get mod_security compiled into my Apache 2.

   Statically, I assume? Because compiling it as a dynamic module
   is very easy :)


> The notes say to cp mod_security.c to the modules/mappers/ directory 
> and edit the modules.mk file, but the compiler make utility complains 
> saying "no rule to make target modules/mappers/mod_security_la"
> 
>    I did some reading and learned about the libtool utility (to some 
> extent).
> 
>    I was able to figure out how to create the .o and .lo files, but I'm 
> not sure about the process to create the .la file. Could you please post 
> the syntax for this. What confuses me the most is what to put for the 
> -rpath option.

   I don't know how to use libtool either. In fact, I know less about it
   than you do. Because of that I keep mod_security in a single file and
   it is very easy to compile and install.

   No one has really explained how to statically compile a module, what
   I described in the manual is a hack.

-- 
ModSecurity (http://www.modsecurity.org)
[ Open source IDS for Web applications ]