Mark wrote:

> -----Original Message-----
> From: Mel Flynn [mailto:mel.flynn+fbsd.questi...@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.
> 

This kind of thing may happen when ports get reorganized. Used to be PCRE 
was either built in or you could build it against the other pcre library. 
Sometime recently it was split out into it's own extension port. I've
had portupgrade barf a time or two when these reorganizations have 
happened in the past. Manual intervention/rebuild was needed to fix
things up.

-Mike
 



_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Reply via email to