Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:62340 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 87574 invoked from network); 21 Aug 2012 12:45:18 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Aug 2012 12:45:18 -0000 Authentication-Results: pb1.pair.com header.from=glopes@nebm.ist.utl.pt; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=glopes@nebm.ist.utl.pt; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain nebm.ist.utl.pt from 193.136.128.22 cause and error) X-PHP-List-Original-Sender: glopes@nebm.ist.utl.pt X-Host-Fingerprint: 193.136.128.22 smtp2.ist.utl.pt Linux 2.6 Received: from [193.136.128.22] ([193.136.128.22:55141] helo=smtp2.ist.utl.pt) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 12/52-11730-DD283305 for ; Tue, 21 Aug 2012 08:45:17 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp2.ist.utl.pt (Postfix) with ESMTP id 897617000457 for ; Tue, 21 Aug 2012 13:45:13 +0100 (WEST) X-Virus-Scanned: by amavisd-new-2.6.4 (20090625) (Debian) at ist.utl.pt Received: from smtp2.ist.utl.pt ([127.0.0.1]) by localhost (smtp2.ist.utl.pt [127.0.0.1]) (amavisd-new, port 10025) with LMTP id ar8i9Ci8N35d for ; Tue, 21 Aug 2012 13:45:13 +0100 (WEST) Received: from nebm.ist.utl.pt (unknown [IPv6:2001:690:2100:4::58:1]) by smtp2.ist.utl.pt (Postfix) with ESMTP id 4164F7000450 for ; Tue, 21 Aug 2012 13:45:13 +0100 (WEST) Received: from localhost ([127.0.0.1] helo=nebm.ist.utl.pt) by nebm.ist.utl.pt with esmtp (Exim 4.72) (envelope-from ) id 1T3npZ-0004gQ-4s for internals@lists.php.net; Tue, 21 Aug 2012 13:45:13 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 21 Aug 2012 14:45:13 +0200 To: Organization: =?UTF-8?Q?N=C3=BAcleo_de_Engenharia_Biom=C3=A9dica_do_Insti?= =?UTF-8?Q?tuto_Superior_T=C3=A9cnico?= In-Reply-To: <50337AA8.30700@lsces.co.uk> References: <5032B197.9080502@lsces.co.uk> <5032BF77.6060108@lsces.co.uk> <5032C533.4070809@lerdorf.com> <5032D277.5050003@lsces.co.uk> <5032D427.70705@lerdorf.com> <503349C4.8070808@lsces.co.uk> <11efbe6b52ab1c3179f47595d9d4a3c9@nebm.ist.utl.pt> <50337AA8.30700@lsces.co.uk> Message-ID: <04a4dd6325257076ebca293e64e1c671@nebm.ist.utl.pt> X-Sender: glopes@nebm.ist.utl.pt User-Agent: RoundCube Webmail/0.8-rc Subject: Re: [PHP-DEV] shared mysqlnd extension ... From: glopes@nebm.ist.utl.pt (Gustavo Lopes) 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