[PATCH] Configure: added new option --with-pcre-conf-opt=OPTIONS.
mdounin at mdounin.ru
Wed Dec 11 16:08:57 UTC 2013
On Wed, Dec 11, 2013 at 07:01:38AM -0800, rand at sent.com wrote:
> > As you already have libpcre installed, you don't need nginx to
> > build it (and you don't need sources). If nginx isn't able to
> > find the pcre itself, use something like this to tell where to
> > look for headers and library:
> > ./configure --with-cc-opt="-I/usr/local/include" \
> > --with-ld-opt="-L/usr/local/lib64"
> That's easy enough, then.
> I've built pcre, separately, with pcre-jit support enabled. Is that
> sufficient for nginx to use pcre-jit? I suspect that it is, and that
> "--with-pcrejit" is also simply a build-pcre-in-nginx flag?
The "--with-pcre-jit" configure option is documented to mean:
$ ./configure --help | grep jit
--with-pcre-jit build PCRE with JIT compilation support
That is, it's only applies when nginx is going to build PCRE
To actually activate JIT compilation, you'll also need to use
pcre_jit directive, see nginx.org/r/pcre_jit.
Note that use of PCRE JIT may actually result in lower performance
(due to more memory used to compiled regular expressions, and less
effective CPU cache as a result), enabling it unconditionally may
not be a good idea.
More information about the nginx-devel