On Thu, Jan 7, 2010 at 6:37 AM, Case Vanhorsen <[email protected]> wrote: > On Thu, Jan 7, 2010 at 4:53 AM, Bill Hart <[email protected]> wrote: >> Yes, it was fixed. It definitely shouldn't do this. >> >> 2010/1/7 Case Vanhorsen <[email protected]>: >>> Hello, >>> >>> The current trunk (r2579) is passing all my 64-bit Windows stress tests. >>> >>> But mpz_nextprime is still returning too many composites. For example, >>> gmpy.next_prime(3270400) is returning mpz(3270403). >>> >>> I thought this was fixed earlier? >>> >>> casevh >>> >>> -- >>> 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. >>> >>> >>> >>> >> >> -- >> 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. >> >> >> >> > Strange. I'll look at this again tonight. > > casevh > Took a real quick look. It definitely is fixed. My real problem is that I was doing the the next_prime test under Linux and "make install" was not updating libmpir. I'm so used to it working, I didn't see the error message:
test -z "/usr/local/share/info" || @MKDIR_P@ "/usr/local/share/info" /bin/bash: @MKDIR_P@: command not found I'll look at that tonight. casevh
-- 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.
