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?
What was causing me more confusion ( for the last two hours ) was that I could
not get the remote machine to connect to the database, so I was not sure if the
mysqli module was working at all. I've had to 'create' an extra set of users on
the PHP5.4 machine as 'localhost' will not work as a connection. I've found some
references to needing to use the ip address, and with some juggling I now have a
working connection on that machine via the domain name ... finally.
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
