Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:86723 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 50093 invoked from network); 16 Jun 2015 22:20:56 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Jun 2015 22:20:56 -0000 Authentication-Results: pb1.pair.com smtp.mail=cmbecker69@gmx.de; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=cmbecker69@gmx.de; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.17.21 as permitted sender) X-PHP-List-Original-Sender: cmbecker69@gmx.de X-Host-Fingerprint: 212.227.17.21 mout.gmx.net Received: from [212.227.17.21] ([212.227.17.21:50021] helo=mout.gmx.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id CA/41-41412-541A0855 for ; Tue, 16 Jun 2015 18:20:54 -0400 Received: from [192.168.0.100] ([95.89.139.132]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0MP0LT-1ZBKjz0Sm7-006Qps; Wed, 17 Jun 2015 00:20:44 +0200 Message-ID: <5580A13F.9040806@gmx.de> Date: Wed, 17 Jun 2015 00:20:47 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: =?UTF-8?B?Sm9oYW5uZXMgU2NobMO8dGVy?= CC: Sara Golemon , "internals@lists.php.net >> PHP Internals" References: <00c501d0a773$f84fee90$e8efcbb0$@belski.net> <557EDF48.9000800@gmx.de> <1434379932.17693.5.camel@kuechenschabe> <1434400117.17693.10.camel@kuechenschabe> <4efunalbluqdcrf5h91lmsqtedj5t40i95@4ax.com> <557F4B64.6040403@gmx.de> <1434411840.17693.17.camel@kuechenschabe> <557F6788.9040908@gmx.de> <1434455919.21120.0.camel@kuechenschabe> In-Reply-To: <1434455919.21120.0.camel@kuechenschabe> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K0:tFOHtm/LwvH3W1mjBiqIm2Y5y3GbRLjvlmKEAtgOzfcnuF10UAu kAdqVo0IL/ReSGd65//zXqkzg/+vtGY+Rr/XnCv8vS6rET/UMVd6ZGTQ9z1n4v1+wh8N8kI /aGjN70fk2gE5aFC/WjPbTEPejAieYM/1IzxiDaV3g5Thv2MDNxEdMvDI5UkgsyUjD+/A/e 0ZtoSKCF1XLc+42MR5U+Q== X-UI-Out-Filterresults: notjunk:1;V01:K0:Yk79+mlADM8=:xXWOEx+oSmPNRNrxgXqkc0 IRSWXgg9XFYwqJLkrr3I16k8NI/7oCfrTbmkUEDMsXOTQa8OjjrSaW0uXgSGZmvO0vAU+S6YZ jPKln4X/TBmaoLkcUkueHtDmpkjDJ8nSJ4VKop2UPnNDOEBlwXkQbKsm4JE+lpVgICyIjP0Lr 7oo9RoJgrtRNeC7UKcRppaaOuMH/Tb94+LG/vIIjPCwUpJsi1Gn+/2XcMPUx2SEml7PRI/ZZ/ a32eagUkhz8hLhkBo6AWqu6WYTRTqWU1CfOiTM3OdbEGkxd47Tw8+TyZuDAtNReHBiSYbXfnA aziJewxNZtbDsw6OxirVpZ3qvA3M5/tVYr+uM+w7de3T9+dVT+2qF6/BpD8Bizdbwkey2pZeu ZeJbw0sNmy7D6FRtAe1zDK9UlTs4NCXDw0ed7ELb4xA+lkYFF80ZIbS46U8W/xt5SIQQKeya2 zSOHD1ffVB1K7xg69RbdqS0oaKMIaHwwuKpP3OA3OFti1W909U+Q2weOSgkTw1rC9C8gsvX2w BQ2fXw5MkAKxCcNPoTFSCraF3W6H7HdzcEnzOMIkm9IDffrJTvltJWeL9RB282K4jYWt7IudO e8OVWtNoYbaESW7gh5qGut58d3jUvDmD+86IxswxFEpnVeggX+grTrZ1cjEO1CKZ7Y2PXLRHV KaerfRChdHR/OQPv66RBz0LQdxZCq91/cuJva+dx24my/OF5M1PJLmDmw0o3pKdQqRGc= Subject: Re: [PHP-DEV] PHP7 releases vs Windows Sources? From: cmbecker69@gmx.de (Christoph Becker) Johannes Schlüter wrote: > On Tue, 2015-06-16 at 02:02 +0200, Christoph Becker wrote: >> Johannes Schlüter wrote: >> >>> It is not including the generated parsers. This means the user might use >>> a different version, which might cause a bug which might be hard to >>> debug as usage of provided files is assumed. >> >> Fair enough. However, the Windows sources neither contain the generated >> parser files, because they would break linking on Windows, see >> . > > This is a bug and has to be addressed. I have investigated further. The issue is commit b8e2629[1]. I'm certain that Sara had good reasons to mark zendparse() as ZEND_API. However, that breaks building with the generated zend_language_parser files with MSVC, if they have been generated with a somewhat recent bison (2.4.1 still works, 2.7.12 fails), because newer versions declare zendparse() again in .c and .h – without ZEND_API. It seems the only possibility to fix this mismatch would be to use a custom skeleton, but the /usr/share/bison/README states: | These skeletons are the only ones supported by the Bison team. | Because the interface between skeletons and the bison program is not | finished, *we are not bound to it*. In particular, Bison is not | mature enough for us to consider that "foreign skeletons" are | supported. So what to do? [1] -- Christoph M. Becker