ID: 50990 Updated by: paj...@php.net Reported By: php-bugs-2010 at ryandesign dot com -Status: Open +Status: Closed Bug Type: GNU MP related Operating System: Mac OS X 10.6.2 PHP Version: 5.3.2RC1 New Comment:
@susan dot smith dot dev at gmail dot com Thing is your emotional replies have simply little to do with the actual issues (the technical one is indeed easy to fix). We have to be careful that no viral (no bad meaning here) licensed code got in or is used with php, to avoid troubles. We have met issues already with the same kind of license changes and we really don't want this mess again. That has nothing to do with propaganda or any other pollitical discussions. PHP is known to have a very liberal license and what we provide usually have no limitation for commercial/closed source/free softwares usage. Now, about the issue, I applied a fix that should work with (very) old versions as well. Previous Comments: ------------------------------------------------------------------------ [2010-02-19 08:26:58] susan dot smith dot dev at gmail dot com @ pajoye at php dot net I should probably ignore your comment, simply... Was I not polite? Why? Did I say that someone choice are "madness"? Or I simply said that different libraries give different support to different systems? Users should be free to make their own choice, shouldn't they? Some PHP users asked for a very small compatibility issue, and someone here suggested them to change the library they are using... This is not respect for users choices, is it? I suggested a very simple change. With it, PHP will be compatible with old GMP versions, with the last GMP version, with old MPIR versions and with the last MPIR version. You may say that suggesting such a small change is not polite, maybe... but it solved the problems to the users. Is there someone that is using this ticket for propaganda? Instead of using it for bug-tracking? Read the entire thread and guess who :-) I suggest to close this discussion this way: verify if the suggested change breaks anything, apply it, and close the ticket. Sorry if you feel this last suggestion as not polite. I'll not answer any more, the bug was solved. ------------------------------------------------------------------------ [2010-02-18 22:52:46] paj...@php.net @susan dot smith dot dev at gmail dot com Please stay pollite. MPIR has more maintainers, more open and active. Yes, GMP is still under development, but that's about it. Now about lgpl v3, we are certainly not on the same line. ------------------------------------------------------------------------ [2010-02-18 18:11:43] vikingjs at mac dot com Thanks, Susan - that substitution (in gmp.c on line 1362 for those following at home) got me over this hurdle as well. ------------------------------------------------------------------------ [2010-02-17 15:52:57] susan dot smith dot dev at gmail dot com Don't be silly! MPIR gives better support for Windows, not for "modern architecture", on POSIX systems GMP (http://gmplib.org/) is usually better... and LGPL v3 is as compatible with the licence of PHP as LGPL v2 is. I solved replacing the outdated __GMP_BITS_PER_MP_LIMB defined constant with GMP_LIMB_BITS. The latter is present in all previous versions, and MPIR define it too. ------------------------------------------------------------------------ [2010-02-10 10:56:33] paj...@php.net ZF depends on the gmp php extension, which can be built against MPIR instead of gmplib. See http://www.mpir.org/. It is a rock solid gmp compatible library with much better support for modern architecture and optimizations, without the (l)gpl v3 license madness. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/50990 -- Edit this bug report at http://bugs.php.net/?id=50990&edit=1
