Ah, that makes sense. Thanks. I'll ensure this gets done for the final
release (and the next snapshot).

I just hope they fix this bug in the next autotools release! The bug
is known to them!

Bill.

2010/1/8 Case Vanhorsen <cas...@gmail.com>:
> On Thu, Jan 7, 2010 at 7:05 AM, Bill Hart <goodwillh...@googlemail.com> wrote:
>> Sorry, I mean it is needed by make install. So perhaps it is the
>> Makefile in the top directory which needs this added.
>>
> I actually had to edit the Makefile in the doc directory. It was
> trying to create the info sub-directory. Everything seems to be
> working now.
>
> Case
>
>> Bill.
>>
>> 2010/1/7 Bill Hart <goodwillh...@googlemail.com>:
>>> Oh, that is a problem caused by autotools. Probably to fix it, you can
>>> edit the Makefile in the test directory. You'll probably find a line
>>> that says:
>>>
>>> mkdir...@mkdir_p@
>>>
>>> You need to replace this with a command to run mkdir. On my system it is:
>>>
>>> MKDIR_P=/usr/bin/mkdir -p
>>>
>>> I don't know why this would be there, as I thought I fixed this issue
>>> by updating configure.in. Trouble is, I of course just hard wired it
>>> to work on my machine and not anyone else's. I forgot that this
>>> command will be needed when doing make check, which the user will
>>> need.
>>>
>>> I don't have a complete fix for this issue yet. It is a known bug in
>>> the latest autotools. I can't believe they haven't fixed it. It
>>> beggars belief.
>>>
>>> Bill.
>>>
>>> 2010/1/7 Case Vanhorsen <cas...@gmail.com>:
>>>> On Thu, Jan 7, 2010 at 6:37 AM, Case Vanhorsen <cas...@gmail.com> wrote:
>>>>> On Thu, Jan 7, 2010 at 4:53 AM, Bill Hart <goodwillh...@googlemail.com> 
>>>>> wrote:
>>>>>> Yes, it was fixed. It definitely shouldn't do this.
>>>>>>
>>>>>> 2010/1/7 Case Vanhorsen <cas...@gmail.com>:
>>>>>>> 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 mpir-de...@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.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> You received this message because you are subscribed to the Google 
>>>>>> Groups "mpir-devel" group.
>>>>>> To post to this group, send email to mpir-de...@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.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>> 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 mpir-de...@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.
>>>>
>>>>
>>>>
>>>>
>>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "mpir-devel" group.
>> To post to this group, send email to mpir-de...@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.
>>
>>
>>
>>
>
> --
> You received this message because you are subscribed to the Google Groups 
> "mpir-devel" group.
> To post to this group, send email to mpir-de...@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.
>
>
>
>
-- 
You received this message because you are subscribed to the Google Groups 
"mpir-devel" group.
To post to this group, send email to mpir-de...@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.


Reply via email to