Opened 12 years ago
Closed 12 years ago
#443 closed defect (invalid)
Checking for PCRE JIT support always successful
| Reported by: | Den Ivanov | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | nginx-core | Version: | 1.3.x |
| Keywords: | configure, pcre | Cc: | |
| uname -a: | SunOS unknown 5.10 Generic_148889-03 i86pc i386 i86pc | ||
| nginx -V: | NGINX version 1.4.4. | ||
Description
Checking for PCRE JIT support always successful.
This patch may help:
--- auto/lib/pcre/conf-orig
+++ auto/lib/pcre/conf
@@ -171,6 +171,7 @@
if [ $PCRE = YES ]; then
ngx_feature="PCRE JIT support"
ngx_feature_name="NGX_HAVE_PCRE_JIT"
+ ngx_feature_run=yes
ngx_feature_test="int jit = 0;
pcre_free_study(NULL);
pcre_config(PCRE_CONFIG_JIT, &jit);
PCRE version 8.33, NGINX version 1.4.4.
Change History (3)
comment:1 by , 12 years ago
comment:2 by , 12 years ago
Хорошо, значит это просто косметическая проблема.
Я скомпилировал PCRE без поддержки JIT и удивился, когда увидел
JIT support: found
в выводе configure
comment:3 by , 12 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Ok, closing this as there is no problem.
Note:
See TracTickets
for help on using tickets.

And what's the problem? This check is expected to fail if PCRE JIT related code can't be compiled (in particular, the pcre_config(PCRE_CONFIG_JIT) call). If it can, nginx will use the pcre_config(PCRE_CONFIG_JIT) call at runtime to ask a particular library loaded if PCRE JIT is available.