Re: shared mysqlnd extension ...

From: Date: Tue, 21 Aug 2012 12:45:13 +0000
Subject: Re: shared mysqlnd extension ...
References: 1 2 3 4 5 6 7 8 9  Groups: php.internals 
Request: Send a blank email to internals+get-62340@lists.php.net to get a copy of this message
Em 2012-08-21 14:10, Lester Caine escreveu:
Gustavo Lopes wrote:
So should I be updating that bug to the current state of play? That this is actually by design? Or create a new bug that states that '--enable-mysqlnd=shared' should not be allowed? Or is there some third position in this jigsaw?
It usually helps that the extension you compile is binary compatible with the PHP build you're loading it in. In your case, I'd guess you compiled PHP with ZTS support but mysqlnd without. As to whether '--enable-mysqlnd=shared' actually works or not I can't be sure as I haven't tested it. But there's nothing in the problem you're having that points to it not working when built properly.
Current situation is that I've run a clean build of the Apache module with mysqlnd included statically, and the mysqli extension is compiled as shared. If I add the '--enable-mysqlnd=shared' then it does build a shared mysqlnd module, but the module is unusable due to the 'executor_globals' error, so either there should be no option TO build shared? Or the problem in the shared module needs fixing?
I've just tried to compile mysqlnd and mysqli shared and it worked (at least sapi/cli/php -n -d extension_dir=modules -d extension=mysqlnd.so -d extension=mysqli.so -i showed no problems). It is at least conceivable that there's some bug I'm not hitting. In any case, this is a development mailing list. So you can either try to figure out the problem yourself using this mailing list asking for pointers if necessary -- that means actually checking the source code, inspecting symbols in the binaries, preprocessor defines after configure etc. -- or you can file a bug report with clear, complete steps for reproducing the problem. -- Gustavo Lopes

« previous php.internals (#62340) next »