RE: [PHP-DEV] Symbol clash between Recode and MySQL extensions

2005-02-13 Thread Derick Rethans
On Sun, 13 Feb 2005 [EMAIL PROTECTED] wrote: > I was thinking that rather than linking against the recode library (and > implicitly importing all symbols within it), we could instead dlopen() it, > and use dlsym() to import only symbols we want. Looking at the recode > extension, theres only a han

RE: [PHP-DEV] Symbol clash between Recode and MySQL extensions

2005-02-12 Thread php
> -Original Message- > From: Jani Taskinen [mailto:[EMAIL PROTECTED] > Sent: Sunday, 13 February 2005 5:25 PM > To: [EMAIL PROTECTED] > Cc: internals@lists.php.net > Subject: Re: [PHP-DEV] Symbol clash between Recode and MySQL > extensions > > > >

Re: [PHP-DEV] Symbol clash between Recode and MySQL extensions

2005-02-12 Thread Jani Taskinen
Also documented in the manual: http://www.php.net/recode Just blame recode and mysql. They both should namespace protect their functions. :) If you build the extensions as shared ones, then you can always make sure in php.ini that you load recode.so first.. --Jani On S

Re: [PHP-DEV] Symbol clash between Recode and MySQL extensions

2005-02-12 Thread Wez Furlong
I think you should be talking to the people that wrote those two libraries to ask them to clean up their exports; it's nothing to do with PHP. For a quick "fix", I'd suggest dropping recode and using iconv instead. --Wez. On Sun, 13 Feb 2005 16:24:42 +1100, [EMAIL PROTECTED] <[EMAIL PROTECTED]>