On 11 Mar 2008, at 12:31, Raphaël HUCK wrote:

>>> * Is it possible to link with an external PCRE lib?
>>
>> Yes, it is. If a libpcre is found, it will not link the internal one.
>
> I've just done it by passing the paths in CFLAGS and LDFLAGS.
>
> cherokee compiled with static modules and external PCRE now takes  
> 243472
> bytes.

Does this size include the cgi handler?

>>> * I've also seen that when configured with
>>>
>>> --enable-static-module=fcgi,file,round_robin
>>>
>>> it shows:
>>>
>>> checking module "file"... static
>>> checking module "fcgi"... static
>>> checking module "cgi"... static
>>> checking module "round_robin"... static
>>>
>>> all the others being dynamic.
>>>
>>> Does enabling "fcgi" statically automatically imply "cgi"
>>> statically?
>>
>> No. Actually, you have just hit a configure.in bug. I'm going to try
>> to figure out how it could be fixed up.
>
> This bug comes from line 1149 of configure.in:
>
>       if echo $use_static_module | grep $mod >/dev/null || echo
> $use_static_module | grep all >/dev/null; then
>
> and more precisely from:
>
>       echo $use_static_module | grep $mod
>
> In my case
>
>       use_static_module="fcgi,file,round_robin"
>
> so
>       echo "fcgi,file,round_robin" | grep cgi
>
> is true.
>
>
> echo $use_static_module | grep -w $mod
>
> fixes the problem ("-w" added to grep).

grep -w is supporter on Linux, Solaris and OS X, so I guess it's ok to  
use it.
Thanks for pointing out the solution. :-)

--
Greetings, alo.

_______________________________________________
Cherokee mailing list
[email protected]
http://cherokee-project.com/cgi-bin/mailman/listinfo/cherokee

Reply via email to