Date: Sat, 16 May 2009 10:15:38 GMT From: Mark <admin@asarian-host.net> To: <freebsd-questions@freebsd.org> Subject: RE: php5 pcre Message-ID: <200905161015.n4GAFbsF016555@asarian-host.net> In-Reply-To: <200905161158.18317.mel.flynn%2Bfbsd.questions@mailing.thruhere.net> References: <4A0C27A1.2020108@fxclub.org> <4A0D292D.4030508@fxclub.org> <200905161158.18317.mel.flynn%2Bfbsd.questions@mailing.thruhere.net>
next in thread | previous in thread | raw e-mail | index | archive | help
-----Original Message----- From: Mel Flynn [mailto:mel.flynn+fbsd.questions@mailing.thruhere.net] Sent: zaterdag 16 mei 2009 11:59 To: freebsd-questions@freebsd.org Cc: Mark Subject: Re: php5 pcre > I thought I was the only one this had happened to. :) In my case I > resolved it by going into the pcre directory itself and build it > from there. > That don't make sense. Any chance you had BUNDLED_PCRE selected and decided > to untick it in the config dialog? If this really is all you did, then > maybe extension ordering is the culprit. Move pcre.so in extension.ini upwards > and see if the bug resurfaces. No, I didn't untick anything. I saw the 'undefined symbol' in my Apache log, and decided to recompile pcre.so. Then the error went away. I had this happen, 2 years or so ago, with mysql extension for PHP4, too: the second time compiling it the (other types of errors) disappeared. That's actually not all that strange, really, because it's entirely plausible that sometimes, compiling an extension the first time, it is dependent on something that wasn't built yet the first around. - Mark
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200905161015.n4GAFbsF016555>