By xicanista on

After installing the search module I tested it out and got the following error message, "Compilation failed: this version of PCRE is not compiled with PCRE_UTF8 support at offset 0." I searched Drupal's support and others have had the same problem. I found that there were two basic responses: Re-install php because newer versions enable UTF8 support for PCRE or re-compile PCRE.

So I did my own sleuthing around my machine. I am running 4.3.10 and UTF8 support is enabled. I ran a nice script (./pcretest -C) and discovered I am running version 5.0 *without* UTF8 support enabled. At this point it looks like my problem might be solved by re-compiling PCRE.

I looked at the PCRE documenation at http://www.pcre.org/ and my best guess right now is I need to uninstall the current pcre installation, configure the source file using "./configure --enable-utf8" from the source directory, run "make" to install the libraries, and then test the installation.

Has anyone else had this problem? Is this how you re-compiled pcre? Can you give me any heads up on potential pitfalls?

I don't know exactly what else on my machine is relying on PCRE right now, so I am a bit gun-shy.

Comments

xicanista’s picture

xicanista commented

I found the documentation on pcre unnecessarily cryptic, but that is how it is for a lot of things, so I suppose I should not complain.

My VPS (virtual private server) has a port system that included source code that would enable utf-8 support for pcre. After uninstalling the original pcre installation (see 'man vuninstall'), I went to the source directory to run make and then install the utf-8 enabled pcre code.

I verified pcre had utf-8 enabled by going to the pcre directory and running ./pcretest -C It gave me:
PCRE version 6.3 15-Aug-2005
Compiled with
UTF-8 support
Unicode properties support
Newline character is LF
Internal link size = 2
POSIX malloc threshold = 10
Default match limit = 10000000
Match recursion uses stack

I also verified by trying to do a search on my website. When I entered a search term instead of getting the 'pcre utf-8 support not enabled' message it simply said no results were found.

No results were found because I did not have caching enabled on my site. Enabling it is easy to do. After I logged on to my site I went to administer>settings and then clicked on the enable caching radio button.

I ran a bunch of searches and it is coming up with what I would expect.

DrLou’s picture

DrLou commented

xicanista:

A rebuild of PCRE did not fix this error on Solaris 10 - SPARC... Yes, we were sure to compile with the UTF8 support...

We have rebuilt both v4.5 and v6.6 of PCRE, both of which with both UTF8 and Unicode Properties Support. These both reported PCRE lib version (in phpinfo) of 3.9 - (02 Jan 2002). Our issue was slightly different to yours (apparently), in that our php compile pointed to these libs: --with-pcre-regex=/usr/local

However, the only way to 'fix' this was to compile PHP with its own internal implementation of PCRE; ie, remove the --with-pcre-regex option from php's compile step. This results in a PCRE lib version of 6.2 (01-Aug-2005)!!!

Spent a few hours on this one - hope it helps someone...

Lou

broncos88’s picture

broncos88 commented

how do i remove --with-pcre-regex?