[development] PHP5 going forward

Walt Daniels wdlists at optonline.net
Mon May 28 15:42:11 UTC 2007


Perhaps this tells us something about our ongoing discussion about whether
to allow foreign code in our CVS. Clearly PHP has allowed it and has a
version which is necessary for successful use. TinyMCE is likely to have
similar properties if we have a slightly customized version in the Drupal
CVS, namely someone who installs for the public repository is likely to have
problems.  This is an opportunity to do better and have a private copy and
do enough version checking to insure that it is the one being used and
complain with an obvious error message instead of an obscure failure
message. 

-----Original Message-----
From: development-bounces at drupal.org [mailto:development-bounces at drupal.org]
On Behalf Of Earnie Boyd
Sent: Monday, May 28, 2007 11:15 AM
To: development at drupal.org
Subject: Re: [development] PHP5 going forward

Quoting Earnie Boyd <earnie at users.sourceforge.net>:

> Quoting Earnie Boyd <earnie at users.sourceforge.net>:
>
>> Quoting Gordon Heydon <gordon at heydon.com.au>:
>>
>>> Hi,
>>>
>>> I like this idea, and getting as many of the major PHP projects 
>>> involved as possible would be the best way to go.
>>>
>
> Does anyone have a working configuration for Apache-2.2, PHP-5.2.x and 
> Drupal?  I've been trying but I keep getting an issue with PCRE and 
> UNICODE as I have previously mentioned.  Unless this issue is 
> addressed then pushing for PHP5 is a mute point.
>

Thanks to private conversation with Khalid and Wim I was able to determine
the issue.  PHP comes with its own version of PCRE and I had overridden the
use of that version with --with-pcre-regex=/usr/local.  
After removing that configuration item the issue has been resolved.

Earnie


--
No virus found in this incoming message.
Checked by AVG Free Edition. 
Version: 7.5.472 / Virus Database: 269.8.1/822 - Release Date: 5/28/2007
11:40 AM




More information about the development mailing list