Re: [mpir-devel] Fwd: [sage-devel] Re: Upgrading the optional GMP spkg

2012-03-15 Thread Jason
-- > From: Dima Pasechnik > Date: Tue, Mar 13, 2012 at 11:18 AM > Subject: [sage-devel] Re: Upgrading the optional GMP spkg > To: sage-devel@googlegroups.com > > > > > On Tuesday, 13 March 2012 21:30:07 UTC+8, Simon King wrote: >> >> Hi! >>

Re: [mpir-devel] Fwd: [sage-devel] Re: Upgrading the optional GMP spkg

2012-03-14 Thread Bill Hart
ssage -- > From: Dima Pasechnik > Date: Tue, Mar 13, 2012 at 11:18 AM > Subject: [sage-devel] Re: Upgrading the optional GMP spkg > To: sage-devel@googlegroups.com > > > > > On Tuesday, 13 March 2012 21:30:07 UTC+8, Simon King wrote: >> >> Hi! >>

Fwd: [sage-devel] Re: Upgrading the optional GMP spkg

2012-03-13 Thread William Stein
Hi MPIR devs Do any of you know what Dima is alluding to below? -- Forwarded message -- From: Dima Pasechnik Date: Tue, Mar 13, 2012 at 11:18 AM Subject: [sage-devel] Re: Upgrading the optional GMP spkg To: sage-devel@googlegroups.com On Tuesday, 13 March 2012 21:30:07 UTC

[sage-devel] Re: Upgrading the optional GMP spkg

2012-03-13 Thread Nils Bruin
On Mar 13, 11:18 am, Dima Pasechnik wrote: > 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... It would probably be *essential* that these get added if GAP is to ever run in library mode. I doubt that one can ha

[sage-devel] Re: Upgrading the optional GMP spkg

2012-03-13 Thread Dima Pasechnik
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)!