#19589: Upgrade MPIR to 2.7.1
-------------------------------------+-------------------------------------
Reporter: jdemeyer | Owner:
Type: enhancement | Status: positive_review
Priority: major | Milestone: sage-6.10
Component: packages: | Resolution:
standard | Merged in:
Keywords: | Reviewers: François Bissey
Authors: Jeroen Demeyer | Work issues:
Report Upstream: N/A | Commit:
Branch: | 6ca243c806b350acb1c19c7613a1159f9592db2b
u/jdemeyer/upgrade_mpir_to_2_7_1 | Stopgaps:
Dependencies: #19602 |
-------------------------------------+-------------------------------------
Comment (by leif):
Replying to [comment:24 wbhart]:
> I propose to reissue MPIR-2.7.1 with fixed .so version numbering.
>
> LIBGMP_LT_CURRENT = 22
> LIBGMP_LT_REVISION = 1
> LIBGMP_LT_AGE = 6
>
> LIBGMPXX_LT_CURRENT = 12
> LIBGMPXX_LT_REVISION = 1
> LIBGMPXX_LT_AGE = 4
>
> which (I have checked) leads to 16.6.1 and 8.4.1.
>
> Is this ok with everyone?
To avoid a "downgrade" compared to 2.7.0's mistaken version numbers I
guess.
I'd of course prefer fixing those of 2.7.0... B)
[[BR]]
While you're at it, some of the confusion presumably arose from the use of
periods instead of colons (libtool syntax) in the version table, starting
with MPIR 2.1.2 and on:
{{{
# GMP -version-info
# release libgmp libgmpxx libmp
# 2.0.x - - -
# 3.0 3:0:0 - 3:0:0
# 3.0.1 3:1:0 - 3:0:0
# 3.1 4:0:1 - 4:0:1
# 3.1.1 4:1:1 - 4:1:1
# 4.0 5:0:2 3:0:0 4:2:1
# 4.0.1 5:1:2 3:1:0 4:3:1
# 4.1 6:0:3 3:2:0 4:4:1
# 4.1.1 6:1:3 3:3:0 4:5:1
# 4.1.2 6:2:3 3:4:0 4:6:1
# 4.1.3 6:3:3 3:5:0 4:7:1
# 4.1.4 6:3:3 3:5:0 4:7:1 WRONG, same as 4.1.3!
# 4.2 6:0:3 3:2:0 4:4:1 REALLY WRONG, same as 4.1!
# 4.2.1 7:1:4 4:1:1 4:10:1
#
# MPIR -version-info
# release libgmp libgmpxx libmp
# 0.9.0 7:1:4 4:1:1 4:10:1 WRONG, same as GMP 4.2.1
# 1.0.0 7:2:4 4:2:1 4:11:1
# 1.1.0 7:3:4 4:3:1 4:12:1
# 1.2.0 7:4:4 4:4:1 4:13:1
# 1.3.0 8:0:0 4:5:1 4:14:1
# 1.3.1 8:1:0 4:6:1 0:0:0
# 2.0.0 9:2:0 4:7:1
# 2.1.0 10:0:1 4:8:1
# 2.1.1 10:1:2 4:9:2
# 2.1.2 10.2.2 4.10.2
# 2.1.3 10.3.2 4.11.2
# 2.1.4 10.4.2 4.12.2
# 2.2.0 10.5.2 4.13.2
# 2.2.1 10.6.3 4.14.3
# 2.3.0 10.7.3 4.15.3
# 2.3.1 10.8.3 4.16.3
# 2.4.0 11.0.4 4.17.3
# 2.5.0 11.1.4 4.18.3
# 2.5.1 11.2.4 4.19.3
# 2.5.2 11.3.4 4.20.3
# 2.6.0 11.0.5 4.21.3 Clearly wrong!!
# 2.7.0 16.0.6 8.0.4 Attempt to correct wrt all
prev
# 2.7.1 16.1.6 8.1.4
#
# Starting at 3:0:0 is a slight abuse of the versioning system, but it
# ensures we're past soname libgmp.so.2, which was used on Debian
GNU/Linux
# packages of gmp 2. Pretend gmp 2 was 2:0:0, so the interface changes
for
# gmp 3 mean 3:0:0 is right.
#
# We interpret "implementation changed" in item "1." above as meaning any
# release, ie. the REVISION is incremented every time (if nothing else).
# Even if we thought the code generated will be identical on all systems,
# it's still good to get the shared library filename (like
# libgmpxx.so.3.0.4) incrementing, to make it clear which GMP it's from.
}}}
You could also add an extra column for the ''resulting library version''
(in period notation).
--
Ticket URL: <http://trac.sagemath.org/ticket/19589#comment:25>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
