On Feb 5, 12:18 pm, Bill Hart <goodwillh...@googlemail.com> wrote:
> 2009/2/5 <ja...@njkfrudils.plus.com>:
>
>
>
> > On Wednesday 04 February 2009 19:54:03 Bill Hart wrote:
> >> Thanks. As soon as we release, it would be great if you could give it
> >> a go and we can issue a service release.
>
> > Should I create a branch for it?
>
> I don't think that is a good idea. We should release, then do this in
> trunk. Otherwise we are going to have to do it all over again!
>
> I would release, but I am still waiting on:
>
> 1) Results of mabshoff's build testing on SkyNet
That is happening tonight since I will release Sage 3.3.alpha6 with
the 0.9-rc3 mpir. I will then do a full build test on SkyNet and
various other machiens.
> 2) Someone to move the tarball and webpage over towww.mpir.org(I
> don't have access).
(a) I can give you access
(b) I can move the html and the tarball over there, too. I am busy for
the next couple hours, but I will try to squeeze it in.
> > I dont do C++ , and I dont know how comprehensive the make check c++ bit is
> > ,
> > if someone can email me some c++ programs , I can test them
>
> Oh yes, we also have libgmpxx. I had forgotten about that. I also don't do
> c++.
>
Building Sage against MPIR is the best regression test for C as well
as the C++ library I am aware of :)
>
> > I assume we are going to leave internal names as __gmp_blah etc
>
> Yes, no function names should change.
Yes, too much code uses internal gmp function names. The same applies
to C++ namespaces if GMP would use them.
> Bill.
>
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"mpir-devel" group.
To post to this group, send email to mpir-devel@googlegroups.com
To unsubscribe from this group, send email to
mpir-devel+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/mpir-devel?hl=en
-~----------~----~----~----~------~----~------~--~---
