# drop bison 1.x? - Thread: https://externals.io/message/55076 - Original archive: https://news-web.php.net/php.internals/55076 - Started by Pierre Joye on 2011-09-01T23:23:51+00:00 - Messages: 11 - Reply by email to internals@lists.php.net - More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt --- ## #55076 — Pierre Joye — 2011-09-01T23:23:51+00:00 URL: https://externals.io/message/55076#55076 It would be nice to get at least a little bit of the context before going in any kind of arguing. For one the failing test happening after my commit was my mistake. It has nothing to do with the bison versions but me having committed a wrong expectf expression. However, the 1.x support was the reason why I made this change. Instead of making it right I've updated my boxes with bison 2.x. Lazy and better.1 That being cleared, anyone using 1.x will have noticed that the tests did not pass. Fact is that it looks like I am the only tester using 2.x. Do you have any example of supported systems still having only bison 1.x support? Also 1.x is 13 years old, I would very surprised to see anyone still using such an old system with 5.3. Now, as stated earlier, my testing hosts do not have 1.x anymore and I won't care about it anymore either. So basically nobody here takes care if it anymore but let claim we do :) --- ## #55078 — Reindl Harald — 2011-09-01T23:33:22+00:00 URL: https://externals.io/message/55076#55078 · In reply to: #55076 it seems fedora had never bison 1.x http://koji.fedoraproject.org/koji/packageinfo?packageID=1084 Am 02.09.2011 01:23, schrieb Pierre Joye: > It would be nice to get at least a little bit of the context before going in > any kind of arguing. > > For one the failing test happening after my commit was my mistake. It has > nothing to do with the bison versions but me having committed a wrong > expectf expression. However, the 1.x support was the reason why I made this > change. Instead of making it right I've updated my boxes with bison 2.x. > Lazy and better.1 > > That being cleared, anyone using 1.x will have noticed that the tests did > not pass. Fact is that it looks like I am the only tester using 2.x. Do you > have any example of supported systems still having only bison 1.x support? > > Also 1.x is 13 years old, I would very surprised to see anyone still using > such an old system with 5.3. > > Now, as stated earlier, my testing hosts do not have 1.x anymore and I won't > care about it anymore either. So basically nobody here takes care if it > anymore but let claim we do :) --- ## #55080 — Richard Quadling — 2011-09-02T10:42:48+00:00 URL: https://externals.io/message/55076#55080 · In reply to: #55076 > It would be nice to get at least a little bit of the context before going in > any kind of arguing. > > For one the failing test happening after my commit was my mistake. It has > nothing to do with the bison versions but me having committed a wrong > expectf expression. However, the 1.x support was the reason why I made this > change. Instead of making it right I've updated my boxes with bison 2.x. > Lazy and better.1 > > That being cleared, anyone using 1.x will have noticed that the tests did > not pass. Fact is that it looks like I am the only tester using 2.x. Do you > have any example of supported systems still having only bison 1.x support? > > Also 1.x is 13 years old, I would very surprised to see anyone still using > such an old system with 5.3. > > Now, as stated earlier, my testing hosts do not have 1.x anymore and I won't > care about it anymore either. So basically nobody here takes care if it > anymore but let claim we do :) > > > The default build tools for building PHP on Windows uses Bison 1.27. http://windows.php.net/downloads/php-sdk/php-sdk-binary-tools-20110512.zip contains [2011-09-02 11:36:29] [D:\php-sdk-binary-tools-20110512\bin] [] >bison.exe --version GNU Bison version 1.27 -- Richard Quadling Twitter : EE : Zend : PHPDoc @RQuadling : e-e.com/M_248814.html : bit.ly/9O8vFY : bit.ly/lFnVea --- ## #55101 — Lester Caine — 2011-09-02T20:02:57+00:00 URL: https://externals.io/message/55076#55101 · In reply to: #55076 Pierre Joye wrote: > Also 1.x is 13 years old, I would very surprised to see anyone still using > such an old system with 5.3. It's the version packaged with the current windows build kit ;) -- 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// Firebird - http://www.firebirdsql.org/index.php --- ## #55119 — Pierre Joye — 2011-09-02T21:55:48+00:00 URL: https://externals.io/message/55076#55119 · In reply to: #55101 no, read the mails pls... > Pierre Joye wrote: > > […] > > It's the version packaged with the current windows build kit ;) > > -- > 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// > Firebird - http://www.firebirdsql.org/index.php > > -- > > > > -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org --- ## #55122 — Lester Caine — 2011-09-02T22:20:55+00:00 URL: https://externals.io/message/55076#55122 · In reply to: #55119 Pierre Joye wrote: > no, read the mails pls... > > […] ? http://windows.php.net/downloads/php-sdk/php-sdk-binary-tools-20110512.zip has bison 1.23 in it ... 28 June 1999 That is the one I'm running all of the windows builds on -- 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// Firebird - http://www.firebirdsql.org/index.php --- ## #55123 — Pierre Joye — 2011-09-02T22:55:48+00:00 URL: https://externals.io/message/55076#55123 · In reply to: #55122 It uses now bison 2.4, you can replace it with the gnu win32 version by deleting the old one and put the bison zip archive in php-sdk\ (share and bin). The SDKs file are updated on release only, that's why it is still 1.x there. > Pierre Joye wrote: > > […] > > > […] > > ? > http://windows.php.net/downloads/php-sdk/php-sdk-binary-tools-20110512.zip > has bison 1.23 in it ... 28 June 1999 > That is the one I'm running all of the windows builds on > > -- > 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// > Firebird - http://www.firebirdsql.org/index.php > -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org --- ## #55217 — Hannes Magnusson — 2011-09-05T11:58:14+00:00 URL: https://externals.io/message/55076#55217 · In reply to: #55123 Then we need a sdk-dev so people doing their own windows builds can work in a correct environment while they are testing. Updating the sdk only on release makes it impossible for devs to test on windows prior to releases. -Hannes > It uses now bison 2.4, you can replace it with the gnu win32 version > by deleting the old one and put the bison zip archive in php-sdk\ > (share and bin). The SDKs file are updated on release only, that's why > it is still 1.x there. > > > > […] > > > > -- > Pierre > > @pierrejoye | http://blog.thepimp.net | http://www.libgd.org --- ## #55218 — Pierre Joye — 2011-09-05T12:03:47+00:00 URL: https://externals.io/message/55076#55218 · In reply to: #55217 as I said earlier, these files are updated on release. It will be done for the next releases. I will see if I can provide "snapshots" SDK but that's something I try to avoid as it bring its lot of issues with unstable/untested libs. In the meantime it is very easy to replace the existing bison with the the one from gnu win32, as I described earlier in this thread. On Mon, Sep 5, 2011 at 1:58 PM, Hannes Magnusson wrote: > Then we need a sdk-dev so people doing their own windows builds can > work in a correct environment while they are testing. > Updating the sdk only on release makes it impossible for devs to test > on windows prior to releases. > > -Hannes > > > > […] > -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org --- ## #55219 — Hannes Magnusson — 2011-09-05T12:06:21+00:00 URL: https://externals.io/message/55076#55219 · In reply to: #55218 > as I said earlier, these files are updated on release. It will be done > for the next releases. I will see if I can provide "snapshots" SDK but > that's something I try to avoid as it bring its lot of issues with > unstable/untested libs. That sounds like a good idea to me. It will give other people the chance to test the libs in a broader environment then your testing facilities. -Hannes --- ## #55220 — Pierre Joye — 2011-09-05T12:08:40+00:00 URL: https://externals.io/message/55076#55220 · In reply to: #55219 On Mon, Sep 5, 2011 at 2:06 PM, Hannes Magnusson wrote: > > > […] > > That sounds like a good idea to me. > It will give other people the chance to test the libs in a broader > environment then your testing facilities. it is not about our testing facitilites but about people using unstable, incompatible, unreliable binaries to build their 3rd party extensions and then report crashes to us. -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org