Jason wrote:
I added app tests for
mpfr-3.1.0
mpfi-1.5.1
ecm-6.4.1
flint-2.3
pari-2.5.1
[Apparently Jeroen missed this.]
and the first missing functions are
../../../mpfr-3.1.0/src/mulders.c: In function 'mpfr_divhigh_n_basecase':
../../../mpfr-3.1.0/src/mulders.c:208:3: error: 'gmp_pi1_t' undeclared (first
use in this function)
../../../mpfr-3.1.0/src/mulders.c:208:3: note: each undeclared identifier is
reported only once for each function it appears in
../../../mpfr-3.1.0/src/mulders.c:208:14: error: expected ';' before 'dinv2'
../../../mpfr-3.1.0/src/mulders.c:229:3: warning: implicit declaration of
function 'invert_pi1'
../../../mpfr-3.1.0/src/mulders.c:229:15: error: 'dinv2' undeclared (first use
in this function)
../../../mpfr-3.1.0/src/mulders.c:244:9: warning: implicit declaration of
function 'udiv_qr_3by2'
make[2]: *** [mulders.lo] Error 1
I'll add the new undocumented functions this weekend to the svn for a
mpir-2.5.2 release in the next week or so
Note that MPFR 3.1.0 builds and works well with (still) MPIR 2.1.3 in
Sage, so these types and functions must have been removed from MPIR at
some point, unless I'm missing something...
-leif
> and also tests for the current stable GAP and the development version
of GAP
-----------------------------------------------
We currently test against
mpfr-3.0.1.tar.bz2
mpfi-1.5.tar.bz2
mpc-0.9.tar.gz
ecm-6.3.tar.gz
flint-2.1.tgz
pari-2.3.5.tar.gz
on all the usual test machines. I can easily add gap and any other smallish
packages(sage itself is too big) and/or versions.
Jason
---------------------------
Probably GAP uses some of the GMP internals. As far as I know, we
don't test MPIR against GAP. It sounds like we should.
Bill.
On 14 March 2012 02:55, William Stein<[email protected]> wrote:
Hi MPIR devs
Do any of you know what Dima is alluding to below?
---------- Forwarded message ----------
From: Dima Pasechnik<[email protected]>
Date: Tue, Mar 13, 2012 at 11:18 AM
Subject: [sage-devel] Re: Upgrading the optional GMP spkg
To: [email protected]
On Tuesday, 13 March 2012 21:30:07 UTC+8, Simon King wrote:
Hi!
I had problems with the optional gmp-4.2.1 spkg. After some half-
succeeding attempts to fix it, I tried to upgrade the spkg to the
latest upstream code: It works like a charm (i.e., builds and passes
self-tests)!
If someone is interested: #12661 provides a new gmp-5.0.4.spkg
(intended to be optional, of course) and needs review.
that's the version of GMP used by GAP 4.5 (they are moving towards
using an external
longnums package), and I know they recently were working quite a bit
with GMP people
to get in the right patches.
I wish GAP worked with MPIR, but the latter does not provide all the
GMP calls used by GAP.
It would be good if these were added...
Dima
The old spkg had a lot of patches. So far, the new applies none of
them - on openSuse, the unpatched code passes tests. However, I'd be
glad if the patch authors could check whether the fixes (some of them
addressing platform specific issues) all made it upstream.
According to the old spkg's SPKG.txt, it is needed to upgrade the
optional polymake spkg if gmp is upgraded. I haven't tried it.
Best regards,
Simon
--
To post to this group, send an email to [email protected]
To unsubscribe from this group, send an email to
[email protected]
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
--
William Stein
Professor of Mathematics
University of Washington
http://wstein.org
--
You received this message because you are subscribed to the Google Groups
"mpir-devel" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/mpir-devel?hl=en.
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You received this message because you are subscribed to the Google Groups
"mpir-devel" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/mpir-devel?hl=en.