> What environment are you running in? What were your other configuration > options? Perhaps there's some odd interaction that is causing this.
Windows (32-bit) building PCRE as a DLL.
We have defined a few non-default values in config.h.
PCRE version 8.20 2011-10-21
Compiled with
UTF-8 support
No Unicode properties support
No just-in-time compiler support
Newline sequence is LF
\R matches all Unicode newlines
Internal link size = 2
POSIX malloc threshold = 10
Default match limit = 50000
Default recursion depth limit = 2500
Match recursion uses stack
> The design of the JIT interface is supposed to be such that a program
> does not need to know whether JIT is available or not; dummy functions
> are provided that do nothing when JIT support is not compiled. Something
> has clearly gone wrong with this in your environment. It would be good
> to figure out what it is.
That's where I broke it, thank you. I did not understand that dummy
functions would be provided when SUPPORT_JIT was not defined.
I'm not (yet) using the new JIT functionality so I did not include
pcre_jit_compile.c in the build at all. Thus my unresolved externals.
Adding compilation of pcre_jit_compile.c (as I have since seen stated
in the documentation) does yield a successful build with no alteration
of pcretest.c.
Ah, it turns out that I am the "odd interaction that is causing this".
On the other hand it seems pcretest may currently be the only reason to
use pcre_jit_compile.c with the base library. I'm guessing that may not
hold true in future versions. It's great you've enabled such a large
feature without breaking the core functionality.
