Re: mod-security-users Digest, Vol 6, Issue 22

This part is also confusing, i have no idea which PCRE apache is 
compiled with, the production server seems to be compiled via source, 
the dev server is via freebsd ports. One has its apache prefix in 
/www/apache the other is /usr/local so where exactly do i put the top 
directory /usr/local/share/apache2 only has a build directory in it.


If you have compiled Apache yourself you might experience problems 
compiling ModSecurity against PCRE. This is because Apache bundles PCRE 
but this library is also typically provided by the operating system. I 
would expect most (all) vendor-packaged Apache distributions to be 
configured to use an external PCRE library (so this should not be a 
problem).

You want to avoid Apache using the bundled PCRE library and ModSecurity 
linking against the one provided by the operating system. The easiest 
way to do this is to compile Apache against the PCRE library provided by 
the operating system (or you can compile it against the latest PCRE 
version you downloaded from the main PCRE distribution site). You can do 
this at configure time using the --with-pcre switch. If you are not in a 
position to recompile Apache then, to compile ModSecurity successfully, 
you'd still need to have access to the bundled PCRE headers (they are 
available only in the Apache source code) and change the include path 
for ModSecurity (as you did in step 7 above) to point to them.

Do note that if your Apache is using an external PCRE library you can 
compile ModSecurity with WITH_PCRE_STUDY defined, which would possibly 
give you a slight performance edge in regular expression processing.



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV